Legal

Privacy Policy

Effective date: October 29, 2026

Last updated: October 29, 2026


1. Who this is about

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.

2. What we collect

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.

3. Why we use it

●To run the Service: deploy and run your coworkers, execute jobs on schedule, give Aeco context, keep your knowledge base, and send you notifications (including via Telegram, if connected).
●To bill you, via Stripe.
●To secure the platform: detect abuse, unauthorized access, and fraud.
●To improve the product, using aggregate, de-identified usage patterns — not the content of your connected accounts.
●To comply with legal obligations.

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.

4. Where coworker output goes: AI model providers

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:

●Anthropic
●OpenAI
●Google
●DeepSeek
●Groq
●Mistral
●xAI, OpenRouter, Together AI, Fireworks AI, and Perplexity (available as additional options)

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.

5. Other service providers (sub-processors)

We share data with the following categories of providers, each only to the extent needed to run the Service:

CategoryProviderWhat it gets
Hosting (app)VercelServes the web app; sees request/traffic metadata
DatabaseNeonStores account data, settings, and execution metadata (PostgreSQL)
Servers (agents, voice)HetznerRuns coworker containers, the browser sandbox, code runner, and our self-hosted voice service
Sign-inClerkAuthentication, MFA, session management
PaymentsStripeBilling, subscriptions, payment method tokens
Account connectionsComposio, NangoOAuth brokering for connected apps (Gmail, Calendar, Slack, etc.)
MessagingTelegramOnly if you connect it — delivers/receives messages to your coworkers
EmailResendTransactional email (receipts, account notices)
Web searchBrave Search, Tavily, DuckDuckGoSearch queries a coworker makes when it looks something up on the web
AnalyticsPostHogProduct usage analytics (only when enabled)
Error monitoringSentryCrash/error reporting for reliability
AI inferenceAnthropic, OpenAI, Google, DeepSeek, Groq, Mistral, and the additional options in Section 4Generate 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.

6. Disconnecting an account erases what we copied from it

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.

7. Your rights

If you're in the UK/EEA (and we extend the same rights to everyone, regardless of location), you can:

●Access a copy of the personal data we hold about you.
●Correct inaccurate data, via your account settings or by asking us.
●Delete your account and associated data.
●Export your data in a machine-readable format before deletion.
●Object to processing based on legitimate interest, and withdraw consent where processing relies on it.
●Complain to your local data-protection authority (e.g. the ICO in the UK) if you think we've mishandled your data.

To exercise these rights, contact hello@aecaro.com. We'll respond within 30 days.

8. Deleting your account

When you delete your account:

●Your coworkers and running jobs are stopped immediately, and your active subscription is cancelled with the payment provider.
●Your account data, connected-account copies, knowledge base, chat history, job history, and billing-linked records are deleted promptly and in any case within 30 days of your request. If you instead cancel your subscription, your data is kept for 30 days and then deleted. Security and audit logs tied to your account are kept for up to 90 days after deletion and then purged.
●Some records may be kept longer where the law requires it (e.g. financial records for tax purposes, typically 6–7 years).

9. Retention, generally

●Account data, connected-account copies, knowledge base, and chat/job history: kept while your account is active, and deleted within 30 days of account deletion (Section 8).
●Execution traces, activity events, and webhook logs: automatically deleted after 90 days.
●Audit log: kept while your account is active, and purged 90 days after account deletion.
●Backups: rotate out within 90 days of deletion.

Aggregate, de-identified analytics may be kept indefinitely since they no longer identify you.

10. Cookies

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.

11. Children

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.

12. International transfers

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.

13. Changes to this policy

We'll post updates here and, for material changes, notify you by email at least 30 days before they take effect.

14. Contact

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.