Privacy policy
What mttr keeps, why, for how long, and who else sees it. Nothing here is sold or shared for advertising.
Who keeps it
mttr is run by subinternal. When this page says mttr keeps something, subinternal keeps it, on machines it runs. Ask about anything here, or for anything to be removed, through the form on the page for teams.
Sites mttr reads
mttr reads public pages only, under its own crawler name, and obeys each site’s robots.txt. It never reads a private address, a page behind a sign-in, or a form, and it reads a few pages at a time so a site is never put under load.
It keeps what it reads: each page’s address, text and newest HTML, its links, and what each rule found. That is what lets a later read be set against an earlier one. Pages can hold names and contact details their site chose to publish; mttr keeps them as part of the page and does nothing else with them.
Sites mttr reads are named on the leaderboard, in their reports and on the public index. Sites read from Google Search Console for their owner, and any whose owner asked, go by an anonymous code instead.
When you come in early
Before mttr opens to everyone, the first page asks for an email, and you may skip it. An email given is kept with the sites you were reading when you gave it, to let you in and to write to you once when mttr opens, with a link back to those reads. You may be asked again as a read runs and on its report, and Not now puts that away.
When you sign in or sign up
An account is an email and a key. The key is kept only as a one-way hash, so mttr cannot show it again. Signing in by email sends a short code to that address; the code is kept only until it is used or expires. Your email is used to know whose account it is and to send those codes, and for nothing else.
What your agent asks
Each call a key makes is kept: which tool, about which site, how long it took and whether it answered. Never the text of a page or anything you typed. Calls are kept 90 days, then forgotten, and they are shown only on your own progress page.
What your agent tells mttr
An agent can tell mttr what it did on a site, step by step: what it planned, changed and checked, what it found, the files it touched and the rules it worked on. These notes are kept with your account, shown on your progress page, and read by mttr to learn where agents get stuck and what to build next. They are never shown to anyone else or sold. Your agent is asked never to send secrets or a site’s private data.
Claiming a site
A claim is checked by looking for its token in your domain’s DNS or in a file on your site. The token and the result of each check are kept with your account, and a public server checks proved claims once a day.
When you tell us why not
A visitor who browses without reading a site may be asked, in a small card, what stopped them and what they would want instead. What you write is kept with the email you give, if you give one, the card that asked and the page it was on, and nothing else about you. It is read by the people who build mttr, to decide what to build next, and is never shown to anyone else.
Whether a card was put away, and when, is remembered in your browser’s own storage, not in a cookie, so the cards do not ask again. Clearing your browser’s data forgets it.
When you book a session
The form keeps your name, work email, company, site and the answers you choose, to prepare and arrange the session. The site you name is read before the call. These requests are seen only by the people preparing it.
Your address and where you are
Your IP address is used while you are here to keep the free limits fair, such as reads and checks an hour, and to tell apart people asking at once. It is held in memory and not written down, except as the one-way marks below.
Results that depend on a place, such as which assistant answers to show first, use the city nearest the location Cloudflare gives for your address, in the United States only. That city is used for the page and not kept, unless you pick one yourself, which a cookie remembers.
A vote in a poll on a live card is kept with a one-way mark made from your address and the card, so one person counts once. The mark cannot be turned back into the address.
Counting how mttr is used
mttr counts how many people take each step, such as opening a report, asking for a read or signing up, as one number for each step and each day. No cookie, address or name is kept with it, and no one’s way through the site is followed. Crawlers, scripts and the owner of mttr are not counted. mttr runs no analytics script and no advertising code.
It also counts the pages people open, and how many people a day. To count a person once in a day without a cookie, each visit is given a one-way mark made from the address, the browser’s name and a secret that changes every day. The mark cannot be turned back into either, is kept only for that day, and is deleted the next, so no one can be followed from one day to another.
Cookies
mttr sets a cookie only to do what you asked. None is for tracking or advertising, and none is set by anyone else.
| Cookie | What it is for | How long |
|---|---|---|
mttr_soon | Remembers that you are past the first screen, and whether you gave an email there. | 30 days with an email; until the browser closes if you skipped |
mttr_session | Keeps you signed in. | 30 days, or until you sign out |
mttr_p | Keeps a progress page open after you followed its link. | Until the link lapses |
mttr_connected | Remembers that this browser has connected an agent, so the setup steps make way for what comes next. | One year |
mttr_near | Remembers the city you picked for results that depend on a place, or that you turned place off. | 180 days |
mttr_beta | Lets you into features still in testing, once you gave their password. | 30 days |
Who else sees it
A few services do part of the work. Each sees only what its part needs.
- Cloudflare carries every request to mttr and back, and so sees your address and the pages you ask for, as any network in between would.
- The assistants a citation lookup asks, such as Gemini and Perplexity, receive the question alone: a kind of business and a city, never your name, email or anything about you.
- A mail service delivers sign-in codes, and sees the address and the code.
- Google Search Console is read only for sites whose owner added mttr to them.
The models that read your pages run on mttr’s own hardware, so a page’s text is not sent to an outside service to be understood. Nothing is shared with anyone else unless the law requires it.
How long it is kept
Reads of a site are kept while mttr runs, so its history holds, unless its owner asks for them to be removed. An account and what it holds are kept until it is closed. Agent calls are kept 90 days. Sign-in codes last minutes. Early access emails are kept until mttr opens and has written to you, then while you have an account. Session requests are kept while the conversation they started goes on.
Your choices
You may ask what mttr keeps about you, have it corrected, or have it removed, and you may close an account with everything it kept. A site’s owner may have its reads named by a code, or removed. Ask through the form on the page for teams, and say which email or site it is about; mttr answers within 30 days.
Children
mttr is made for people who run websites. It is not meant for anyone under 16, and it does not knowingly keep anything about them.
What is never done
What mttr keeps is never sold, rented or shared for advertising, and is never used to build a profile of a person.
Changes to this page
When what mttr keeps changes, this page changes with it, and its date says when. A change that uses what you gave in a new way will be told to you before it applies.