Security & trust
Aedrova uses authenticated workspace access, channel permissions, scoped connections and backend checks. Release testing and independent review remain part of the launch process.
What the controls mean
Private content is governed by membership and authorization. Upload checks validate content before publication. Provider credentials are kept out of frontend assets and protected in the supported credential storage. Transport encryption does not make the product end-to-end encrypted: authorized backend or AI services may process readable content for the requested feature.
We do not claim SOC 2 certification, a guaranteed absence of vulnerabilities, a universal residency commitment or a public uptime SLA. The current Beta is still under validation. Limits, outage recovery and cross-workspace testing remain release gates.
Report a vulnerability
Email [email protected] with “Security report” in the subject. Include the affected feature, minimal reproduction steps and expected versus actual access, using your own test accounts. Redact credentials and private content. Do not access more data, disrupt availability, socially engineer users or publish secrets.
We will coordinate a safe investigation. There is no paid bounty, blanket authorization to test third-party infrastructure or automatic legal safe-harbor promise on this page. Ask before testing beyond normal use of your own accounts.
Availability
The public website is in waitlist mode. Paid checkout and public desktop downloads are not active. Some hosted features and connectors remain in testing. This page is not a live uptime monitor; contact support for an incident or provider-specific question.
Contact security support ↗