Privacy Policy

Last updated 20 October 2026

1. Who this covers

This policy explains how Metatheory Inc. (“Metatheory”, “we”, “us”) handles personal information in connection with mrmeeseeks.app, the Mr. Meeseeks desktop application, our command-line tools, and the Mr. Meeseeks Chrome extension (together, the “Service”).

In short: Mr. Meeseeks is local-first. Your conversations, memory and imported chat history are stored in files on your own computer, under your home directory (by default ~/.mrmeeseeks). We do not receive them unless you use a hosted feature that needs to send them to us.

2. What stays on your computer

Unless you turn on a hosted feature, the following stay local and are never sent to us:

your chats with the agent, its memory, summaries and project files;
chat history you import, including from Claude Code, the Codex CLI, ChatGPT and claude.ai;
any provider API keys you supply yourself, and the local configuration files that hold them.

Local data is yours to inspect, back up or delete. Deleting those files deletes the data.

3. Information we collect

Account information. When you sign in with GitHub or Google, we receive your email address and basic profile identifiers from that provider, and we store the account record, group and credit balance needed to run your account. We do not receive your password.

API keys we issue. We store a hashed form of the keys our service issues to your devices, with a label you choose and the dates they were created and last used, so you can review and revoke them.

Billing information. If you buy credits or a subscription, payment is handled by our payment processor. We receive the transaction result and credit ledger entries; we do not receive or store full card numbers.

Hosted feature content. If you use our hosted model-routing or summarization service, the prompts, context and conversation excerpts needed for that request pass through our service to the model provider you selected, and the response passes back. We log operational metadata for each request, such as time, model, token counts, cost and status, which we need for metering, billing and abuse prevention.

Service logs. Our servers record ordinary request information, including IP address, timestamp, path, status code and user agent, for security, rate limiting and debugging.

Product analytics. We may use a product analytics provider (for example PostHog) on our website and hosted service to measure page views, feature usage and errors, so we can see what works. Where this uses cookies or similar technology, it is limited to our own web properties. We do not use it to profile the contents of your conversations.

Support correspondence. If you email us, we keep the message and our reply.

We do not ask for special-category data, and you should not send it to us. We do not knowingly collect information from children under 13.

4. The Chrome extension

The Mr. Meeseeks Chrome extension exists for one purpose: to bring your own past ChatGPT and Claude web conversations into your local Mr. Meeseeks memory. It is local-first and consent-gated.

It only works when you pair it. You enter a pairing code shown by the Mr. Meeseeks app on your computer. Until it is paired, the extension does not read or export anything.
It only runs when you ask it to. Reading your chat history happens when you click Export in the extension popup and choose how far back to go. There is no background scraping and no scheduled collection.
It reads only the chat pages you are signed in to. On chatgpt.com and claude.ai, it reads your own conversation list and message text using the same signed-in session your browser already has. It does not read other sites, other tabs, your browsing history, or your passwords.
Where the data goes. Exported conversations are sent to the Mr. Meeseeks application running on your own computer, over a local connection, and are stored in your local memory directory. If you skip pairing, the export is saved to your Downloads folder instead. Either way, the extension does not send your conversations to Metatheory's servers.
What we receive from the extension. Nothing by default. Your conversation content is only ever seen by us if you later choose to use a hosted feature, such as hosted summarization, on your local memory.
Removal. Uninstalling the extension stops it completely. Imported conversations stay in your local memory until you delete them.

We do not sell or transfer the data handled by the extension, do not use it for advertising, creditworthiness or lending, and do not use it for any purpose unrelated to importing your own history.

5. Importing from your own machine

The desktop app and command-line tools can import chat history that Claude Code and the Codex CLI already store in their configuration directories on your computer. This is opt-in, you choose the sources, and the result is written to your local memory directory. These imports do not send data to us.

6. Saved memory (optional)

This section describes an optional feature that is not generally available yet. Its wording is pending legal review.

