Skip to content

Privacy

Last updated 10 November 2026

What we store

Browsing Matter of Record needs no account. If you sign up, we store your email address, the profile details you choose (username and display name), the cases you follow, the coverage you log, and any ratings, tags or reviews you write. Your email address is never shown publicly.

Your profile, follows, logs and ratings are private unless you opt in. A published review appears on the coverage item with your handle only if you make both the profile and reviews public.

Always private: your email address, password, notification delivery mode, and calendar feed token. Public only if you opt in, independently: the profile page itself, the cases you follow, the coverage you log (including ratings), and published reviews. A published review on a coverage item shows your handle only when both the profile and reviews are public; otherwise it is attributed to "A member" or is not shown.

Analytics and cookies

We use PostHog, an EU-hosted analytics provider. Every visit is counted anonymously: the page you viewed is sent without cookies or anything stored in your browser, and it is not linked to your other visits. Nothing else is sent to it unless you accept. If you accept, PostHog keeps an identifier in your browser so a return visit is recognised, receives the events below, and records sessions and click heatmaps. Anything you type into a box is masked before it leaves your browser, and search terms are stripped from the page addresses it records. Its autocapture (which records every click and keystroke) stays off.

Microsoft Clarity runs on every visit. It records how pages are used — clicks, scrolling and mouse movement — as heatmaps and session replays. Until you accept, and if you decline, it sets no cookies: each page you view is recorded on its own and is not linked to your other pages or visits. If you accept, it sets cookies on this site to link the pages of one visit. Anything you type into a box is masked before it leaves your browser, and search terms and sign-in links are stripped from the page addresses it records. It does not run on sign-in, account or settings pages. Microsoft processes this data under its own privacy statement.

Declining changes nothing about how the site works. We set no advertising cookies, and analytics never runs on admin pages.

What you search for is never sent. Free-text search terms are stripped from every page URL before it reaches PostHog, and none of the events below carry the words you typed — only whether a search returned results and which one you picked.

This is every category of event we send, and the properties attached to each:

CategoryWhat's attached
Page viewsWhat's attachedThe page URL, with any q, query or search parameter removed before it is sent.
Following a caseWhat's attachedWhich case (its internal id, not the case name), your notification delivery mode, and whether the action succeeded.
Logging and reviewing coverageWhat's attachedWhich coverage item, the status or rating you set, which tag you applied, and the character length of a review — never the text of the review itself.
SearchWhat's attachedHow many results a search returned and which result you picked, and — when a search found nothing — whether any filters were active, whether we could offer near matches, and whether you asked us to add the case. The words you typed are never sent as an event property, and are stripped from the page-view URL before it leaves your browser.
HomepageWhat's attachedViewport and consent state, result-count and query-length buckets, and homepage control interactions. Raw search text is never sent.
CollectionsWhat's attachedWhich collection, which case in it you opened, and the member's position on the shelf.
Signing upWhat's attachedThe sign-up method (email or Google) and which part of the site started the flow.
Reading a case pageWhat's attachedWhich case, which timeline control you used, whether you expanded a timeline entry, which folded year range you revealed on the register, which element opened a source link (the row citation, the clip card's badge, the full-scan dialog — reached from the clip card's teaser, the row's only scan trigger since BAS-2058 — or the fallback caption — BAS-1311/BAS-1313/BAS-1535), and — on a podcast excerpt card — the show name, episode title, excerpt start position and segment count (never the quote text). Selecting a place on the locator map records which case, which place, and which control you used (the map's pin or its numbered row in the key); a timeline entry's headline opening its own anchor records which case and which event; and coverage artwork opening the work's stored link records which case, which work and which kind of coverage — internal ids only in all three, never a place name, an event title or the work's own title. Adding a hearing to a calendar records which case and event, and which surface (the Next up card, the hearings list, or the timeline) — never the hearing title. Asking to be reminded about one hearing records which surface you used and the timing you chose (day before, morning of, both, or off) — not the case, event or hearing title.
Your dashboardWhat's attachedHow many cases you follow, how many updates were listed, which update you opened, which event's watch link you used, and which followed case you marked caught up (its internal id, not the case name).
ErrorsWhat's attachedA stack trace, with no page content attached. When a public page fails to load from our database, the error names which part of the page failed, and carries the published case's web address segment and which of our sites served it. This is the one category not blocked on admin-only pages, so a crash on a page only staff use is still visible to us.
Internal operationsWhat's attachedOperational counts and flags only — outcome and action names, which transcription service was used, which version of our search was used, how recently the episode was created and whether it carried identifiers, the coverage item's internal id that links one episode's lookup → candidate → review events together, and a per-run correlation id that joins one retrieval attempt's events to its run-history row. When a public page fails to load from our database: which part of the page failed, the database error code, whether it ran out of time and how long it took, the published case's web address segment, and which of our sites served it. Attached to the case's internal id or to the episode, excerpt, coverage item, or staff account the operation concerns. Provider identifiers (Particle episode ids, the provider's reference number for the request), URLs, headlines, quote text, transcript text, notes, and other member data are never sent.
Supporting the recordWhat's attachedWhich payment link was opened (Stripe $5/$10/$25/custom, or Ko-fi). Server-side: the contribution's origin and currency, and the reason a payment needs manual review. A payment is never tied to an analytics identity — these events share the constant id support-anonymous.
MCP toolsWhat's attachedThe tool name and that the call came from MCP, attached to the signed-in account id when available or an anonymous operational id otherwise.

Once you sign in, these events are tied to your account id so we can, for example, tell how many people who follow a case also log coverage of it. We keep raw event data in PostHog for up to 12 months, after which it is deleted automatically; aggregated statistics with no per-person identifier may be kept longer. Internal jobs (the search index, scheduled crawls) also send a small number of operational events that never carry member data.

Supporting the record

One-time contributions on the support page are processed by Stripe. The payment itself happens on the processor's pages; card and account details go to them, never to us.

We keep a contribution ledger of what the processors report: the amount, the currency, the payment date, and the billing email used for the payment, which we need for the accounting and record-keeping the law requires. Contributions are never published, and there is no public supporter list. Deleting your account does not remove this ledger — it keys to the billing email the processor reported, not to your account, and the rolling five-year tally is a legal record either way.

Email

We send two kinds of email. Account email — sign-up confirmation, password resets and similar transactional messages — goes to every account. Optional case alerts go only where you turn them on: for a case you follow, either as each change to this site’s record goes out or in a daily or weekly digest, under your notification settings. You can turn alerts off per case in settings or from the unsubscribe link in any alert email. There is no marketing email.

Your data

You can download a copy of your data from the settings page at any time — your profile, follows, logs, ratings, reviews and review tags as a JSON file.

You can change your profile at any time in settings. Deleting your account is immediate and cannot be undone: it removes your profile, follows, logs, ratings, reviews — including any hidden or awaiting review — and review tags. Some records outlive it: a report you filed on someone's review keeps an anonymous record id with no name attached; a correction or erasure request you sent keeps the name and email you gave for our reply; anything others have already seen, quoted or cached cannot be recalled; and copies inside provider backups, plus the analytics events described above, age out on their own retention schedules. For anything else, write to contact@matterofrecord.app.

Related policies