Map-first workflow
The Android app opens to nearby map markers and shows online/offline status continuously.
EVERYWHERE IN ONE PLACE
Capture location notes for site visits, operations, internships, research walks, and class projects 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.
Place, history, and access stay separate: the journey stop preserves the snapped coordinate, the note keeps its own editable record, and the note's visibility plus required access scope decides who can open note content.
If a code starts with GT, TB, GK, or GC, LocationNotes points you to the origin site. If the item came from a retired or private system and you still have it, create one trackable and use Bring your own secret code.
Public notes stream from the LocationNotes API. Basemap uses Google Maps when a website API key is configured.
Nearby public notes
Scroll sideways to browse nearby notes without losing the map context.Core product behaviors for operations, campus, and project work.
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.
The quick-start documentation hub for users, teams, notes, trackables, and the rules around them.
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.
Trackable groups can provide fallback item title, description, and default link values while the group page shows which items are still waiting for activation.
Learn how LocationNotes trackables can power conference giveaways, branded handouts, QR-based swag, and post-event usage insights.
LocationNotes lets your team keep company-owned URLs on printed SWAG while still using our trackable workflow, exports, and API behind the scenes.
Learn which public URLs are safe to share, why the simple public route families matter, and which page shapes are live today.
Learn how verified external links appear on teams, notes, trackables, and grouped defaults without becoming internal page routes.
Learn the difference between required security email and optional feature alerts for comments and trackable activity.
Learn how uploads are screened, resized, stored, reported, and permission-checked through their parent profile, note, team, trackable, or trackable-group page.
Learn which help tickets start from the support page, how tracking works, and when a report button or an error ticket is the better fit.
Public team pages can be viewed without signing in, but team management and workspace tools still require an authenticated account.
Admins can invite members, approve membership requests, deny requests, remove members, and remove invitations at any time while connected to the API.
Admins and members can create team notes offline after team membership has been synced to the device.
If a team admin removes a member note and the original creator still exists, the note becomes that creator's private personal note instead of being fully deleted.
Team membership changes, approvals, invitations, removals, and team deletion require an active API connection.