Your privacy, scout.

Public preview notice · Updated November 3, 2026.

What we store

Accounts contain your email, public scout name, verification status and a password hash. We also store submitted reviews, ratings, photos, bathroom tips, business claims, moderation decisions and support requests. We use these records to run accounts, publish approved contributions, verify business authorization and respond to problems.

What other scouts see

Approved review text, ratings and your public scout name appear on public restroom detail pages and can be indexed by search engines. Approved photos and the community feed remain available to signed-in members. Approved location details can appear on the map. Your account email, business contact details, pending photos and support requests are not included in public listings. Moderators can access these private records to review them. Do not submit personal information or photos of people using facilities. Photo uploads are re-encoded to remove original metadata.

Location and device storage

On arrival, your browser may ask permission to center the map near you. You can decline and use city or ZIP search instead. Your most recently selected area is remembered on your device. California restaurant and restroom lookups use bundled map-data snapshots on our server. Panning the map refreshes results around its approximate center. Live-provider searches outside that directory send approximate coordinates to the map provider; map tiles also reveal the map area being viewed and your IP address to the tile provider. California city and ZIP suggestions are bundled on-device; US Census suggestions also come from our server. When you choose address lookup for a submission, the street address is sent to the US Census geocoder to obtain an approximate position. Theme and first-visit notice preferences are stored on your device. Saved places and unfinished local activity may be stored in your browser. Session cookies keep you signed in. This build does not include advertising trackers or third-party analytics scripts.

Service providers

Render hosts the app and stored data. Resend processes verification email addresses and messages. OpenStreetMap tiles supply maps; Geofabrik supplies our California OpenStreetMap extract. Overpass services can supply live searches when a bundled directory is unavailable. You can download the California restaurant directory and mapped restroom directory, plus the mapped building address associations, under the Open Database License. The city/ZIP index uses Census geographic data. Firebase Authentication stores persistent accounts and supports Google sign-in. Discord sign-in uses a server-side OAuth flow linked to Firebase. Cloud Firestore stores community content, private profiles, roles and moderation records. Those providers process the information needed for their features. AI photo screening is optional; human review still applies. Hosting and delivery providers may keep operational logs under their own policies.

Retention and requests

There is currently no automatic account-data deletion schedule. Records are retained until removed by the operator; backups can retain older copies. Accounts and acknowledged community submissions are stored persistently in Firebase. Render uses a temporary local cache; that cache is rebuilt from Firestore after a restart. Use Help & support to request access, corrections or deletion. These requests are reviewed manually and identity must be checked before private information is released or an account is removed. You can stop device location access in your browser and clear locally saved places through browser site-data settings.

These pages describe this public-preview implementation. The operator must review the notice, retention settings and contact process before a wider launch.