Only what we need.
You can explore places without an account or location permission. We don’t ask for medical diagnoses.
What’s public.
Published notes, their needs tags, your display name, optional visit date, and helpfulness totals are public. Notes may be indexed by search engines. Your email, saved preferences, and reports are private.
What we store.
Accounts store an email address, a securely hashed password, a display name, and optional preferences. We use an essential session cookie to keep you signed in. Preferences are also saved in this browser. Note drafts are stored in this tab’s session storage for up to 24 hours and removed on publication. Closing the tab clears its session storage.
Location stays purposeful.
“Near me” requests your location only when you choose it. Coordinates are used for the current nearby search, not saved as a personal location history. Area-based provider caches can contain map bounds without an account identity.
External map services.
Maps are loaded from OpenFreeMap by default; it receives the IP address and map areas needed to serve tiles. Submitted searches are sent through our server to the configured geocoder; area searches and access-detail requests go to the configured OSM provider. Don’t enter private addresses or confidential information into place search. These providers have their own privacy policies.
No advertising or tracking analytics.
The application contains no advertising or analytics trackers. Short-lived abuse-control records use hashed keys; the operator’s reverse proxy or server may retain operational logs. Production operators should minimize and set retention for those logs.
Removing content and account access.
You can remove your own published notes. They disappear publicly but remain in the database as a moderation record. For this self-hosted first release, full account export or erasure is handled by the installation’s operator; there is no automated erasure request flow. Backups can retain earlier data until they expire.
About this release.
This notice describes the software’s current behavior. Before a public launch, the operator must supply contact details, a retention policy, and an appropriate process for privacy requests.