Privacy Policy
This page describes what Third Platz actually does today, not a template of what a bigger company might do. When something changes, this page changes with it. Last updated 26 October 2026.
The short version
- Reading needs no account. Contributing needs one, made with an email address or with Google.
- What you contribute is public by design. Your email address, your votes and your sign-in details are not.
- We keep our own record of what happens on the site (for example "a vote was cast on this page"), to see what works. It never includes your IP address or anything you typed, and we use no outside analytics or advertising tools.
- A few service providers handle data for us: Cloudflare (every request), Resend (account emails) and Google (only if you use Google sign-in, plus its sign-in prompt for visitors who aren't signed in). We don't sell data or share it with anyone else.
Information you give us
- Your account. If you sign up with email: your email address, your handle and your password, stored only as a secure hash. If you sign in with Google: your name, email address and the link to your Google profile photo, which Google sends us when you choose to continue. We use your name to suggest your handle; the photo isn't shown anywhere on the site today.
- What you contribute. Lists, places and things you add, short descriptions, takes, reviews, questions, comments and votes, all linked to your account. Everything except your votes is public.
- An optional home location, a city or country only, never a precise address. You set, change or clear it on your own profile; it's never guessed from your IP address. It powers the optional "Locals" view on list pages.
- Reports. If you report something, we keep the reason you picked and any note you wrote, so a moderator can act on it. You can report without an account.
Information collected automatically
- Sign-in sessions. When you sign in, we store the session with your IP address and your browser's user-agent string (which browser and device type), to keep you signed in and to help spot misuse of your account.
- Rate limiting. To stop abuse, we count recent requests per IP address in the server's memory. These counts aren't written to the database and disappear within the hour.
- Product events. We record a small, fixed set of actions, such as a vote, a post, a sign-in or the Google sign-in prompt being offered, together with the page it happened on and your account if you're signed in. We never store your IP address, user agent, referrer or anything you typed, and we never set a cookie for it. The data stays on our server, is never shown publicly and is used only for overall numbers, not to profile anyone.
- Automated traffic. When a bot, scraper or AI agent (not a person using a browser) reads our machine-readable pages, such as the markdown versions, robots.txt and llms.txt, we log what kind of agent it was, the page, the hour, and a salted hash of its IP address. This only produces weekly totals; the hash is never linked to an account.
- Searches with no results. When a search finds nothing, we keep the normalised search words, not linked to whoever searched, as ideas for what to add. They're never shown publicly unless a person reviews and approves them.
Cookies and storage on your device
We use no advertising or tracking cookies. What we do use:
- A session cookie when you're signed in.
- A legacy identity cookie, only if an older version of the site gave you one before accounts were required. It's never issued now; it's only read so your old contributions still show as yours.
- Short-lived security values while a Google sign-in is in progress, so it can't be hijacked.
- Storage in your own browser, which never leaves your device unless you post: the places you recently viewed (local storage), any unsent draft, so it survives signing in, and a note that the Google prompt was already offered in this tab (both in session storage, cleared when you close the tab).
- Cloudflare, which protects the site, may set a strictly necessary security cookie.
Who else handles data
- Cloudflare. Every request to the site passes through Cloudflare's network for speed and protection, so Cloudflare processes your IP address and the request.
- Our hosting provider runs the server and stores the database.
- Resend sends account emails (verifying your address, resetting your password), so it receives your email address and that message.
- Google. If you choose Google sign-in, Google confirms your identity and sends us the details listed above. Separately, for visitors who aren't signed in, most pages load Google's sign-in prompt from accounts.google.com a few seconds after the page opens (never on sign-in pages, and at most once per tab). Loading it means Google receives that request, including your IP address, and may read its own cookies if you're signed in to Google. Google's privacy policy covers what it does with that. Close the prompt and it won't come back in that tab.
- Classifying what you post (which place and topic it's about) runs on our own server today. If we ever send that text to an outside AI provider, we'll name the provider here first.
- We don't sell personal data, use advertising networks, or share data with anyone not listed here, unless the law requires it.
What's public
Contributions are public by design, so don't put personal information in anything you post that you wouldn't want public. Every account has a public profile page (/u/{handle}) that collects your public contributions: lists, places added, posts, comments and their counts. It never shows your email address or your votes. Your karma score, shown next to your handle, is worked out only from those public contributions, never from how you voted. Individual votes are never published.
How long we keep it
- Your account and contributions: until you ask us to delete your account. Anything you delete yourself comes off the public site straight away.
- Session records, including IP address and user agent: for the life of the session. Signing out deletes it; expired sessions are deleted once they're noticed, and some can stay in the database until then.
- Product events: we haven't set a deletion date yet. They hold no IP address, user agent or text, and this page will say when a limit is set.
- Automated-traffic log entries: 30 days. The weekly totals made from them have no per-request detail and are kept.
- Searches with no results: up to 90 days, unless approved as a suggestion.
- Reports: kept as a record of moderation decisions.
Your choices
You can read everything without an account. You can set or clear your home location at any time on your profile. You can close the Google prompt, or turn off third-party sign-in prompts in your Google account settings. You can block cookies, though then you can't stay signed in. To get a copy of your data, correct it or delete your account, email us (below). We'll do it and confirm.
Changes to this policy
When what we collect or who handles it changes, this page is updated at the same time, with a new date at the top.
Contact
Privacy questions and requests: [email protected].