Saved memory is off unless you turn it on. When you turn on Save chat to my account in the app, and confirm it on that device, the app uploads a copy of your local memory to your mrmeeseeks.app account so you can restore it on another computer:

What is stored: your memory's message log, its summaries and its current view, and, unless you untick it, the images attached to your chats. Meeseeks work logs are stored only if you choose to include them. The app uploads what is already in your memory files, after the app has removed recognised secrets. Configuration files, provider API keys and project files are never uploaded.
Where: on our infrastructure provider's servers (Cloudflare), kept separately for each account and encrypted at rest. This is not end-to-end encrypted: our service can read it in order to serve it back to your devices.
What we do with it: we store it and return it to devices signed in to your account. We do not use it to train models, do not include it in any training data, and do not write its content to our request logs.
Deleting it: turn the feature off in the app and choose to delete the server copy, or use Delete saved memory on your account page. Deletion removes it from our live storage straight away. Our storage provider's recovery copies may keep it for up to 30 days. Your local files are not affected.

7. How we use information

to run your account, sign you in and authorize your devices;
to provide hosted features you turn on, including routing requests to model providers;
to meter usage, apply credits, take payment and keep records;
to keep the Service secure and available, including rate limiting and investigating abuse;
to fix problems, and to understand which features are used;
to answer your support messages;
to comply with law and enforce our Terms of Service.

Where the GDPR or similar law applies, we rely on performing our contract with you, our legitimate interests in security and improving the Service, your consent where we ask for it, and compliance with legal obligations.

We do not use your conversation content to train our own models.

8. Who we share with

We do not sell your personal information, and we do not share it for advertising. We use a small number of service providers who process data on our behalf under contract:

Model providers such as Anthropic and OpenAI, for hosted routing and summarization requests you make. Their own terms and privacy policies govern what they do with the request.
Infrastructure and hosting providers, for serving the site and storing account records, logs and, if you turn it on, saved memory.
Payment processing, for purchases.
Identity providers (GitHub, Google), when you choose to sign in with them.
Product analytics, as described above.

We may also disclose information if the law requires it, to protect our rights or someone's safety, or in connection with a merger, acquisition or sale of assets, in which case this policy continues to apply to the information transferred.

9. International transfers

We are based in the United States and our providers may process data in the United States and elsewhere. Where required, we rely on appropriate safeguards, such as standard contractual clauses, for transfers out of your region.

10. How long we keep it

We keep account records while your account exists and for as long as we need them for legal, tax and accounting purposes. Request and security logs are kept for a limited operational period. Hosted request content is kept only as long as needed to complete the request and to keep the metering and billing record of it. Saved memory, if you turn it on, is kept until you delete it or delete your account (see section 6). Local data on your computer is kept until you delete it.

11. Your choices and rights

Use it without us. You can run Mr. Meeseeks locally with your own provider API keys and not use hosted features.
Keys. You can see and revoke the keys issued to your devices on your account page.
Saved memory. If you turned it on, you can delete it at any time from the app or your account page.
Access, correction, deletion, portability and objection. Depending on where you live, you may have these rights over the personal information we hold. Write to support@mrmeeseeks.app and we will respond as the law requires. We may need to verify your identity.
Account deletion. Ask us at support@mrmeeseeks.app and we will delete your account record, subject to records we must keep. Unexpired credits are forfeited on deletion. Your local files are not affected: delete your Mr. Meeseeks data directory to remove them.
Complaints. You may complain to your local data protection authority.

12. Security

We use measures such as encryption in transit, hashed credentials, scoped API keys and access controls. No system is perfectly secure, and keeping your own machine, browser and keys secure is your responsibility.

13. Compliance limits

We make no HIPAA, PCI DSS or similar compliance claims, and we have no business associate agreement in place. Do not use the Service to process protected health information, payment card data or other regulated data that requires such an agreement.

14. Changes to this policy

We may update this policy. We will change the date above and, for material changes, give notice by a reasonable means such as the site or email.

15. Contact

Metatheory Inc.
Email: support@mrmeeseeks.app