meerko

Legal

Privacy policy

Last updated 7 October 2026 Covers Meerko Cloud, not self-hosted installs

The short version

We only keep Gmail messages from your Meerko threads

Replies to emails Meerko sent, and messages from people in your sequences. The rest of your inbox is never stored.

Your Google tokens are encrypted

Mailbox access tokens are stored encrypted, and we never see your Google password.

We don't sell data or train AI on it

Meerko makes no AI calls. Your own agent does the thinking, on your side.

Product analytics with PostHog, no ads

We measure how Meerko is used (in the EU) to improve it. No ads or tracking pixels.

Fields in [brackets] are filled in once the company details are final.

01Who we are

Meerko Cloud is run by [Legal entity name], [Registered address] ("Meerko", "we"). For your account, we decide how your data is used (we're the controller). For the leads and emails you put into Meerko, we only process them on your instructions (we're your processor).

02What we collect

DataWhat it is
AccountYour name, email address and Google account ID, from Sign in with Google.
MailboxesThe Gmail address you connect, its access tokens (encrypted), your sender name and daily limit.
Your workspaceTables and leads you import or find, sequences, drafts, and their pipeline stages.
EmailsEmails Meerko sends for you, and the replies in those threads.
Connected appsApps you approve (like Claude Code), when they were connected and last used.
UsagePages you visit, clicks, and session recordings in which what you type and your workspace data are masked. Errors, with the page or request they happened on.
Agent tool callsWhen an agent uses Meerko Cloud's MCP server: which tool it called, the arguments and result, the short reason the agent gives, the agent app and model, and how long it took. Never your conversation with the agent.
TechnicalServer logs with IP addresses, kept by our hosting provider for security.

03Gmail data

Meerko's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
  • Meerko asks Google for two permissions: to send email as you, and to read your inbox so it can spot replies.
  • It only stores messages in threads Meerko started, or from people in your sequences. For other recent mail it checks the sender's address and nothing else, and never stores it.
  • Gmail data is used only to send your emails and handle replies. It's never sold, used for ads, or used to train AI models.
  • Nobody at Meerko reads your email, unless you ask us to for support, or the law or a security investigation requires it.

04How we use it

  • To run the service you asked for: search, enrichment, sequences, reply detection and the pipeline.
  • To keep it secure: sign-in, abuse prevention and debugging.
  • To understand how Meerko is used and fix what breaks (product analytics and error tracking).
  • To answer you when you contact support.
  • We don't sell personal data or use it for advertising.

05Who we share it with

Only with the providers that run Meerko, under contracts that limit them to doing so. Apps you connect act on your behalf with the access you approved.

Sub-processorPurposeLocation
Google CloudHosting, scheduling and secret storageBelgium (EU)
SupabaseDatabaseGermany (EU)
PostHogProduct analytics, session recording, error tracking and agent tool-call analyticsGermany (EU)
IcypeasLead search and email finding: your search filters, and names with company domains[Location]

06Where it's stored

In the EU: the app runs in Google Cloud's Belgium region, the database in Supabase's Frankfurt region, and analytics in PostHog's EU cloud (Frankfurt). When a provider outside the EU is involved, the transfer is covered by the European Commission's Standard Contractual Clauses.

07How long we keep it

For as long as your account is open. When you ask us to delete your account, we delete your workspace data within [30] days, and it leaves backups within [X] days after that. Disconnecting a mailbox or an app ends its access straight away.

08Your rights

AccessGet a copy of your data
CorrectFix what's wrong
DeleteClose your account and erase it
ExportTake your data elsewhere

Email [privacy@domain] and we'll answer within 30 days. You can also complain to your data protection authority.

09People you email

If you got an email sent through Meerko: it came from the sender's own Gmail account, and they decided to send it. Every sequence email has an unsubscribe link; using it stops all of that sender's Meerko emails to you. To ask what data a sender holds about you, contact them, or write to us and we'll pass it on.

10Cookies

The cookies needed to sign you in, and one analytics cookie from PostHog. No advertising cookies.

CookieWhat it's forLasts
meerko_sessionKeeps you signed in to the dashboard30 days
meerko_nextBrings you back to the page you were on after signing in15 minutes
ph_<key>_posthogPostHog analytics: recognises the same browser across visits (also kept in local storage)1 year
meerko_signin_nonceTies a Google sign-in to the browser that started it, so nobody can sign you in to their account10 minutes

11Contact

Questions about your data?

[privacy@domain] · [Legal entity name], [Registered address]

We'll post changes here and update the date at the top. For significant changes, we'll email account owners first.