Privacy policy
poolScout (poolscout.org) is a personal, non-commercial project: a community map of publicly playable pool tables. Last updated November 17, 2026.
What we collect
- Reports. The information you submit about a venue (table condition, price, and so on) is public and shown to everyone. Reports are not shown with your name or email.
- Account details. If you create an account: your email address and, for email accounts, a hash of your password (we never store the password itself). If you sign in with Google, we receive your Google email address and a Google account identifier. We request the basic profile scopes (openid, email, profile). We use the email and the identifier, and from your name we make one suggested display name (your first name and last initial, like “Parker_H”) to offer you if you choose a public name. The name itself is not stored.
- Device and abuse protection. The first time you visit, we set a cookie holding a random token on your device. We log that a new visitor arrived (a timestamp, with nothing that identifies you) so the site owner can see how many people find the app. A second cookie keeps a small count of how many different days you have visited, so the owner can see how often people come back; that count stays in your browser, and our server only adds you to an anonymous tally (how many browsers have visited on 2 days, 5 days, and so on) plus a timestamp for the return visit, never anything that identifies you. With it we keep only a coarse note of where you came from, such as a search engine, another website's name, or a tag on the link you followed (like “qr-hillside”), and whether you landed on the map or on a place page. We never keep the full address of the page that sent you, your IP address or your browser details for this, and visits by search-engine crawlers aren't counted. If you later submit a report, we store only a hash of the token. This lets us count your reports once and carry them over if you later create an account. We also store a keyed hash of your IP address, never the address itself, to limit spam.
- Location. If you tap "Near me", your browser shares your location with the page to sort venues by distance. It is not sent to or stored on our servers. If you add a place using "Use my location", the coordinates are saved as that place's location.
- Check-ins. If you check in at a place, your phone sends its position once so we can confirm you are within about 150 meters of it. We keep only which place, which account and when, never the position itself. Check-ins are not shown with your name: other players see only a count for the day (like “3 check-ins tonight”).
- Your public name (optional). If you choose a name, it is shown on a place's card when you are the person who has checked in there on the most different days (the “top regular”; at a place with a single check-in, that's the one person who has checked in), in the app only (not on pages search engines index). It never shows when you are somewhere, or a history of where you've been. You can change it, remove it, or hide it at particular places in Settings.
- Comments. A comment you post on a place is public, with the name you chose and the time. It is stored with your account so you can delete it, and it is not monitored or moderated. If you delete your account, your comments stay up without your name (shown as "poolScout member") unless you choose to delete them too. We do not show comments on the public place pages that search engines index. Links in a comment are shown as typed and are not fetched or previewed by us.
- Contact messages. If you send us a message with the Contact form, we store it with the time and, if you were logged in, your account email, or the email you chose to give so we can reply.
- Places you add. A place's name, address (if given) and location are public. The addition is linked internally to your device token (and your account, if logged in) so we can limit abuse.
- Address search. When you search for an address while adding a place, the text you type is sent from our server to the US Census Bureau geocoder and, if that finds nothing, to OpenStreetMap's Nominatim service. Your own IP address is not sent to them.
Cookies
We use only essential cookies: a device token, set on your first visit (up to one year), a login session (30 days), and a short-lived cookie during Google sign-in. We use no advertising or analytics cookies.
How we use it
To show venue information, work out the community's consensus answers, keep your account working, send account emails (confirmation and password reset), and prevent abuse. We don't sell or share your information for advertising, and there is no advertising on poolScout.
Who handles it
poolScout runs on Vercel (hosting), Neon (database), and Resend (account emails), and uses Google for optional sign-in, the US Census Bureau and OpenStreetMap Nominatim for address search, and OpenFreeMap/OpenStreetMap for map tiles and data. Your browser requests map tiles directly from OpenFreeMap.
Your choices
You can log out at any time. You can delete your account yourself in Settings: this removes your email, name, check-ins and sign-ins. The reports you submitted stay on the map as anonymous contributions, no longer linked to you, unless you choose to delete them too. You can also contact us at the address below.