Legal
Privacy Policy
Last updated: 5 September 2026Effective: 5 September 2026
This policy explains what personal data Didit collects when you use ai-cmo.dev (the “Service”), why we collect it, who else processes it and what rights you have. It is written for the people who open accounts, for their team members and for visitors to the marketing site. Questions go to privacy@ai-cmo.dev.
1. Who we are and how to reach us
Didit operates ai-cmo.dev and is the controller for the personal data described in this policy, except where we act as your processor (see the note at the end of this section). We haven’t appointed a data protection officer; the privacy contact below handles every request.
- Entity
- Didit
- Registered address
- Available on request at privacy@ai-cmo.dev
- Privacy contact
- privacy@ai-cmo.dev
- Support contact
- hello@ai-cmo.dev
When you bring personal data about other people into the Service, for example contacts in a connected analytics account, leads in a brief or names in a draft, you decide why and how that data is processed and we process it on your instructions as your processor. If your use requires a data processing agreement, write to the privacy contact above and we will put one in place.
2. The data we collect
We collect only what the Service needs to work. The categories below describe what that is and where it comes from. Your email address and a password are necessary to enter into the contract with us: without them you can’t create an account or use the Service. The other categories are collected only when you use the feature that needs them, and that feature won’t work without them.
Account data
Your email address, display name and password. Passwords are stored as scrypt hashes, never in clear text. When you log in with a one-time code, the code is stored hashed and expires within minutes. For each session we keep a session row with the IP address and browser user agent that opened it, so that you can see and revoke sessions and so that we can detect abuse.
Billing data
Your plan, credit balance, invoices, credit transactions and the Stripe customer and subscription identifiers. Card numbers never reach our servers: Stripe collects and stores them. Financial records are kept in pseudonymised form for the period tax law requires.
Connector data
When you connect a third-party account we store the OAuth tokens or credentials needed to act on your behalf, basic identifiers that confirm which account is connected (such as an account id or property name), and the data the connected service returns when an Agent uses it: search performance from Google Search Console, traffic from Google Analytics, campaign data from Google Ads (adwords scope only), repository and pull-request metadata from the GitHub App, posts and engagement from X, LinkedIn and Reddit, backlink data from Ahrefs, and event deliveries to webhooks you register. Reddit and Ahrefs credentials are stored with access controls; encryption at rest is being extended to them.
Site, crawl and competitor data
The pages, sitemaps, metadata, performance scores and structured data of the Sites you add, together with the public pages and public AI answers the Research and GEO Agents collect about competitors you name. Crawled pages can contain personal data published on those pages, such as author names or contact details. We process it only to produce your analysis.
Content you create
Briefs, documents, brand details, instructions to Agents, drafts you edit and the decisions you take in the Review Queue. Public workspace pages under /p/ contain whatever you choose to publish there.
Usage, device and log data
Agent runs, credit usage, feature interactions, API and MCP calls (with the key id, timestamp, endpoint and status), error reports and server logs that carry your IP address and user agent. Error reports go to Sentry with personal identifiers disabled.
Support and communications
Emails you send to our support or privacy addresses, and the transactional emails we send you (codes, receipts, digests, notices) with their delivery status.
We don’t ask for, and you should not upload, special categories of personal data such as health, political or biometric data.
3. Why we process it and on what legal basis
Under the General Data Protection Regulation (GDPR) we need a legal basis for every purpose. This table lists them.
| Purpose | Data used | Legal basis |
|---|---|---|
| Creating and securing your account, sending login codes, keeping sessions | Account data, session rows | Contract (Art. 6(1)(b)); legitimate interest in security (Art. 6(1)(f)) |
| Running the Agents: crawling, analysis, drafting, measuring AI visibility | Site, crawl and competitor data; content you create; connector data | Contract (Art. 6(1)(b)) |
| Publishing what you approve to connected channels and webhooks | Connector data, content you create | Contract (Art. 6(1)(b)) |
| Billing, invoicing, credit accounting and fraud prevention | Billing data, usage data | Contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)); legitimate interest in preventing fraud (Art. 6(1)(f)) |
| Transactional email: receipts, notices, security alerts, digests you enabled | Account data | Contract (Art. 6(1)(b)); legitimate interest in keeping you informed (Art. 6(1)(f)) |
| Debugging, error monitoring and abuse prevention | Usage, device and log data | Legitimate interest in a reliable and safe service (Art. 6(1)(f)) |
| Analytics on the marketing site, only where a Google Analytics tag is configured | Cookies and usage data | Legitimate interest in understanding how the marketing site is used (Art. 6(1)(f)) where the law allows analytics without consent; consent (Art. 6(1)(a)) in the EEA, the UK and any other jurisdiction that requires it, where the tag stays off until a consent control exists |
| Answering support and privacy requests | Support and communications | Contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)) |
| Complying with tax, accounting and other legal duties, and defending claims | Billing data, account data | Legal obligation (Art. 6(1)(c)); legitimate interest in establishing or defending legal claims (Art. 6(1)(f)) |
Where we rely on legitimate interest, we have weighed it against your interests and rights, and you can object at any time (see Your rights). We don’t make decisions about you that have legal or similarly significant effects by automated means alone, and we don’t sell personal data.
4. How AI models process your data
The Agents send prompts and context to large language models through OpenRouter, which routes each request to the model provider we select for that task: Google (Gemini), Anthropic (Claude) or DeepSeek models. Search and crawl steps use Exa and Firecrawl. A prompt can include excerpts of your Site, your brief, connector data the Agent needs and public information about competitors.
We send only what the task needs and we do not use your data to train models. The providers process the request to return an answer under their own API terms, which also govern whether they retain the request or use it to train their own models; we don’t control either. See the sub-processor table for regions. Output comes back to your workspace and stays there until you delete it.
Output can be inaccurate or incomplete and can contain statements about identifiable people, for example an author of a competitor’s page. Nothing is published without a person approving it in the Review Queue, and you remain responsible for reviewing any personal data in what you approve.
7. International transfers
The Service runs in the European Union. Several providers in the table above are established in the United States, so personal data can be transferred outside the European Economic Area. For those transfers we rely on the European Commission’s Standard Contractual Clauses, entered into with each provider, together with the supplementary measures those providers offer, such as encryption in transit and at rest and the sending of only the data a task needs. Google Analytics data about visitors from the European Economic Area or the United Kingdom is transferred to Google in the United States only after those visitors have consented to analytics, and only under the Standard Contractual Clauses or whichever transfer tool applies at the time.
You can ask the privacy contact for a copy of the safeguards that apply to a specific provider. Connected platforms you authorise may process data in their own regions under their own terms.
8. How long we keep data
We keep personal data only as long as it serves the purpose it was collected for, after which we delete or anonymise it. The schedule below applies unless a legal hold or a dispute requires a longer period.
| Data | Retention |
|---|---|
| One-time login codes | Minutes: each code expires after its short validity window and is then purged |
| Session rows and the session cookie | 30 days from creation, or immediately on logout or revocation |
| Account data | For the life of the account, then deleted within 30 days of an account deletion request |
| Workspace, Site, crawl, competitor and content data | Until you delete the Site or workspace from its danger zone, or the account is deleted |
| Connector tokens and credentials | Until you disconnect the Connector or delete the workspace; deletion revokes access at the provider first and removes local data once every revocation is confirmed |
| Deletion audit trail (what was deleted, when, by whom) | 400 days |
| Invoices, credit transactions and other financial records | 7 years, pseudonymised, to meet tax and accounting law |
| Server logs and error reports | Only as long as debugging and security need them, then deleted; Sentry error events expire under its retention setting |
| Support and privacy correspondence | Until the request is closed and afterwards for as long as reasonably necessary to evidence how it was handled |
| Transactional email delivery records | As held by Postmark under its retention settings, then deleted |
Backups are subject to periodic rotation. They exist for disaster recovery only and are not a restoration service available to customers.
9. How we protect data
We apply technical and organisational measures proportionate to the risk. Among them:
- encryption in transit (TLS) for every connection to the Service, the API and the sub-processors
- passwords hashed with scrypt; one-time codes stored hashed with a short time-to-live; session cookies signed with an HMAC
- API keys stored encrypted at rest with AES-GCM and scoped to the permissions you choose; Google Ads tokens and webhook signing secrets encrypted with AES-256-GCM
- Reddit and Ahrefs credentials stored with access controls; encryption at rest is being extended to them
- rate limiting, enumeration resistance on login and signup, and outbound signing of webhook deliveries
- hosting on a shared AWS platform in Ireland (eu-west-1) with restricted administrative access, monitored spend limits and error tracking without personal identifiers
- revoke-first deletion for Connectors, so no credential is left behind on a provider after you delete a workspace
No system is perfectly secure. If we learn of a breach that affects your personal data, we will notify you and, where required, the supervisory authority without undue delay and within the deadlines the GDPR sets. Please report security concerns to hello@ai-cmo.dev.
10. Your rights
Under the GDPR and equivalent laws you can ask us to:
- access the personal data we hold about you and receive a copy
- rectify data that is inaccurate or incomplete
- erase your data, subject to the retention we must keep by law
- receive the data you provided in a portable, machine-readable format
- restrict processing while a dispute about accuracy or lawfulness is resolved
- object to processing based on legitimate interest, and to any direct marketing
- withdraw consent at any time where consent is the basis; this doesn’t affect processing that already took place
To exercise a right, email privacy@ai-cmo.dev from the address on your account so that we can verify it is you. We respond within 30 days; if a request is complex we may extend that by up to two further months and will tell you why. Requests are free unless they are manifestly unfounded or excessive.
Inside the Service you can already: update your display name and password, review and revoke sessions, rotate and revoke API keys, disconnect Connectors, and delete Sites and workspaces from their danger zone. Self-serve account deletion and data export are not available in the product yet; email the privacy contact and we will complete either within 30 days.
If you believe we process your data unlawfully, you can lodge a complaint with a supervisory authority. Our lead authority is the Agencia Española de Protección de Datos (AEPD); you can also complain to the authority of the country where you live or work.
11. Google API Services disclosure
The Service’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.
In practice this means that data from Google Search Console, Google Analytics and Google Ads is used only to provide and improve the features you asked for inside your workspace: search and traffic analysis, recommendations and, for Google Ads, campaign management under the adwords scope. We don’t use Google user data for advertising, we don’t sell it, we don’t transfer it to third parties except sub-processors needed to run the feature or where required by law, and no human reads it except with your consent, for security or abuse investigation, or to comply with the law. Data sent to AI models is limited to what a specific analysis needs. You can disconnect Google from the connections settings at any time, which revokes our access.
12. Children
The Service is for businesses and is not directed at anyone under 18. We don’t knowingly collect personal data from children. If you believe a child has opened an account, contact the privacy address and we will delete it.
13. Changes to this policy
We update this policy when the Service, our providers or the law change. The date at the top of the page shows the current version. For material changes, such as a new purpose or a new category of sub-processor with access to your content, we will email the address on your account or show a notice in the product before the change takes effect.
14. Contact
For any question about this policy or your data, write to privacy@ai-cmo.dev. General support is at hello@ai-cmo.dev.
This document is the English original. Where a translated version differs, the English text governs. Read it together with the Terms of Service.