ReMyndWho we are
ReMynd is built and operated by M37 Inc., trading as Move37. M37 Inc. is the entity responsible for the personal data described in this policy — the data controller, in the language of the GDPR.
"We", "us" and "our" below mean M37 Inc. "ReMynd" means the Mac app and the website at remyndai.com.
The fastest way to reach a human about anything here is [email protected].
The honest headline
A lot of privacy pages open with "nothing ever leaves your device." We are not going to tell you that, because for ReMynd it is not true and you would find out.
ReMynd has an account system, it reports its own crashes, it measures how the app is used, its AI sends your question and the part of your history needed to answer it to a model in the cloud, and you can share a moment or back your history up. All of that leaves your Mac. What does not leave, unless you send it, is the thing that actually matters: the recording of your screen and the text inside it.
So the accurate claim, and the one we will hold ourselves to, is narrower and stronger:
Your history lives on your Mac. Pieces of it leave only through features you use or switch on, and the only readable copies we host are ones you chose to share or send to yourself.
Everything below is the detail behind that sentence.
What stays on your Mac
Your history is kept in a local database and video files under ~/Library/Application Support/Move37/ReMynd-<your account id>/Recordings/ (or Move37/ScreenomeX/Recordings/ before you sign in). It holds:
- Screen recordings. The video ReMynd captures.
- Extracted text. What OCR reads from the window you are focused on.
- Your searches. The words you type into search.
- Your timeline and your second brain. The notes, entities and connections ReMynd builds from your history.
- Call and dictation audio, and the transcripts made from it.
None of it is uploaded to us as a whole. You can open that folder, and you can delete it. If you delete it, that history is gone — unless you turned on backup, we have no copy to restore from. Pieces of it leave only through the features in the next section: ReMynd's AI, sharing, report emails and backup.
Two details worth knowing, because they narrow what is captured in the first place:
OCR is scoped to the focused window. ReMynd extracts text from the window you are working in, not from everything visible. Windows behind it are recorded as video but not read.
ReMynd's own sensitive windows are excluded. The recorder skips OCR when a ReMynd window overlaps what you are focused on, so the app does not end up reading its own AI chat back into your history.
What leaves your Mac, and where it goes
This is the part most policies bury. It is the part you should actually read.
| What leaves | When | Who receives it |
|---|---|---|
| Email address, and the authentication tokens for your account | You create an account or sign in | Google Firebase Authentication |
| Account profile: your plan, settings and onboarding progress | You use the app while signed in | Google Firebase |
| Crash and error reports: stack traces, error messages, OS version, device model, app version and your account email. Some error reports include file paths, which contain your Mac's user name | The app crashes or hits an error | Sentry |
| Usage telemetry: which features you use, counts, durations, query lengths, your plan, and figures such as free disk space and CPU use — linked to your account email | You use the app | Segment, which forwards to Mixpanel, and PostHog |
| Your question or task, plus the slice of your history needed for it | You use Ask, or an AI feature such as a day or call summary | ReMynd's AI relay, then OpenRouter, then a zero-data-retention model provider |
| AI usage records: which feature, which model, token counts, cost, response time. Never the text of a prompt or answer | Each AI request | PostHog |
| A shared snippet: the screen video of that stretch, and the apps, window titles, documents and web pages open during it | You press Share on a moment | ReMynd's share service, at share.remyndai.com |
| A shared call: its audio, transcript and summary | You press Share on a call | ReMynd's share service, at share.remyndai.com |
| A report email: a summary of your day or week written by ReMynd's AI, plus screen frames if you turn them on | Report emails are on for your account | ReMynd's report service, which hands the email to Customer.io to deliver |
| Subscription and billing status | You buy or change a plan | Stripe, through Google Firebase |
| Encrypted backups of your history | Only if you turn on backup | Your own S3-compatible bucket, or ReMynd Storage |
| The app's version, when it checks for updates | Periodically | Our release server |
| Speech model files, downloaded to your Mac | You enable transcription | Hugging Face — a download to you, not an upload from you |
A few of those deserve more than a table row.
ReMynd's AI is the real exception
There is no way to answer a question about your history without showing a model that history. So when you use Ask, or a feature that writes a summary of your day or of a call, the text it needs — your question and the matching slice of your history — leaves your Mac. Summaries can run in the background once they are on for your account; they take exactly the same path.
Every AI request ReMynd makes takes this path:
- ReMynd's AI relay checks that you are signed in and forwards the request. It does not store your prompts or the answers.
- OpenRouter routes the request to a model, under two rules the relay attaches to every request and no client can loosen: the provider must offer zero data retention, and it must not use prompts for training.
- The model provider answers and keeps nothing.
The app attaches the same two rules on your Mac before a request leaves it, and blocks any request it cannot attach them to, so the guarantee does not rest on a single server.
If that trade is not one you want to make, do not use the AI features — recording, search and your local timeline all keep working without them.
AI you bring is routed by you
Two kinds of AI sit outside that path, because they run on your accounts, not ours:
- Your own API keys. If you add your own key or model endpoint in Settings, requests go where you pointed them, under that provider's terms. Requests to OpenRouter on your own key still carry the zero-retention rules.
- Agents you connect. ReMynd Agent runs the Claude Code or Codex already installed on your Mac, signed in to your own account, and Claude Desktop, Claude Code, Codex or the ChatGPT desktop app can read your history through ReMynd's connector. What those agents send to Anthropic or OpenAI goes under your agreement with them, not through us.
Sharing makes a link anyone can open
When you share a snippet or a call, ReMynd uploads that moment to our share service and gives you a link. For a snippet that is the screen video plus the apps, window titles, documents and web pages open during it; for a call it is the audio, transcript and summary. Nothing is uploaded until you press Share.
The link is unlisted, but anyone who has it can open it, so share it the way you would share the file itself. There is no way to take a shared link down from inside the app yet: email [email protected] and we will delete it.
Report emails are written on your behalf
If daily or weekly report emails are on for your account, ReMynd's AI writes the report through the zero-retention path above, and the finished email goes to our report service, which hands it to Customer.io to send to you. Customer.io is told not to keep a copy of the message and not to track opens or clicks. If you also turn on screen frames, we host those images for at most seven days so the email can show them, then delete them. Report emails are off unless they are switched on for your account.
Telemetry records shape, not substance
We instrument the app so we can tell whether a feature works and whether ReMynd is straining your Mac. The events carry the shape of what you did, not what you did it to. Concretely, when you search, the event we record contains how many characters your query was and how many results came back. It does not contain the words.
The same principle applies throughout: we count searches, we do not collect search terms. Alongside events we record your plan and machine figures such as free disk space and CPU use.
Telemetry is linked to your account email, so we can help when something breaks for you and send the setup emails described under "Email". It goes to Segment, which forwards it to Mixpanel, and to PostHog. Crash reports go to Sentry with your account email attached for the same reason.
Cloud backup is encrypted before it leaves
Backup is off by default and needs a plan that includes storage. You choose where it goes: your own S3-compatible bucket, where you supply the endpoint, region and keys, or ReMynd Storage, a bucket we run for you.
Either way, your history is encrypted on your Mac before it is uploaded, with a key made from a password you choose. That password is not sent to us, so we cannot read your backup in either place. The keys for your own bucket are stored in your Mac's Keychain, not with us.
We email you about getting set up — for example if you downloaded ReMynd but have not opened it, or have not used it in a while — and about new releases. These go through Customer.io, which we keep updated with your email, when you last opened the app, which version you run, and signs that the app is straining your Mac.
Today these emails go to everyone who has given us an email address, whether or not they ticked "send me occasional product updates". Every one has an unsubscribe link, and unsubscribing stops them. It does not stop transactional messages such as your download link.
What we do not do
- We do not train models on your screen history, and we do not let anyone else.
- We do not send your history to any AI model provider that retains it or trains on it.
- We do not pool your history with other users' for any purpose.
- We do not sell, rent or trade your personal information. We have never done this and we do not have a business model that depends on it.
- We do not put screen content, search terms, or the text of your questions into analytics events.
- We do not use advertising trackers or third-party advertising cookies anywhere in the app.
- We cannot read your backups, wherever you store them.
The website
remyndai.com uses two kinds of analytics.
Our own counter. Each browser gets a random identifier, kept in localStorage and in a first-party cookie (rm_vid, which lasts two years). Against it we record the page you viewed (the path, without any query string), the referring site's domain, your device category (desktop, tablet or phone), the country your request came from as reported by our CDN, and campaign parameters when you click download. This lives in our own database and does not include your IP address.
PostHog. We also use PostHog, loaded through our own subdomain, k.remyndai.com. It records page views, clicks, and session recordings of how you move through the site, with everything you type masked. It keeps an identifier in a cookie and in localStorage, and it receives your IP address, which it uses to estimate your location. We strip query strings from the addresses it records except campaign tags; ad click identifiers are kept so we can tell which ads work. If your browser sends Do Not Track, PostHog records nothing.
Forms. The site asks for your email in three places: before a Mac download starts, on a phone so we can send you the link, and to join the Windows waitlist. When you submit one we store your email, your consent choices, any campaign parameters in the URL, and your approximate location (city and country), browser, operating system and language. That goes to HubSpot, Customer.io, Mixpanel and PostHog, and PostHog links your earlier visits — and your use of the app, if you sign up with the same address — to that email. The download-link email is sent through Google Firebase and counts opens and clicks. The product-updates box is optional, and leaving it unticked still gets you the link.
Our servers' request logs also see your IP address and browser, and your email when you submit a form.
You can unsubscribe from any marketing email using the link in the footer of that email, or by writing to us.
How long we keep things
| Data | Retention |
|---|---|
| Your screen history | On your Mac, under limits you set in the app, until you delete it |
| What you send to ReMynd's AI | Not stored by our relay, and not retained by the model provider |
| Shared snippets and calls | At their link until deleted — email us and we will delete one |
| Screen frames in report emails | At most seven days |
| Account record | For as long as your account exists. There is no self-serve deletion in the app yet: email us to close your account and we delete the record within 90 days |
| Crash reports | 90 days |
| Usage telemetry | Not deleted automatically yet — email us and we will delete yours |
| Website session recordings | 30 days |
| Website analytics and form submissions | Not deleted automatically yet — email us and we will delete yours |
| Email contact record | Until you ask for deletion; unsubscribing stops the emails |
Your rights
Wherever you live, you can ask us to show you what we hold about you, correct it, delete it, or send it to you in a portable format. You can object to us processing your data for marketing at any time, and we will stop.
If you are in the UK or EEA, our legal bases are: performing our contract with you (running your account, sending your download), our legitimate interests (keeping the app working, understanding which features are used, security), and your consent (marketing email, which you can withdraw at any time). You have the right to complain to your local supervisory authority.
If you are in California, you have the right to know, delete, correct, and to opt out of sale or sharing of personal information. We do not sell or share personal information as those terms are defined by the CCPA, so there is nothing to opt out of — but the right stands, and exercising any of these rights will never degrade the service you get.
To exercise any of this, email [email protected]. We will respond within 30 days. We do not require you to create an account to make a request.
Security
Your history's main protection is architectural: it is on hardware you control, not on a server that can be breached at scale. There is no central store of readable screen recordings to steal: the backups we hold are encrypted with a key we do not have, and the only readable recordings we host are moments people chose to share.
For the data we do hold — account records, telemetry, your email, shared links — we use encrypted transport, encrypted storage at rest with our providers, and access limited to the people who need it. No system is perfectly secure, and we will not pretend otherwise. If we ever suffer a breach affecting your personal data, we will notify you and the relevant regulator as the law requires.
Children
ReMynd is not intended for anyone under 16, and we do not knowingly collect their personal information. If you believe a child has provided us data, email [email protected] and we will delete it.
International transfers
M37 Inc. is based in the United States and our providers are largely US-based. If you use ReMynd from the UK or EEA, your account and telemetry data will be transferred to the US under Standard Contractual Clauses or an equivalent safeguard. Your screen history is not collected, so it is not transferred — apart from the pieces you send through the features above, which may be processed in the US.
Changes to this policy
If we change how we handle your data in a way that matters, we will update the date at the top and tell account holders by email before the change takes effect. We will not quietly widen what we collect and rely on you re-reading this page.
Contact
Questions, data requests, or a correction to something on this page go to M37 Inc. at [email protected]. A person reads that address.
If you find something here that does not match what the app actually does, we want to know. That is a bug in the product or a bug in this page, and either way we will fix it.