Privacy.
What Mark collects, what it doesn’t, and why the difference is architectural rather than a promise on a page.
This page does one thing. It collects an email address if you give it one.
If you sign up for early access, the form stores the email you entered. Nothing else. There is no analytics script on this site, no pixels, no third-party tags, no session replay.
- What is stored. The email address you typed. The date you submitted it.
- Where it is stored. A single database row at the hosting provider for this site.
- What it is used for. One email when Mark ships. Nothing else. No newsletter, no marketing drips, no “product updates.”
- When it is deleted. Six months after launch, or sooner on request. Unsubscribe is a single click in the launch email.
- Who sees it. The two people building Mark. No marketing agency. No data broker. No partner.
The site itself is static HTML. There are no cookies set by Mark. Your browser may send standard request headers (IP, user-agent) to the host; these are not logged for analytics and are discarded with the host’s normal log rotation.
The app does not phone home. Not for telemetry, not for analytics, not for the coach.
Mark is a native macOS app. Your activity data, your marks, your transcripts, your coach conversations all live in a local database on your Mac. Nothing about your day is transmitted to a server controlled by Mark.
Local-only is not a setting. It is the architecture.
- Activity capture. Stays on your machine. Stored in a SQLite database inside the app’s sandbox.
- The coach. A local language model runs on your Mac. Your day is never sent to OpenAI, Anthropic, Google, or anyone else. There is no API key required and no token meter.
- Crash reports. Off by default. If you opt in, reports are anonymous and contain no activity data.
- License check. Once, on activation, the app verifies your license key. The check sends the key and nothing else. It does not run again.
- Updates. The app checks for a new version against a static manifest. The request contains no user identifier.
These are not policies that can be quietly amended in a future version.
The Never list is the binding form of this page. The architecture makes each line enforceable: there is nothing to leak because there is nothing collected; there is no team dashboard because there is no server to host one; there is no data to sell because the data never leaves your machine.
- No cloud sync.
- No team dashboard.
- No cloud LLM costs.
- No data sales.
- No surveillance.
If any of these change, the change will be announced before it ships, in a release note titled with the commitment that changed. Not buried in a policy diff.
You can delete your data at any time, without asking.
The app: uninstalling Mark removes the local database. There is no copy of your activity anywhere else to delete.
The email list: reply to any email from Mark with the word “delete” and your address is removed within seven days. Or email privacy@makeamark.ai directly.
If you are in the EU, UK, or California, the GDPR / UK GDPR / CCPA rights of access, correction, deletion, portability, and objection apply to the one piece of data Mark holds about you: the email address you submitted. Email the same address to exercise any of them. There is no form to fill in.
This page changes only when something material changes.
Cosmetic edits will not bump the date at the top. A change to what is collected, who can see it, or how long it is kept will. If you signed up for early access, you will get a single email when that happens, not a notification banner you have to dismiss.
One human, one inbox.
Questions, deletion requests, or pushback go to privacy@makeamark.ai. Replies usually take a day or two.