effective: september 2026
when you use rantr, we collect:
we use your data to:
preparing a complaint does not publish your words, join a case or contact a company. the description is processed by typesafe (jev) and openai to draft and check the letter. we do not save the complaint description or generated letter as a public rant. edits made to the generated letter stay in your browser unless you copy or share them. publishing a story is a separate action labelled as public. imported public posts are displayed as source links without their text or order details.
when you leave an address on a rant (following it, claiming your own, or as you release it), we send it an email asking you to confirm. the link opens a page with a confirm button: opening the link confirms nothing (mail scanners open links on their own); only pressing the button counts. until then we send it nothing else and it doesn't count toward any rant's signal. the link works once and expires after 7 days. if you didn't ask, ignore it.
if you claim your own rant, the email with your private link leads to the same page with the confirm button.
so nobody can use rantr to flood an inbox, we send one address at most 3 confirmation emails an hour, and at most one every 10 minutes per rant. addresses that bounced or marked us as spam get nothing more.
once confirmed, we email you when something emerges from that frustration. that can include offers from companies or builders who say they fix the problem; those emails are labelled "offer" and say when rantr may be paid for them. every email has a link to stop them.
if an address that asked us to stop is left on a rant again, we send it a single confirmation (at most one a day). we only write to it again if someone presses confirm on that email; otherwise nothing changes.
ever. we're not in the business of selling information.
we use these services:
on campaigns, a 90-day essential cookie remembers this browser so you can change votes, publish an experience, withdraw it and mark similar experiences. we store a hash with those actions. browser counts do not represent verified people. as you type on a campaign, we send your draft to Typesafe (JEV) for reading and suggested connections. we cache a hash and reading result for reuse within 10 minutes, not the draft text; published experiences are public. withdrawal hides the text from public pages, but cannot remove copies already shared.
by default we use only what is essential: a campaign voting cookie, a language cookie and your cookie choice (kept in your browser). no tracking cookies unless you say yes.
if you choose "allow analytics" in the banner, we load google analytics, which sets cookies (_ga) to count visits and see which pages help. you can change your mind at any time.
your rant's private page never loads google analytics, and no page sends it private or confirmation links.
you can:
to exercise these rights, use the account settings or email [email protected]
rants: they stay published until you ask us to take one down at [email protected]; when we do, we also delete the addresses left on it.
drafts: we don't store them. while you type, the text is sent to typesafe and openai to read it; what we read from it (which can quote short parts of it) stays in the server's memory, keyed by a fingerprint of the text, for at most 10 minutes and is then dropped.
emails: we keep a one-way hash (sha-256) of every address we asked to confirm and every address we told about an emergence, with the time, so we never write twice and can enforce the send limits. they are kept as long as the rant or the emergence exists. we also keep a copy of every email we send (recipient, subject and text) in our send log.
deleted accounts are permanently removed after 30 days.
you must be at least 13 years old to use rantr. if you're in the EU, you must be 16+.
we'll update this policy occasionally. check back here for changes.
questions? email [email protected]