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 counts which features get used, and its AI agent sends your question to a model that runs in the cloud. All of that leaves your Mac. What does not leave 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 memory is never in our cloud. It is on your Mac, and if you choose to back it up, in a bucket you own.
Everything below is the detail behind that sentence.
What stays on your Mac
These never reach ReMynd, in any form:
- 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 and into Ask.
- 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.
They live in a local database and video files under ~/Library/Application Support/Move37/ScreenomeX/Recordings/. You can open that folder. You can delete it. If you delete it, that history is gone — we have no copy to restore from.
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 |
| Crash reports: stack traces, OS version, device model, app version | The app crashes or hits an error | Sentry |
| Feature telemetry: event names, counts, durations, character counts | You use the app | Segment, which forwards to Mixpanel |
| Subscription and billing status | You buy or change a plan | Our payment processor and Firebase |
| Your question, plus the slice of your history needed to answer it | Only when you use ReMynd Agent | Anthropic (Claude) |
| Speech model files, downloaded to your Mac | You enable transcription | Hugging Face — a download to you, not an upload from you |
| Encrypted backups of your history | Only if you turn on cloud backup | The S3-compatible bucket you configured, using your keys |
Three of those deserve more than a table row.
ReMynd Agent is the real exception
When you use the agent, your question and the relevant part of your history are sent to Anthropic's Claude to be answered. There is no way to answer a question about your history without showing the model that history.
This is the single place where your screen content leaves your machine, it only happens when you invoke the agent, and it does not happen in the background. If that trade is not one you want to make, do not use the agent — recording, search and your local timeline all keep working without it.
Telemetry records shape, not substance
We instrument the app so we can tell whether a feature works. The events carry the shape of what you did, not what you did it to. Concretely, when you send a message to Ask, the event we record contains the length of your query, whether a response came back, and how long the response was. It does not contain the query or the response.
The same principle applies throughout: we count searches, we do not collect search terms.
Cloud backup is your infrastructure
Backup is off by default. Turning it on asks you for an S3-compatible endpoint, a region, an access key and a secret. That is your storage account. Your history is encrypted and written there.
We do not hold those keys, we cannot read that bucket, and revoking our access is something you do in your own provider's console rather than something you ask us for.
What we do not do
- We do not train models on your screen history, and we do not let anyone else.
- 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 do not read the bucket you configure for backup.
The website
remyndai.com is deliberately lighter than the app.
First-party analytics, no cookies. Each visit generates a random identifier stored in your browser's localStorage — not a cookie, not shared with anyone, and cleared when you clear site data. Against it we record the page you viewed, the referring site's domain, your device category (desktop, tablet or phone), and the country your request came from as reported by our CDN. We do not store your IP address and we do not run third-party analytics or advertising scripts.
When you download. Downloading ReMynd on a Mac asks you for nothing — no email, no account, no form. The download itself is counted anonymously against a random identifier your browser keeps, so we can see how many people downloaded without knowing who they were. On a phone there is nothing to install, so we offer to email you the link instead. If you take us up on that, your email address, your consent choices and any campaign parameters in the URL are stored and shared with HubSpot and Customer.io so we can send you the link and, if you agreed to it, occasional product updates. The marketing checkbox is genuinely optional — unticking it still gets you the link.
You can unsubscribe from any marketing email using the link in the footer of that email, or by writing to us. Unsubscribing does not affect transactional messages such as your download link.
How long we keep things
| Data | Retention |
|---|---|
| Your screen history | On your Mac, under limits you set in the app, until you delete it |
| Account record | For as long as your account exists, then deleted within 90 days of closure |
| Crash reports | 90 days |
| Product telemetry | 24 months |
| Website analytics | 25 months |
| Marketing contact record | Until you unsubscribe or ask for deletion |
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 user screen recordings to steal, because we never built one.
For the data we do hold — account records, telemetry, your email — 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 transferred, because it is not collected.
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.