Effective date: October 29, 2026
Last updated: October 29, 2026
This Privacy Policy explains how Aecaro ("Aecaro," "we," "us") collects and uses personal data when you use www.aecaro.com and the Aecaro platform (the "Service"). It applies to you as the account owner and, where relevant, to people whose information passes through your connected accounts (e.g. people you email, meet with, or message through a coworker).
If you're in the UK or EEA, we process your data as described below under UK GDPR / EU GDPR, and Section 7 sets out your rights.
Account information. Name, email, and authentication identifiers, via Clerk (our sign-in provider). If you're an agency/reseller, also your company name and billing address.
Connected-account data. When you connect an account (Gmail, Google Calendar, Google Drive, Google Sheets, Slack, LinkedIn, and others we support) via OAuth through Composio or Nango, your coworkers can read and, depending on the autonomy level you set, act on data in that account — emails, calendar events, files, messages. We store the minimum copy needed for a coworker to act on it (e.g. extracted facts, commitments, or summaries) rather than mirroring the whole account.
Knowledge-base files. Documents, notes, and other files you give a coworker to work from.
Voice notes. If you send a coworker a voice message (in the app or via Telegram), the audio is sent to Aecaro's own transcription service, running on our own infrastructure — not a third-party speech vendor — converted to text, and the text is kept as part of your conversation. The audio itself is processed in memory and is not written to disk or stored once transcription completes or fails.
Billing data. Handled by Stripe. We receive your plan tier, billing status, and payment history from Stripe — never your full card number.
Logs and technical data. IP address, browser/user-agent, session timestamps, and execution/error logs, kept for security monitoring, abuse prevention, and debugging. Execution traces, activity events, and webhook logs are automatically deleted after 90 days.
We do not sell your personal data. We do not use your content, including the content of your connected accounts and knowledge base, to train models, and we do not allow third parties to do so on our behalf.
To generate a coworker's or Aeco's response, the relevant prompt (which may include information read from your connected accounts or knowledge base) is sent to the AI model provider configured for that coworker. Depending on which model you or we select, that may be:
If you supply your own API key for a provider, your requests go to that provider under your own account with them.
Each provider processes that data under its own terms and privacy policy, and may retain it briefly for abuse monitoring per their own policies. We send requests through the providers' commercial API interfaces, not their consumer products, but we do not control their practices, so check each provider's current terms for specifics.
We share data with the following categories of providers, each only to the extent needed to run the Service:
| Category | Provider | What it gets |
|---|---|---|
| Hosting (app) | Vercel | Serves the web app; sees request/traffic metadata |
| Database | Neon | Stores account data, settings, and execution metadata (PostgreSQL) |
| Servers (agents, voice) | Hetzner | Runs coworker containers, the browser sandbox, code runner, and our self-hosted voice service |
| Sign-in | Clerk | Authentication, MFA, session management |
| Payments | Stripe | Billing, subscriptions, payment method tokens |
| Account connections | Composio, Nango | OAuth brokering for connected apps (Gmail, Calendar, Slack, etc.) |
| Messaging | Telegram | Only if you connect it — delivers/receives messages to your coworkers |
| Resend | Transactional email (receipts, account notices) | |
| Web search | Brave Search, Tavily, DuckDuckGo | Search queries a coworker makes when it looks something up on the web |
| Analytics | PostHog | Product usage analytics (only when enabled) |
| Error monitoring | Sentry | Crash/error reporting for reliability |
| AI inference | Anthropic, OpenAI, Google, DeepSeek, Groq, Mistral, and the additional options in Section 4 | Generate coworker/Aeco output (see Section 4) |
We don't promise a particular data-residency region. We may add or replace providers; we'll update this table and, for material additions, notify you by email.
If you disconnect a connected account (Gmail, Calendar, etc.) — from the Connectors page, by removing a single connection, or by asking a coworker to disconnect it — Aecaro revokes the OAuth token and deletes the data we had copied out of that account (for example, extracted facts or calendar commitments used by the look-around/attention features). Revoking access revokes the data, not just the connection.
If you're in the UK/EEA (and we extend the same rights to everyone, regardless of location), you can:
To exercise these rights, contact hello@aecaro.com. We'll respond within 30 days.
When you delete your account:
Aggregate, de-identified analytics may be kept indefinitely since they no longer identify you.
We use essential cookies for sign-in (Clerk) and payments (Stripe). We don't use advertising cookies. When product analytics (PostHog) is switched on, it counts page views using a pseudonymous identifier kept in your browser's local storage, not in a cookie.
The Service is intended for business use by adults. You must be at least 18 to use it, and we don't knowingly collect data from children. If you believe a child has given us data, contact hello@aecaro.com and we will delete it.
Aecaro's providers, including Vercel, Stripe, and the AI model providers, may process data in the United States and other countries outside your own. Where the law requires a transfer mechanism, we rely on the provider's data-processing terms, which generally incorporate Standard Contractual Clauses or equivalent safeguards. If you need a data processing agreement, contact us at hello@aecaro.com.
We'll post updates here and, for material changes, notify you by email at least 30 days before they take effect.
Privacy questions or data-subject requests: hello@aecaro.com. We have not appointed a data protection officer.
Portions of this document are adapted from the Basecamp open-source policies (https://github.com/basecamp/policies), © 37signals, used under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Changes were made. Aecaro's version is likewise offered under CC BY 4.0.