Plainly
WHAT THIS SITE RECORDS
People come here to find out what happens if the police search their car, or whether a landlord can walk in, or what a charge carries. A list of those questions with a name or an address beside it is a thing that can be breached, subpoenaed, or read by whoever holds a database key next year, and no promise written on a page stops that happening. Not collecting it does.
So this is not a policy in the usual sense. It is a list of what the code does, written by the person who runs the site. If a line here turns out to be wrong, the contact page at the foot of this one reaches that person, and the page or the code gets fixed.
WHAT IS KEPT
What people search for
The words typed into the search box, which state they were on, and which result they opened. Nothing beside it: no address, no account, no session, no cookie, no fingerprint of a browser.
Why: It decides what gets written next. A question people keep asking that the guide cannot answer is the most useful thing this site can learn.
What people search for on the video shelf
The words typed into the video search box, how many videos matched, and the first three it showed, kept as a count per phrase per day. No time of day, no address, no account, no cookie, and never a row per search: two people typing the same words on the same day are one number. Removed after ninety days.
Why: A phrase that finds no video is the list of footage to go and find. It is counted once somebody stops typing, not per letter.
That a request was made, on the three things that have a ceiling
A counter, and nothing else, on the answer agent, the contact form and the search box. The number is kept against a salted hash whose salt carries the date, so the same visitor is a different number tomorrow and a week of activity cannot be lined up into one person's history. What was asked, written or searched for is never in this counter at all, and neither is an address: the hash is computed here and the database only ever sees the result.
Why: Each of the three can be called without signing in, and each costs something when it is called in a loop: the answer tool costs money per question, and the contact form sends mail from a domain this site owns, which a flood would get marked as a spam source. Counting is all a ceiling needs, and counting does not require knowing who.
Aggregate traffic
Pageviews, which page, and where the visit came from, through Vercel Web Analytics. It was checked before it went in: the script sets no cookie and writes nothing to localStorage, sessionStorage or IndexedDB, and it is served from this domain rather than someone else's. There is nothing in it that can recognize the same person twice.
Why: Without it there is no way to tell whether anybody is reading this, or which parts. It is the difference between building the guide people use and the guide we guessed at.
An account, if you make one
Your email address, which is how the sign in link reaches you. The list of sections you saved. A username, given as member and six digits when the account is made and yours to change, for telling accounts apart. A nickname and an icon, if you pick them on your account page: one from the site's own set, or a picture you upload, which is drawn again by the site as a small square image with nothing else from the file kept, and shown only to you. A refund you ask for with Request a refund: which charge, whether the terms cover it, and whether the owner was emailed. On a case or Pro, if you add one, one more email address that copies of your reminders go to. Any files you add to a case, which have an entry of their own below. If you turn on two step sign in, the secret your authenticator app shares is kept by Supabase, the sign in service, beside your account, and removed when you turn it off; this site never reads it. Nothing else. Not what you searched for and not which pages you read: searches are written without an account beside them whether you have one or not, and there is no column that could hold one. Not what you asked the answer agent either, unless you press Keep on an answer or ask inside a case, which has an entry of its own below.
Why: So the pages somebody is saving are still there on the next device, and after the phone is gone. It is the only thing on this site that follows a person, and it follows them because they asked it to.
Answers you keep, if you keep any
Nothing from Ask is stored with your account unless you press Keep under an answer, or ask inside a case, where every answer is kept with the case so its page and its summary have them. Then the question you typed, the answer with its headline, the sections it cited, which state, the name you file it under if you give one, and when, are kept with your account so you can read it again on any device. Removing one removes it, and deleting the account removes every one, those kept with a case included.
Why: So an answer read in a worried moment is still there when the letter arrives a week later, and so the site can tell you when a law behind an answer you kept has changed.
Your plan, if you buy one
Stripe's customer number for you, which plan you are on, and for each case its name, its state, when it opened and when it closes, and how many of its questions are used. A log of the payment notices Stripe sends is kept too: which kind of notice, which customer number, which plan, and when. Stripe holds the card, and anything it asks for at checkout, under its own privacy policy; this site never sees the card number. Deleting the account removes everything here but the log of payment notices, which keeps no name or email address and stays so a refund can still be traced.
Why: So a plan works the moment it is paid for, stops when it should, and a refund or a question about a charge can be answered from a record rather than a guess.
A message, if you send one
What you write on the contact page, or in the request form at the foot of each state's page, and an email address only if you choose to type one. Leave it blank and the message arrives anonymous. Your address is not recorded either way.
Why: So a gap somebody reports can be answered, when they want an answer, and so the pages people ask for are the ones written next.
A reminder, if you set one
Which period in which state's guide, the date you typed, the date the counting reaches, and when the next email goes out, stored with your account so it can be sent to your account's email address, and to the one more address you added, if you added one. No notes, no names, no case number. It is deleted thirty days after its date, or the moment you remove it on your account page. When a law change email goes to you, a record that it went is kept with your account, holding which change and when, so the same change is not mailed twice.
Why: So the email before a date arrives without you keeping a file, which is the paid tool you asked for. The address it goes to is read from your account when the email is sent, and is not copied anywhere else. A person you add gets a copy of each reminder that says it is from you, with a link that stops their copies without an account; law change emails are never copied.
Files you add to a case, if you add any
Each file as you gave it, with its name, its size, its type, which case it belongs to, the note you wrote about it if you wrote one, and when it was added. The files sit in a private storage bucket that the site's public key cannot list, read, change or delete; the site's server opens a file only for the signed in account that added it, and hands it back on a link that works for one minute. Nothing reads what a file shows unless you press Read this paper on it: then that one file is sent to Anthropic, the company whose model reads it, under Anthropic's terms for its API, and what it found (the kind of paper, the court, the case number, the dates, the charges and the amounts) is kept with the file and removed with it. A file stays until you remove it, and removing it removes the file itself, not only its place in the list. Deleting the account, at the foot of the account page, removes every file with it, and the same place downloads everything the account holds in one file. Said plainly, because it is the opposite of everything else on this page: this is the one thing here that holds what a situation is with an account beside it. It can be reached by whatever can reach the storage, which means a breach, a court order served on this site, or whoever holds the site's service key, though the code never opens a file except to hand it to its owner. If that is the wrong trade for a file, the timeline on Saved pages keeps photos on this device only, as the section below describes.
Why: So the papers of a case, the ticket, the letter, the photos, are in one place on every device, still there after the phone is gone, and ready to hand to a lawyer. It is part of a case or Pro because keeping files costs money every month they are kept.
That your account has had its free paper reading
The free reading on Read my paper sends the one file you choose to Anthropic, the company whose model reads it, under Anthropic's terms for its API, and shows you what it found. Neither the file nor the reading is kept anywhere on this site: the file passes through the server for that one request and is not written down, and the reading lives in your browser tab until you leave the page. What is kept is one row with your account's id, the time, and a salted hash of your email address with any plus tag taken out, and at Gmail its dots, which is how the reading is one per account and one per inbox; the hash cannot be turned back into the address, and the row goes when the account goes. The reading also counts as one of your free questions, through the same counter as Ask, which holds no account.
Why: So anybody holding a ticket or a notice can see what a case would do with it once, without paying and without the paper being kept. The one row is the least that makes once mean once.
That a card has had Pro's free days, if you start them
When Pro starts with free days, Stripe's fingerprint for the card, which is Stripe's own number for a card and not the card number, is run through a salted hash on this server, and the hash is kept with the id of the subscription it started. Nothing else about the card is stored here: Stripe holds the card, and this site never sees its number. The hash stays when an account is deleted, which is what keeps the free days once per card.
Why: So the free days are once per card as well as once per account. A new account paying with a card that has had them starts Pro paid, and the hash is the least that makes that check possible.
What you write in a case, if you write anything
On a case's own page: whether the case is about charges or a claim of your own, the charges you add, the dates you add, what you wrote happened and on which day, the costs you list with the amount you typed for each, the people you add with the phone number or address you typed for them, your notes, the name you gave the case's helper and what you wrote the case is about. When you ask a question inside a case, a short brief of it goes with the question to Anthropic's model so the answer is about the law your situation turns on: what you wrote it is about, the charges, the dates ahead, the kind of each paper read, for a claim the costs you listed and their total, and your last two questions in that conversation with the headline each got. None of that is kept with the question. Each is kept with the case it belongs to, and the browser can read only its own account's; it is written only by the site's server after checking the case is yours. Nothing reads it but the page that shows it to you. Removing an entry removes it, open case or closed, and deleting the account removes every one of them with it. The same plain words as the files above: this is your situation written down with an account beside it, and it can be reached by a breach, a court order served on this site, or whoever holds the service key. Saved pages, in your browser and further down, does a version of this that never leaves the device. A case folder, the zip with the summary and every paper, is put together on your own device; MyRightz sends it to nobody, and it goes only where you share it.
Why: So the charges, the dates, what happened and who to call are in one place on every device, organized by the time you talk to a lawyer rather than remembered. A charge you pick from the guide is shown with what it carries, read from the guide itself each time the page opens.
WHAT IS REFUSED
These are not oversights that might be filled in later. Each one is a thing the site could easily do and does not.
- A reason to make an account. Every section, statute, case and charge is readable without one, and reading creates no record of you at all. An account keeps your saved pages across devices and, with a case or Pro, is where a reminder or a law change email is sent. What it holds is listed above.
- A cookie, unless you sign in. Reading the guide sets none, on any page, ever. Signing in sets a session cookie, because a session is what a cookie is for: it carries the session and nothing else, script cannot read it, and signing out removes it. There is no tracking cookie here at any point, for anybody.
- Your IP address, anywhere. Not in the search log, not beside a contact message, not against a question asked of the answer agent. The ceilings described above count a salted hash of it that rotates every day and is computed before anything is stored, so what the database holds is a number that cannot be turned back into an address or lined up with tomorrow's.
- A visitor identifier for anybody reading. No id, no fingerprint, and nothing that connects two visits by the same person. Somebody signed in has a session, which is the thread they asked for, and it reaches their saved pages and stops there: the search log, the contact messages and the answer agent's counter are all written with no account beside them, and the answer agent's counter never stores the question at all.
- YouTube's player on a page you did not ask it for. A bare embed ships about a megabyte of Google's player and sets cookies on every page it sits on, whether or not anybody presses play. Here the card is ours until you press it, the player is the no cookie domain, and this is enforced rather than intended: the content security policy this site sends permits exactly one frame from anywhere, that player, and nothing else. What a video card does fetch before you press anything is its thumbnail, which is the next section.
ON YOUR DEVICE ONLY
Everything this site keeps in your own browser is listed here, 18 keys in all, each with what it holds and for how long. Clearing your browser data removes every one of them, and nothing on this site notices.
Local storage, until you clear it
The theme you picked. Light or dark, and only if you picked one. Leave it on the system setting and nothing is written at all.
Local storage, until you clear it
Your saved pages. The slugs of the sections you added, so the list is still there when you come back. Signed in, the same list is on the server, which is the whole of what an account is for.
Local storage, until you clear it or choose Forget it
Your state. The name of the one state you picked, written as its address, such as michigan, so the front page, the menu, the search and the footer open on that state's law instead of asking again. Opening a state's page writes it only when nothing is there yet. It never leaves your browser: it is not a cookie, the server never reads it, and Forget it on the front page removes it.
Local storage, until you clear it
That you closed the strip at the top. One word, the word closed, written when you close the banner explaining what this site is, so it does not reappear on every page afterwards. It says nothing about who you are or what you read, and nothing is written at all unless you close it.
Local storage, until you turn it off
Whether answers are read out loud. One word, present or absent. The reading is done by your browser's own speech, and this site makes no request to do it; the one exception is a voice the picker marks Online, below. Nothing here listens: a question asked by voice goes in through your phone keyboard's dictation, which is your phone's, and this site never asks for a microphone.
Local storage, until you clear it
The voice that reads to you, and how fast. The name your device gives the voice you picked, and a speed. The voices are the ones your phone or computer already has, so this site fetches nothing to play them and sends nothing. A few browsers speak some of their voices from their maker's servers instead of on the device; the picker marks those Online, and choosing one means your browser sends that company the words being read. No route takes the choice and there is no version of it on an account. Nothing is written at all unless you pick a voice or a speed.
Local storage, until you clear it
What you asked the answer to call you. A first name, only if you gave one, so an answer can open with it. It rides along with the question you send and is not written down at the other end: there is no column for it, the request is not logged with it, and the counter that decides whether you have asked too many questions hashes an account or an address and never the body. Nothing is written at all unless you set it, and clearing the field clears it.
Local storage, until you clear it
Whether the site buzzes and whether it makes a sound. Two words, true or false, for vibration and for sound. Sound is off until you turn it on, because this site gets opened in rooms where a noise is the last thing anybody needs. The sounds are built out of two tones by the browser at the moment they play, so there is no audio file to fetch and no request to anybody. Nothing here reaches a microphone: this site does not ask for one anywhere, nothing is recorded, and there is no code in it that could.
Local storage, until you clear it
The dates you are counting. One line per period you kept on Your clock: which period it was and the date you gave for it. This is the most telling thing on the list, because a period and a date together say what is happening to somebody and when, so it is the one thing here that has nowhere else to go. There is no route that takes this list, no table that holds it, and no copy of it on an account, signed in or not. The one exception is a date you choose to set an email reminder for, on a case or Pro: that one period and date are then stored with your account so the email can be sent, as the reminder entry above says. Clearing this browser clears the list, and that is the trade.
Local storage, until you clear it
The name you gave your saved pages, their timeline, your notes and your questions. Two fields you typed: what the situation is called and whatever you wrote down about it. Everything else on that page is assembled from things already listed here, the saved sections and the dates. Notes about a situation are the most telling thing on this list after the dates, so they are kept the same way: no route takes them, no table holds them, and there is no version of them on an account. A paid case's own page, which does keep what you write on it with your account, is a separate thing, described under what is kept. Printing is done by your browser, from the page already in front of you, and nothing is sent anywhere to produce the sheet.
Local storage, until you clear it
Which lines are on your stop card. The short names of the lines you picked, and nothing else. The words are read from the guide each time the card opens, so a corrected section corrects the card. No route takes the list and there is no version of it on an account.
IndexedDB in this browser, until you remove it
Photos and files you attach to the timeline on Saved pages. Each file as you gave it, with its name, its size and the line it belongs to. It is never uploaded: nothing on Saved pages sends a file anywhere, and nothing reads what a picture shows. Removing a line removes its files, clearing the writing on Saved pages removes all of them, and clearing this browser's site data does too. That is the trade for keeping them off any server: they are on this device only. The files you add to a paid case are a different thing, uploaded on purpose, and are described under what is kept.
Local storage, until you clear it
The day you last opened each state's front page. A state's name and a date, one pair per state you have opened, so its front page can say how many of the pages in New in that state arrived since you were last there. No time of day, no page you read, and nothing about what you searched for. It is never sent anywhere.
Session storage, gone when the tab closes
The words of a search that found nothing, on their way to the request form. Written only when you press Ask for a page on this under a search that came up empty, so the words are already in the request form when it opens. The form removes them the moment it reads them, and nothing is sent anywhere until you press Send.
Session storage, gone when the tab closes
The words of a search that found nothing, on their way to the question box. Written only when you press Ask it as a question under a search that came up empty, so the words are already in the question box when it opens. The box removes them the moment it reads them, and nothing is sent anywhere until you press Ask. They never go in the page's address, where a server's logs would keep them.
Local storage, until you clear the card or this browser
Your stop card as it was last shown, with the date. The words of each line on your stop card and their sources, written when the card is shown, so the No connection page can show it with no signal at the roadside. It is a dated copy of what was on your screen and is never sent anywhere. Clearing the card removes it.
The browser's offline cache, until you clear this site's data
One page, the No connection screen, and the three typefaces it is set in. Kept so that when a page cannot load for want of a signal, the site, and the app, show a plain No connection screen with Try again and Back instead of the browser's error page. It is the same page and the same three font files for everybody and holds nothing about you. No other page is kept: every page comes from the network each time.
Session storage, gone when the tab closes
The last few pages you moved through in this tab. Up to ten, and the Back button is the only thing that reads them. It uses them to answer one question, whether there is a page of ours behind this one, so that Back does not throw somebody who arrived from a search result off the site entirely.
WHAT LEAVES THIS SITE
Reading sends nothing to anybody else. A section, the whole file, the clock, the charge lookup, the glossary, the contact page and this page were each loaded in a browser with the network watched: zero requests left this site. The few places your browser is sent somewhere else are listed first. After them, every company that handles something for this site, and exactly what each one is given.
A video thumbnail, on two pages
The footage shelf loads a picture for each clip on it, and the front door loads one. They come from YouTube’s image host, so that host is told an address asked for the picture of a particular video. It is not told which page you were on: this site sends a referrer policy that gives another origin the bare name of this site and never the path, so the page you are reading does not travel with the request. No cookie is set and no script of theirs runs, because the policy permits that host for images and nothing else. Every other page on this site loads no picture from anywhere but here.
The traffic counter
Vercel Web Analytics, described above, served from this domain rather than somebody else’s.
What Vercel does with the counts on their side is theirs to describe rather than ours to paraphrase, so it is worth reading from them directly: Vercel’s analytics privacy documentation.
The shop, and only when you press checkout
The merch pages show pictures from Printful, which prints and ships the shop’s orders, but your browser never fetches them from Printful: this site fetches each picture itself and serves it from here, so looking through the shop tells Printful nothing about you. Pressing checkout opens the MyRightz store at printful.me, which Printful runs. From that point the order, your address and your card are given to Printful under its own privacy policy, and none of them reach this site.
WHO HANDLES WHAT
5 companies, each given only what its job needs. Nothing about you is sold to any of them, and nothing is shared with an advertiser, because there is none.
Vercel
Hosts the site and counts traffic
Every page is served from Vercel's servers, so a request for a page passes through them the way a letter passes through a post office. The traffic counter is described above.
Supabase
The database, sign in, and file storage
Everything listed under What is kept is stored with Supabase, and it sends the sign in link to your email address. A case's files sit in its private storage.
Anthropic
The model behind Ask and Read my paper
A question you send to Ask, with the state and the statute text it is answered from, and inside a case the short brief described above. A paper you choose to have read, with whatever is printed on it. Sent under Anthropic's terms for its API; your account and your email address are never sent with any of it.
Stripe
Takes payment for a case or Pro
Your card and anything it asks for at checkout, on Stripe's own page, and your email address so the receipt reaches you. This site keeps only what the plan entry above lists.
Resend
Sends the site's emails
A reminder or a law change email, with the address it goes to, and a message from the contact page on its way to the inbox that reads it.
If something here is wrong
Tell us and it gets fixed, or the page gets corrected. The contact page takes a message without an email address if you would rather not leave one.