Meta-Me
Sign in

Privacy Policy

Last updated: 30 July 2026

1. Who we are

Meta-Me is a personal-tools platform operated by Joe Jarlett, a sole-trader based in the United Kingdom. The data controller for the purposes of UK GDPR is Joe Jarlett, contactable at [email protected].

2. What we collect

2.1 Information you give us

  • Account data: name, email address, profile picture (if you sign in with Google).
  • Content you create: anything you put into the apps you use (knowledge base entries, contacts, transactions, health data, journal entries, etc). The exact data category depends on which apps you use.
  • Feedback and contact form submissions: the message you send and the email address you provide.
  • Payment details: when you subscribe, payment is processed by Stripe. We never see or store your card number; we only store the Stripe customer ID and subscription status.
  • Connected Google accounts: if you choose to connect one, the authorisation to read and act on your Gmail, Calendar, Tasks and Drive. Optional, off by default, and covered in detail in section 3.

2.2 Information we collect automatically

  • Authentication cookies: a single session cookie scoped to .meta-me.uk, set when you sign in.
  • Analytics events: page views, navigation duration, and a small set of custom events. No cookies, no IP retention, no third-party trackers. Visitors are counted using a hash of IP and browser combined with a salt that is randomly generated each day and destroyed at the end of it — so once a day has passed the events cannot be traced back to a person, by us or anyone else. The infrastructure is first-party at analytics.meta-me.uk.
  • Operational logs: request paths, status codes, and error traces for debugging.

2.3 What we don't collect

  • No third-party advertising trackers, no Google Analytics, no Facebook pixels.
  • No cross-site cookies. Our session cookie is first-party only.
  • No location data beyond what you explicitly add to an app.

3. Connected Google accounts

Connecting a Google account is optional and off by default. None of what follows happens unless you explicitly connect an account at /settings/integrations/google, and access is granted one feature at a time — connecting Calendar does not give us access to your mail.

3.1 What we ask for, and why

  • Gmail (gmail.modify): search and read your inbox when you ask Meta-Me to find or open a message, send and draft messages on your behalf, and move a message to the trash when you ask.
  • Calendar (calendar.readonly, calendar.events): read your agenda and create the events you ask for.
  • Tasks (tasks): list, add and complete your tasks.
  • Drive (drive.file, drive.readonly): list and read your files, upload documents Meta-Me generates, and import a document you choose into another app such as the Knowledge Base.

3.2 What we store

  • Authorisation tokens: the refresh and access tokens Google issues, held server-side in the platform database so the features keep working without you re-authorising every time.
  • Account identifiers: your Google account ID, email address, verified send-as aliases, and the short name you give the account.
  • An access log: one row per request we make to Google — timestamp, which app asked, the method and path called, which account was used, the from-address for sends, whether it succeeded and how long it took. This records that we called Google, not what came back.

3.3 What we don't store

The contents of your mail, calendar, tasks and Drive files are fetched from Google when a request needs them, used to answer that request, and not retained afterwards. The exception is content you deliberately import: if you import a Google Doc into the Knowledge Base, a copy is stored there as one of your documents and follows that app's retention rules.

3.4 Other people's data

Your mailbox and calendar contain personal data belonging to people who are not Meta-Me users — senders, recipients, attendees. We fetch it only in response to something you ask for, we do not scan your account in the background, and we do not use it to build profiles or train models. Where answering your request involves passing such content to an AI provider, the AI-processing terms below apply to it.

3.5 Withdrawing access

Disconnect any account at /settings/integrations/google. Disconnecting revokes the authorisation at Google and deletes the stored tokens, account name and aliases from our database. You can also revoke Meta-Me directly from your Google account permissions page. The legal basis for all Google Workspace processing is consent (UK GDPR Article 6(1)(a)).

3.6 Limited Use

Meta-Me's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer this data to others except as needed to provide the features you use, do not use it for advertising, do not sell it, and do not allow humans to read it except with your explicit consent, for security or legal reasons, or where it has been aggregated and anonymised.

4. Where it lives

  • Application database: PostgreSQL on a self-hosted Mac mini in the UK. Daily off-site encrypted backups.
  • Stripe: payment processing, customer records, subscription state. Stripe is the data processor for payment data.
  • Cloudflare: DNS only (DNS-only mode, not proxied).
  • Email (Gmail SMTP): outbound transactional emails (feedback notifications, password resets, milestones).
  • Encrypted vaults (Keel and similar): when an app uses an end-to-end encrypted vault, the encryption key is held in your browser only. The server stores opaque ciphertext and cannot read the contents.

