Privacy policy
Effective October 12, 2026 · Updated October 21, 2026
Aedrova operates this website and provides a collaborative workspace for teams and AI teammates called Buds. These documents cover the website and, when available to you, the desktop app and hosted services.
Business name: Aedrova. We currently use Aedrova as our brand name and do not represent it as a registered corporation. The legal operator, business address and jurisdiction remain to be confirmed before paid launch.
Questions? Visit Customer support, email [email protected], or call (408) 634-5254.
Browse all 25 sections
1. Information we collect
Website and waitlist. Joining the waitlist collects your email address, consent to receive launch updates and a confirmation that you meet the minimum-age/guardian requirements. We do not ask for a date of birth. Enterprise inquiries collect the contact and project information you submit. Support requests include your contact information and the contents of your request. Registration does not create an account or subscription. Waitlist addresses are not used as AI build context. If you complete the optional website introduction before plans, your referral-source choice and optional detail are included with a later waitlist registration to understand how people find Aedrova. Other introduction answers are not included with the registration; your chosen agent nickname is used if you later create a workspace. Referral answers are not sent as AI build context.
Accounts and workspaces. When account access is enabled, Google and Apple sign-in through Supabase provide account details such as your email address and sign-in identifier. You can choose to share a relay address with Apple. You can add a display name and profile picture in Aedrova. We process workspace membership, roles, profile settings, messages, replies, reactions, uploaded files and other content you or your teammates supply. Workspace owners and authorized members can access information according to their permissions.
Buds and connected services. We process your Bud’s name, appearance, instructions, role, preferences and authorized connections. Connecting a service can provide account identifiers, resource selections, access credentials and content available under the permissions you approve. Examples include repositories, documents, design files, social account information, deployment information and Stripe account/balance information. The actual provider consent screen and selected resources determine the connection’s scope.
Meetings and voice. When available and enabled, meeting and voice features process participant information and audio/video needed to provide the call. Transcription processes submitted audio and resulting text. Meeting summaries and transcripts can contain personal or confidential information. Participants must be informed and any required consent obtained before recording or transcription. A call does not mean that recording, transcription or AI access is automatically enabled.
Operational and billing information. Hosting and service systems process IP addresses, request times, error/security information and service usage. We retain subscription state, payment references, run identifiers and AI usage accounting where those features are enabled. Stripe handles card/payment details; this website does not store full card numbers.
2. Why we use information
We use information to operate the service, authenticate accounts, deliver team collaboration and requested AI work, manage authorized connections, prevent abuse, enforce usage limits, provide support, maintain security, process billing and meet applicable legal obligations. Waitlist emails are used for launch updates and administration of your registration. We do not sell personal information or share it for cross-context behavioral advertising.
3. AI, project access and connector permissions
Invoking an AI participant can transmit your prompt, permitted workspace context, relevant files, project content and authorized connector results to the selected provider. Aedrova may use OpenAI or Anthropic, or a coding runtime you connect, depending on the feature and configuration. Only enable a provider or connection if you are authorized to share the relevant data. Do not submit credentials, regulated health information or other highly sensitive information that the service is not configured to handle.
AI processing is not exclusively on your device. Providers’ retention and processing rules depend on their service and account configuration; we do not promise zero retention or that every provider excludes all data from training. Review the selected provider’s applicable terms and privacy information. Aedrova does not use your workspace content to train its own general-purpose AI models.
Automatic planning/execution permissions allow the configured workflow to plan, edit and run supported commands in its build environment. They do not make every connected account universally available to every Bud. Review permissions and generated work. Disconnecting in Aedrova stops future use through that stored connection, but may not revoke permission at the provider; revoke access in the provider’s account settings as well. Data already sent to a provider is subject to that provider’s controls.
iPhone follow-ups. If you choose Allow and send, Aedrova sends your question and the selected reply to OpenAI to generate an answer. The question or reply may include personal information. A new follow-up asks for permission again. You can use chat without sharing this content with OpenAI.
4. Who receives information
Information is shared with authorized workspace participants, service providers needed to deliver the requested functionality, providers you connect, and selected AI providers. Current infrastructure includes Supabase for authentication/database/storage, Render for website/service hosting, Cloudflare for domain/network services, Google for sign-in, and Stripe for enabled payment or Stripe connector functions. Optional integrations include GitHub, Figma, Notion, Supabase, Instagram/Meta, TikTok and Vercel; managed search can use Brave. Availability varies and some connections remain under testing.
We may disclose information when legally required, to respond to valid legal process, protect users or investigate fraud/security incidents. If the business is transferred, relevant information may transfer subject to applicable law and notice where required. We do not grant other workspaces access to your content merely because they use Aedrova.
5. Cookies, browser storage and tracking
With your preference-storage choice, we use browser storage for appearance preferences and website introduction answers, and session cookies when sign-in is enabled. Infrastructure may use security-related cookies and logs. We do not currently run advertising pixels or cross-site behavioral advertising on the website. Because that tracking is not used, browser Do Not Track signals do not change its behavior. Third-party sites you open, including sign-in and connector pages, have their own practices. Fonts and website background media are served by Aedrova.
Chat safety on iPhone. When you report a message, Aedrova Support receives the reason, an excerpt, and the account and conversation identifiers needed to investigate. Blocking stores your choice and restricts direct messages. You can unblock teammates in Account.
6. Retention, deletion and security
Waitlist email addresses are encrypted in our Supabase database and retained for up to one year, unless you request earlier removal. Active workspace content and connector settings are retained while needed to provide the service or until an authorized deletion request is completed. Disconnecting a connector removes its stored grant from active use; it does not delete the source content in the external service.
Session and temporary response data are subject to expiry/maintenance. Billing, usage and security records may be retained when necessary for accounting, dispute handling, fraud prevention or legal obligations. Deleted data may remain in backups until those backups rotate and cannot always be removed immediately from third-party systems. We do not claim one universal retention period for every category or an instant deletion guarantee.
We use access controls, encrypted storage for service credentials and sensitive backend records, and secure transport where supported. Encryption does not mean that no authorized service can decrypt data to perform its function. No service can guarantee absolute security. Protect your account and report suspected exposure promptly through support.
Account deletion on iPhone. Open Account → Delete account to request deletion and get a reference. Allow up to 30 days. We email you when it is complete or if we need more information. If you used Sign in with Apple, Aedrova can use an available Apple token to revoke sign-in access during deletion. Where a token is unavailable, we provide the steps to remove Aedrova in your Apple Account settings.
7. Your choices and privacy requests
For requests to remove your waitlist registration, email [email protected] from the address you registered. You can also request access, correction, export or deletion of personal data, withdraw consent, or ask questions about processing. Identify the relevant account/workspace and request type; do not email passwords, access tokens or identity documents. We may verify your identity and authority before acting, and respond within applicable legal time limits.
For workspace content, your organization may control access and retention; contact its owner as well. Deleting your account does not automatically delete other members’ independently retained content. Rights and exceptions depend on your location and applicable law. Where applicable, you may object to processing, request restriction or complain to your local data-protection authority. We do not retaliate for exercising applicable privacy rights.
8. International processing and children
Providers may process information in the United States and other countries. Your device location does not guarantee the storage location of hosted or provider-processed data. Contact us before using Aedrova if your organization requires specific residency, transfer safeguards or a data-processing agreement. Do not assume those arrangements exist by default.
Aedrova is not directed to children under 13, and they must not register or submit personal information. If you believe a child has supplied information, contact us so we can investigate and remove it as appropriate.
9. Your organization and Aedrova
For our website, waitlist, account administration, security and billing activities, Aedrova determines how the relevant information is used. For content supplied by a team for its own work, the organization may determine the purposes of processing and Aedrova may act on its instructions. Your organization’s own notices and any agreed processing terms also apply. Workspace administrators can manage membership and approved resources; an administrator is not automatically entitled to other organizations’ data or your unrelated connected accounts.
If a workplace gave you access, contact its administrator about its retention and monitoring practices. We help route requests that concern organization-controlled content. We do not treat employment, meeting attendance or a team invitation as blanket consent to every AI use.
10. Purposes and legal bases
Where applicable law requires a legal basis, account and requested service processing is generally necessary to provide the service under our agreement. Optional launch communications and consent-based meeting processing rely on your choice where required. Security, fraud prevention and limited service administration may rely on legitimate interests, balanced against applicable rights. Financial records and responses to valid legal process may be necessary to comply with legal obligations. We do not rely on a generic acceptance of this policy to authorize unrelated processing.
Information required to authenticate, deliver a message or perform an authorized task may be necessary for that feature to work. You can leave optional profile details blank. Declining meeting consent or a connector limits that specific functionality; it does not authorize us to silently obtain equivalent access elsewhere.
11. Regional rights and requests
Depending on applicable law and eligibility, you may have rights to know or access the categories and specific personal information processed; correct it; request deletion or a portable copy; restrict or object to processing; withdraw consent; and complain to a relevant regulator. California and other US state laws can provide additional rights concerning sale, sharing, sensitive information and appeals. Aedrova does not currently sell personal information or share it for cross-context advertising. We do not treat a request as permission to collect additional marketing data.
Use the privacy request instructions or [email protected]. An authorized representative may contact us; we may need evidence of authority and proportionate identity verification before disclosing or deleting account data. Do not send identity documents unless we agree a secure, necessary verification method. We explain any denial or limitation and available appeal route as required by applicable law. Requests do not require a paid subscription. There may be exceptions for others’ rights, security, legal obligations or organization-controlled records.
We have not established that every regional privacy statute applies to Aedrova. These disclosures do not replace any additional notices, representative appointments or contractual transfer safeguards required for a particular market. We review those requirements before expanding availability.
12. Practical controls and limits
See Data and AI controls for connector disconnect, meeting-consent withdrawal, message removal and export/deletion requests. Invoking a coding agent can include accessible workspace history and project context, not only the words after the mention. Bud responses can include evidence retrieved from resources you authorize. Review the provider and context before requesting work; a Bud’s appearance does not change the data flow.
A sent voice message is an audio file shared in its channel. It is distinct from ephemeral audio chunks sent for meeting transcription. Aedrova’s backend does not intentionally write those transcription chunks to disk, but the speech provider has its own processing and retention rules. Saved meeting text is subject to its consent and expiry controls, currently a 30-day text window where enabled. The expiry is an access/maintenance rule, not a promise of immediate physical erasure from every backup.
Our privacy notices are updated as functionality changes. The service-provider inventory distinguishes infrastructure from optional integrations. We do not make solely automated decisions intended to determine your legal rights or similarly significant status; Bud outputs are assistance for human review. Technical rate limits or security restrictions may be automated; contact support if you believe they were applied incorrectly.
13. Where information comes from
We receive information directly from you when you register, configure a profile or Bud, enter a prompt, upload a file, send a voice message, contact support or submit an inquiry. We also receive information from teammates who invite you, identify you in a message, add you to a workspace or share content that concerns you. Information in a team conversation can describe a person who does not have an Aedrova account.
Authentication providers supply the identity information permitted by the sign-in process. A connected service supplies information under its actual grant and selected resources. Infrastructure generates operational information when requests are handled. We do not treat a public profile, an invitation or a colleague’s upload as permission to obtain every record about that person. If you provide information about others, give them any required notice and ensure you have authority to share it.
Search or authorized sources may contain publicly available information. Public availability does not mean that information is unrestricted for every purpose. Retrieved results can be included in an answer, saved work or the context of the requested task. Please identify the relevant source and workspace when requesting a correction; we cannot change the original provider’s independent records.
14. Categories of personal information
The following categories describe information Aedrova can process when the corresponding feature is used. They are not a statement that every category is collected from every visitor.
- Identifiers and account details: email address, display name, username, avatar, authentication identifiers, workspace/member identifiers and network address.
- Profile and team information: optional biography, role/title, presence, custom status, membership, access role, channel participation and preferences you supply.
- User content and communications: messages, replies, reactions, attachments, code, documents, support correspondence, prompts, voice recordings, meeting text and generated results.
- Connection information: provider and account identifiers, resource references, authorization grants and tokens, granted scopes and retrieved information needed for an authorized task.
- Commercial and service records: plan, subscription/customer references, billing state, payment events, request usage, task accounting and relevant purchase/support records.
- Technical information: browser/device or request information exposed during operation, session/OAuth state, timestamps, failure information and security/rate-limit events.
- Preferences and derived task information: Bud instructions, chosen work style, selected context, task state and summaries or other outputs produced from supplied information.
Some content may contain sensitive information even though we do not ask for it: health details, government identifiers, confidential personnel information, precise locations or financial records, for example. Access credentials are sensitive connection information. Do not upload highly sensitive or regulated content unless an appropriate written arrangement and technical configuration support that use. Ordinary account authentication or an Enterprise inquiry alone does not establish such an arrangement.
Aedrova does not intentionally create voiceprints, face-recognition templates or biometric identity profiles from call media. Processing a voice recording to deliver audio or text is different from identifying someone by a biometric template. Audio, avatars and transcripts can nevertheless identify a person and should be shared with care.
15. Purpose limitations and service administration
Identity and membership information allow us to authenticate users, determine available workspaces and enforce role/channel access. Communication content is handled to deliver messages, replies, search and the requested collaboration functions. File information is handled to verify, store and deliver authorized attachments. Connection credentials and resources enable the specific connected-tool work you approve. AI prompts and selected context enable requested answers or builds.
Billing references and usage records allow us to associate a plan with the correct workspace, enforce shared capacity, reconcile payments and prevent duplicate or abusive requests. Error and security information helps diagnose failures, protect sessions and investigate suspected unauthorized use. Support information allows us to respond and document resolution. We use registration/contact information for the communications you request and necessary administrative notices.
These purposes do not authorize unrelated advertising, the public promotion of private workspace content or the creation of unrestricted profiles of individuals. If we introduce a materially different purpose, we will provide appropriate notice and obtain consent or another valid basis where required. If you ask us not to process optional information, the related optional feature may be unavailable while other eligible features remain usable.
16. AI work, results and provider boundaries
A request to a Bud or coding agent can contain more than its visible prompt. Depending on the workflow, relevant authorized conversation history, project files, approved meeting text and retrieved connector evidence can be transmitted. Access controls and context settings determine eligible sources; an account’s ability to view a source is not a promise that every source will be included in every request.
Bud names, role, personality instructions and reporting preferences influence how work is presented. A configurable avatar is a visual identity, not a separate privacy boundary or a claim that the assistant is human. Generated outputs can reproduce or summarize personal information in the input and can be incorrect. Review an output’s audience before posting it to a wider channel, exporting it or approving an external action.
A local coding runtime may send project or prompt information to its provider according to that runtime’s configuration. Aedrova’s hosted-model retention settings do not automatically apply to your separately configured runtime account. We cannot guarantee the accuracy of a provider’s output, its availability or the handling of data outside our instructions and contractual control. Contact us before using a feature that requires a specific provider retention setting or contractual safeguard.
For eligible context exclusions or meeting withdrawal, future use is restricted through the supported controls. Already delivered messages, completed model requests, user copies and independently retained provider records are separate. A request to stop future AI use is not automatically a deletion request for the underlying conversation or original file.
17. Communications and your preferences
Waitlist registration authorizes the launch updates described at registration. You can withdraw that choice by requesting removal from the registered address. Necessary security, account, privacy or billing communications may still be sent when relevant to an active service relationship or a legal obligation. We do not make receiving unrelated promotions a condition of exercising a privacy right.
When email delivery includes an unsubscribe option, use it to stop that optional category. You can also contact support. Messages from your organization or an independently connected provider are governed by that sender’s settings. Turning off a local notification does not delete the related message or change whether a provider processes an authorized task.
18. How retention is determined
Retention depends on the data category, whether the feature is active, your organization’s instructions, the reason for processing and applicable obligations. We consider whether a record remains necessary to deliver requested work, whether it is needed to resolve an incident or payment dispute, and whether a lawful deletion or preservation request applies. We do not retain data indefinitely merely because storage is available.
- Waitlist: registrations are configured with a one-year expiry; verified earlier removal is available through support. Expiry and maintenance govern active registration records, while backups have separate handling.
- Sessions and temporary state: authentication, OAuth and other temporary records have their configured expirations. Browser state and an expired server session may have different lifetimes.
- Managed inference response cache: backend maintenance clears cached response content after its 24-hour window. Usage/monetary accounting can remain. This rule is not a 24-hour deletion promise for chat history, all provider records or saved build results.
- Saved meeting text: the supported shared-text window is currently 30 days where enabled, subject to earlier withdrawal/deletion controls and actual maintenance. Provider-held audio/text and backup copies are distinct.
- Chat, files, voice messages and build records: these can persist for collaboration and history until the relevant supported removal or verified scoped request is completed. Removing a local attachment preview does not necessarily remove its hosted file.
- Connections: stored grants are used while authorized and are removed from active use when disconnected. Original-service data and other independently granted connections remain separate.
- Billing, fraud prevention, legal holds and fulfillment records: limited information may be retained to meet legal obligations, document transactions or requests, or handle actual disputes and security incidents.
There is currently no universal automatic account/workspace erasure timer or one-click full export/deletion feature. Support reviews such requests and explains scope and exceptions. We will not describe an administrative access expiry as verified physical deletion from every system. A backup restoration must also account for approved removals; backup retention and provider obligations should be reviewed before relying on a specific deletion deadline.
19. Identity verification, scope and request handling
Use the contact information below or Data requests and explain the action you want, the account/registration address and the relevant workspace. You do not need to pay for a plan to make a privacy request. We may use your authenticated account, the existing registered address or proportionate additional confirmation to avoid disclosing or erasing someone else’s information.
We seek only the information necessary to verify the request. Do not send passwords, access tokens, full payment details or identity documents in ordinary email. If a stronger check is genuinely required, we will discuss an appropriate secure method. Verification material is used for the request and related security purposes, not unrelated marketing.
A request can involve information controlled by your organization. We may need to coordinate with its authorized administrator and distinguish your personal account from shared business records. A member’s request does not authorize disclosure of another member’s private content or deletion of an unrelated workspace. A portable copy, where required, is subject to applicable scope and other people’s rights; it is not automatically a full database backup or proprietary source-code export.
We respond within the period required by applicable law and explain any permitted extension, refusal, retention exception or appeal path. Where a request is manifestly unfounded or excessive, a refusal or reasonable fee is possible only as permitted by applicable law and with an explanation. We do not impose a blanket request fee. A representative must show authority; where required, we also verify the individual’s identity or direct permission.
20. Additional regional information
California and other US states
When a relevant law applies, available rights may include knowing categories and specific information, correction, deletion, portability, opting out of sale/sharing or certain targeted advertising/profiling, limiting specified sensitive-information use, and non-discrimination for exercising those rights. The category, source, purpose and recipient descriptions in this policy explain our current practices; listed optional features do not mean every category was collected from every person in a particular reporting period.
We do not currently sell personal information or share it for cross-context behavioral advertising, and do not operate an optional advertising-consent program or offer payment for surrendering privacy rights. We do not use sensitive information for unrelated advertising or profiling. An opt-out preference signal does not need to stop a practice we do not engage in; if our practices change, we will provide required notices and applicable signal/choice handling before enabling that practice.
Contact support to exercise an applicable right or appeal a denied request. We will identify any applicable appeal process and regulator route when responding. We have not represented that every state privacy statute applies to this business; eligibility, exceptions and deadlines depend on the law and actual operation. An employer’s separate personnel/privacy obligations are not replaced by this policy.
European Economic Area, United Kingdom and other jurisdictions
Where the relevant rules apply, rights can include access, correction, erasure, restriction, portability, objection and withdrawal of consent. Consent withdrawal does not invalidate lawful processing before withdrawal. For processing based on legitimate interests, explain your circumstances when objecting; applicable balancing and statutory exceptions may affect the outcome. You may complain to the competent supervisory authority, including one in your habitual residence, workplace or place of the alleged infringement where the law provides.
Our stated legal bases explain service, consent, security and legal-obligation purposes. Information received from teammates, organizations, sign-in and connected services is described in this policy as well as information supplied directly. International processing may require additional contractual or statutory safeguards; an applicable representative, specific transfer mechanism or signed data-processing agreement is not established merely by publishing this page. Contact us before using Aedrova for an organization that requires those arrangements.
21. Security, access and incidents
We use authenticated access, workspace/channel permissions and backend checks intended to limit unauthorized access. Credentials and sensitive backend records use protected storage in supported configurations. Authorized services must still process readable data to perform their tasks; the product is not represented as end-to-end encrypted. No encryption, rate limit, review or testing process guarantees that an incident cannot occur.
Users and administrators should protect sign-in accounts, review team access and grants, avoid posting secrets, and promptly report unexpected access. Do not investigate by reading additional private data or disrupting service. Our security reporting page describes a safe reporting path. We investigate relevant incidents and make notifications required by applicable law, contractual commitments and the circumstances; applicable notification periods depend on the incident and law, and this policy does not establish a public uptime SLA.
22. External links, independent services and organizational copies
Provider authorization pages, payment pages, repositories, design tools, social platforms and links posted in chat may be operated independently. Their notices apply to their own collection and use. Disconnecting Aedrova is different from closing a provider account, revoking every provider grant or deleting content created in that service.
Teammates may independently download files, take notes or receive notifications. Your organization may maintain separate records. We cannot erase those copies by deleting one hosted message. Aedrova’s policy describes our handling, not a guarantee that every recipient will comply with your organization’s rules. Share content only with the intended audience and use the appropriate private channel or authorization scope.
23. Children and age eligibility
Aedrova is a team-workspace product and is not directed to children under 13. They may not register or supply personal information. If you believe a child has submitted information, identify the relevant account/content through support without unnecessarily distributing additional information about the child. We will investigate and take appropriate removal or restriction steps.
For users who are minors but otherwise eligible under local law, a parent or guardian’s authorization may be necessary to accept the service terms. We do not deliberately solicit children’s sensitive data, sell their information or use it for cross-context advertising. This clause does not make the product a child-directed service or establish compliance for every school or child-data use case.
24. Business changes and legally required disclosures
A merger, acquisition, financing, reorganization or transfer of relevant assets may involve personal information, subject to appropriate confidentiality and applicable law. We will provide notice when required and do not treat a business change as permission to ignore existing privacy commitments or use content for an incompatible purpose without the required basis.
When responding to legal process or a credible security concern, we seek to disclose information relevant to the request or purpose rather than unrelated workspace content. Law may restrict notification or require preservation. We do not promise never to disclose data to authorities, nor does a general legal-process clause authorize another customer to obtain your private records.
Launch-email opt-out links contain an encrypted, purpose-bound registration reference. Opening a link does not unsubscribe you until you confirm. A minimal suppression record is retained for up to ten years to prevent further optional launch mail; it does not contain your raw email. Exported mailing lists must be regenerated before sending so suppressions apply. Opting out does not delete a workspace or stop essential account notices. You may also contact support to unsubscribe or request deletion.
25. Changes and contact
We update this policy when our practices change and show the effective date above. Material changes will be communicated through the website or account contact information where appropriate. Our current contact details are on Customer support.