Map-first workflow
The Android app opens to nearby map markers and shows online/offline status continuously.
Live public map
The front page loads public notes directly from the API and starts the map over Chicago. Location access is requested only later in workflows that actually need it, such as creating a note.
/api/notes/public/boundsPublic notes stream from the LocationNotes API. Basemap uses Google Maps when a website API key is configured.
Nearby public notes
Scroll sideways to browse the notes closest to your current map center.Offline-first location intelligence
Capture location notes with categories, team context, and visibility controls while offline, then sync safely with GUID-based conflict handling.
Use this lookup only for exact public codes or exact short secret codes. If the code does not match exactly, the page stays here and shows a not-found message instead of redirecting.
Private scan URLs are intentionally not entered by hand here. They are meant to be scanned and routed through the website or app scanner flow.
A public code opens the normal public trackable page. A secret code or private scan QR creates a remembered active-trackable session on this browser so later note flows can attach the trackable without re-entering that secret.
The Android app opens to nearby map markers and shows online/offline status continuously.
Create private notes locally with or without an account. Signed-in members can also create team-associated notes offline.
Authenticated users can start teams, invite members, approve requests, deny requests, and manage team membership.
Browse by nested categories or spatial map view with the same underlying sync model.
Notes can stay personal-private, be published publicly, or belong to a team while remaining team-private or public.
Deleting an account does not automatically delete team contributions. Team notes stay with the team until admins remove them or the team is deleted.
Use local credentials, Google, and Facebook with multi-provider account linking.
Public privacy, support, auth setup, and data deletion pages are served from the same domain as the API.
Learn how identity, profile visibility, ownership, teams, notes, and trackables relate.
Learn how titles, slugs, visibility, invites, moderation, exports, and team ownership work.
Learn how location, hierarchy, comments, visibility, sync, and trackable association fit together.
Learn how public codes, secret codes, QR scans, activation, groups, maps, and exports interact.