Privacy Policy

Last updated: September 3, 2026

1. Who we are

Mother is an autonomous marketing operator. You give it a brand; it researches, writes, generates images and video, publishes to the accounts you connect, measures what happened, and learns from your edits.

Mother is operated by [COUNSEL: registered company name and legal form], [COUNSEL: company registration number], of [COUNSEL: registered address] ("we", "us"). We are the data controller for the account data described in section 2. For the brand data you and your team put into the product, you are the controller and we act as your processor — see the Data Processing Agreement.

[COUNSEL: whether a Data Protection Officer or an EU/UK representative is required, and their contact details if so]

2. What we collect

• Account and sign-in data. Your name, email address and authentication state. Sign-in is handled by Clerk; we do not see or store your password.
• Organisation and membership data. Which organisation and brands you belong to, and your role in each (for example admin or viewer). Roles decide what the agent will do on your behalf.
• Brand data. Everything that defines a brand in Mother: the brand's name and website, the brand instructions ("Brand Instructions"), voice and style notes, palettes, products, uploaded files and reference images.
• Content and conversations. Chat sessions with the agent, drafts, campaigns, scheduled work, workflow definitions and their runs, and the generated text, images and video that come out of them.
• Crawled website content. When you onboard a brand we fetch pages from the website address you give us, to ground the brand brain in the brand's own words. We crawl the site you nominate, not the wider web.
• Connected-account data. For each social or commerce account you connect, the account identity (handle, page or profile id), the posts Mother published, the metrics those posts accrued, and inbound comments, mentions and messages on them. Access tokens for those accounts are held by the connection broker and are never exposed to the model.
• Email data. Sender identity for your brand (from name, from address, reply-to, verified sending domain), the emails Mother sends on your behalf, recipient addresses you supply, and replies received at a brand inbound address you enable.
• Memory data. A per-brand log of what happened and what was learned — the events themselves, plus embeddings derived from them and a graph projection built over them. This is how the brand brain compounds instead of resetting.
• Technical data. Request logs, error reports, and IP address, used for security, rate limiting and debugging.
• Analytics data. Aggregated page and product usage. On this website, analytics load only after you accept analytics cookies — see the Cookie Policy.
• Billing data. The commercial details needed to invoice you, and where a subscription is billed through Stripe, a Stripe customer reference. We do not receive or store card numbers.

3. Why we use it

• To run the product you asked for: research, generation, approval, publishing, measurement and reply.
• To ground the agent in your brand, so its output is yours and not generic — this is what the brand instructions, the elements and the memory layer are for.
• To improve your brand's results over time by learning from your edits, approvals and rejections.
• To send you transactional email: notifications, approval requests, alerts and account messages.
• To keep the service secure and available, and to debug it when it breaks.
• To bill you and to meet our own legal obligations.

We do not train models on your brand data. What Mother learns from your brand is stored against that brand and used for that brand. Your content is sent to the model providers listed in section 6 to produce a result, and comes back. [COUNSEL: confirm each model provider's training and retention terms before we state anything on their behalf]

4. Legal basis

Where the GDPR applies, we rely on: performance of a contract for everything needed to deliver the service; legitimate interests for security, abuse prevention and product improvement; consent for analytics cookies and any marketing email; and legal obligation where the law requires us to keep or disclose something. [COUNSEL: confirm the legal-basis mapping and add any local-law bases required in the jurisdictions we sell into]

5. Where your data lives

• Application and database: hosted on Vercel, with functions pinned to the Frankfurt region (fra1), and a managed Postgres database with Neon in the EU (Frankfurt).
• Per-brand isolation: brand data is separated at the database layer by row-level security. A request carries one brand's identity and can only read and write that brand's rows. See the Security Policy.
• Media: images and video are stored in Cloudflare R2 object storage.
• Memory: the event log lives in the same EU Postgres database. The graph projection built over it runs on our own self-hosted service in the EU.

6. Who processes it

We use the following sub-processors. Each has its own privacy terms; we list what they do for us, not what they promise.

• Clerk — sign-in, sessions, organisations and users.
• Vercel — application hosting and serverless functions (Frankfurt), plus the AI Gateway that routes model calls.
• Neon — managed Postgres, EU region.
• Cloudflare — R2 object storage for media.
• Resend — sending transactional and brand email, and receiving inbound replies.
• Zernio — connecting social accounts, publishing posts, fetching metrics, and retrieving inbound comments and messages.
• Luma and Seedance — image and video generation.
• DataForSEO — search and keyword data.
• Anthropic, OpenAI and Google — the model providers reached through the Vercel AI Gateway for text generation, extraction and embeddings.
• Sentry — error monitoring.
• PostHog — product analytics.
• Upstash — rate limiting.
• Stripe — payment processing, where your subscription is billed through it.
• Fly.io — hosting for two services we run ourselves: the website crawler used at onboarding, and the memory-graph service.

Separately, when you connect an account — a social network, a shop, a CMS — Mother sends content to that platform on your instruction. Those platforms are recipients of your data under their own terms, not our sub-processors.

7. International transfers

We host in the EU. Some sub-processors above are established outside the EEA or process data there. [COUNSEL: confirm the transfer mechanism relied on for each non-EEA sub-processor (SCCs, adequacy, or the EU–US Data Privacy Framework) and whether a transfer impact assessment is needed]

8. How long we keep it

We keep brand data for as long as the brand exists in Mother. It is deleted when the brand is deleted or when you ask us to delete it. The product does not currently expire brand content, memory or generated media on a timer.

Account data is kept while your account is open. Operational logs and error reports are kept for as long as they are useful for security and debugging, then discarded. [COUNSEL: set explicit retention periods for account data, logs, backups and billing records, including any statutory minimum]

9. Your rights

Depending on where you live, you may have the right to access, correct, export, delete or restrict the personal data we hold about you, to object to certain processing, and to complain to your data protection authority.

Here is what the product offers today, honestly: you can read and edit brand instructions, content, drafts and connections in the app, and disconnect any connected account yourself. There is no self-service "export everything" or "delete my account" button yet. Access, export and deletion requests are handled by us manually — contact us and we will action them. [COUNSEL: the response deadline we commit to, and the identity-verification step for a rights request]

10. Automated decisions and AI output

Mother generates content and can act on a schedule. It does not make decisions that produce legal effects about people. Generated content can be wrong, and it is published under your accounts — approvals, autonomy and pause are yours to set, and reviewing what goes out is your responsibility. See the Terms of Service.

11. Cookies

This website sets essential cookies always, and analytics cookies only with your consent. You can change or withdraw that consent at any time. Full detail in the Cookie Policy.

12. Changes to this policy

We will update this policy as the product changes. If a change is material we will tell you before it takes effect. [COUNSEL: notice period for material changes]

13. Contact

Reach us through the contact form, or by email at [COUNSEL: the privacy contact address to publish]. Postal address: [COUNSEL: registered address].