Your data and privacy choices
What Aedrova can use, what you can stop, and how to request a copy or removal.
Choose what reaches AI
Messages, uploaded files, meeting text and connector results are different sources of context. A workspace membership does not make every private channel accessible. Buds use the resources granted to them. Coding requests can include accessible workspace history and project context, so review the provider and scope before invoking the agent.
Use available context controls to review or exclude eligible sources. Changing future access cannot recall a prompt or result already sent to an AI provider. Automatic planning/execution controls allow supported work in the build copy; original-project changes and publishing retain their approval gates. Turning that setting off stops new automatic authorization, not an action already completed.
Disconnect a tool
- Open your Bud’s connectors and select the connection you want to manage.
- Disconnect the stored connection to stop its future use through Aedrova.
- Visit the provider’s authorized-app settings and revoke Aedrova there as well.
- Check any separately granted accounts or resources. Removing one grant may not remove another.
Disconnect does not delete the repository, page, design file, payment records or social account in the original service. The provider manages data already stored in its own systems. Do not submit access tokens in a support message.
Meeting text needs separate consent
Where enabled, meeting privacy settings separately cover saving text and reusing it as AI context. All present participants must consent under the supported workflow. A microphone permission alone is not consent to shared transcription.
Meeting privacy offers withdrawal of AI access and deletion of saved shared meeting text. Withdrawal affects future use of that meeting’s shared text. Deletion is consequential for all participants, so read the confirmation. An end-of-meeting review can correct the transcription before confirmation; that confirmation does not override a participant’s missing or withdrawn consent. Hosted transcription still depends on available infrastructure.
Chat, files and local projects
Use message removal for messages you are authorized to remove. Removing a message is not a promise to erase every database record, prior notification, recipient copy, downloaded attachment or backup. Channel permissions continue to govern private files. A voice recording you send is a channel attachment, not a disappearing meeting chunk.
Your original local project and provider-created copies are separate from hosted account data. Downloaded files, local build copies and exports can remain on a computer after logout or a hosted deletion request. Remove local copies you no longer need using the relevant app or operating system; keep work you are legally required to retain. Do not delete an original project simply to disconnect Aedrova.
Request access, export, correction or deletion
Email [email protected] from your account or waitlist address. State the request type and the relevant workspace name. Specify whether you mean personal account information, a particular file/meeting, or an entire workspace. A whole-workspace request requires authority; one member cannot request other members’ unrelated data.
We verify identity and scope, explain retained records or limitations, and respond according to applicable law. Account/workspace export and permanent deletion currently use this support process; there is currently no one-click automated erase/export feature. Do not email government ID, passwords or keys. Deleting data is separate from cancelling a subscription. Backups and third-party systems can have different removal schedules.
Request help with my data ↗