5. Why we use it (and the legal basis)

  • Operate the service: running the apps you signed up for. Legal basis: contract (UK GDPR Article 6(1)(b)).
  • Process payments: billing, subscription management, invoice records. Legal basis: contract.
  • AI processing of your content: sending your notes, journal entries, documents, transactions etc. to Gemini or Claude when you use AI features. Legal basis: consent (UK GDPR Article 6(1)(a)). You grant this on first use and can withdraw it at /settings/privacy.
  • Health data processing (Keel): weight, exercise, blood-test results, journaling tied to wellbeing. Special category data under Article 9. Legal basis: explicit consent (Article 9(2)(a)). Withdrawable at any time at /settings/privacy.
  • Google Workspace access: reading and acting on the Gmail, Calendar, Tasks and Drive of an account you have connected. Legal basis: consent (Article 6(1)(a)). Withdrawable by disconnecting the account at /settings/integrations/google.
  • Improve the service: anonymous analytics, error monitoring. Legal basis: legitimate interest (UK GDPR Article 6(1)(f)).
  • Security and fraud prevention: rate limiting, abuse detection, audit logs. Legal basis: legitimate interest.
  • Communicate with you: replying to support, sending account-critical emails. Legal basis: contract.

6. Who we share it with (processors)

Meta-Me does not sell or share your personal data for marketing. We share the minimum necessary with carefully-chosen processors. The full, up-to-date list is at /privacy/subprocessors; in summary:

  • Stripe: payment processing and billing.
  • Google (Gemini API, OAuth, Workspace APIs, SMTP): AI inference for features that use Gemini, sign-in if you use Google, access to your own Gmail / Calendar / Tasks / Drive if you connect an account (section 3), outbound transactional email. Gemini API requests are excluded from training per Google's terms.
  • Anthropic (Claude API): AI inference for features that use Claude. Not used for training.
  • Cloudflare: DNS and Cloudflare Tunnel reverse-proxy.
  • Law enforcement: only if compelled by a valid UK legal process.

7. How long we keep it

  • Account data: for as long as your account exists, plus 30 days after deletion to allow recovery from accidental deletion.
  • App content: same as account data. Deleting your account deletes the content.
  • Stripe records: Stripe retains payment records as required by financial regulations (typically 7 years in the UK).
  • Analytics events: retained indefinitely. They are anonymous once the day's salt is destroyed, so there is no personal data left to expire.
  • Google authorisation tokens: until you disconnect the account or delete your account, whichever comes first. Deleted immediately on disconnect.
  • Google access log: retained for as long as your account exists. It holds request metadata only — never message, event or file content.
  • Operational logs and error reports: kept only as long as needed to diagnose and fix the issue, and deleted when you delete your account.

8. Your rights

Under UK GDPR you have the right to:

  • Access the personal data we hold about you.
  • Correct inaccurate or incomplete data.
  • Delete your account and the data associated with it.
  • Port your data, receiving it in a machine-readable format.
  • Object to processing based on legitimate interest.
  • Withdraw consent for any processing where consent is the legal basis.

You can withdraw consent or review your data preferences at any time at /settings/privacy. To exercise any other right, email [email protected] — we aim to respond within 14 days and will fulfil within 30 days (UK GDPR Article 12(3)). You also have the right to complain to the UK Information Commissioner's Office at ico.org.uk.

9. Cookies

We use the smallest possible set of cookies:

  • Session cookie: first-party, scoped to .meta-me.uk, set when you sign in. Required to use authenticated features.
  • Stripe checkout cookies: set by Stripe during the checkout flow only. See Stripe's cookies policy.

No analytics cookies. No advertising cookies. No third-party tracking.

10. Security

We take reasonable steps to protect your data: TLS for all traffic, encrypted backups, role-based access, and end-to-end encryption for the most sensitive data (where the app supports it, like Keel's document vault).

No system is completely secure. If we ever discover a breach affecting your data, we will notify you and, where required, the ICO within 72 hours.

11. International transfers

Most data stays in the UK. Some processors are based in the US (Stripe, Google, Anthropic). When data is transferred outside the UK or EU, it is covered by the UK International Data Transfer Agreement or the Standard Contractual Clauses.

12. Changes to this policy

We will update this page when our practices change. The "last updated" date at the top reflects the most recent change. For material changes, we will notify you by email.

13. Contact

Questions about privacy: [email protected].