Support

Use this page for support contact details, self-service account links, privacy and deletion requests, and the public documentation pages needed for store listings and third-party authentication setup.

Contact

Email: michael.kappel@locationnotes.com

Phone: (630)362-7576

Mailing address: 1331 S. 51st Ave, Cicero, IL 60804

Self-service account pages

Most account tasks are already available on the website without opening a support ticket. If a page below requires authentication, LocationNotes will send you to login first and then return you to the page you selected.

• Account for public profile settings, linked-page visibility, and time zone.
• Account security for password changes, password reset links, email changes, and linked-provider management.
• My account data for personal JSON export.
• Team data for team-wide JSON export when you are a current team admin.
• Beta access for Android pre-release access, request status, and the Beta Testers team page.
• Delete account and data for the permanent deletion path and pre-delete export guidance.

Public pages and discovery

• Public teams for the public team directory.
• Search notes and categories for public search plus the signed-in private-result filters.
• Authentication for current provider behavior and callback URLs.
• API documentation for bearer login, sync, notes, categories, teams, and account-delete examples.
• Privacy and Terms for public policy pages.

Concept guides

• What is a User? for profile pages, identity, ownership, teams, and account-scope rules.
• What is a Team? for titles, slugs, joins, moderation, exports, and deletion boundaries.
• What is a Note? for maps, hierarchy, comments, visibility, sync, and trackable relationships.
• What is a Trackable? for public codes, secret codes, QR flows, activation, groups, and journeys.

Trackables and code flows

Trackables add a second layer on top of notes. They can be discovered by public code, activated by short secret code or private scan QR, attached to notes while an active browser session exists, grouped into inventory sets, and commented on when the relevant policy allows it.

• Short secret codes and private scan URLs are shown only once at creation. After that reveal, LocationNotes will never display them again on ordinary pages or normal API reads.
• Public codes are for public routing. Secret codes and private scan URLs are possession-based access credentials.
• A trackable may be unactivated, personally activated, or team-activated. Unactivated items cannot create new map activity or receive comments.
• Trackable groups can provide fallback item title and description values, but activated items may need their own explicit metadata depending on how the group was created.
• Changing a trackable from one group to another is a detach-first workflow. It must be removed from the old group before it can be associated with a new one.
• Trackable API docs cover create, lookup, activation, active-session, comment, and group-management routes.

Privacy, legal, and deletion requests

• Account export: Download your account data
• Team export for admins: Download team data
• Account deletion guidance: Delete account and synced data
• Facebook Login deletion endpoint and status page: Facebook data deletion

Use support contact when the issue is not already available through self-service, such as a privacy concern, an age-related report, a report of unlawful public content, a broken third-party sign-in flow, or a team membership problem that a team admin cannot resolve.

What to include when you contact support

• The page URL where the problem occurred.
• Your LocationNotes user name or team slug, if the issue involves a specific account or team.
• The note ID, trackable ID, trackable public code, invite link, or public page URL if the issue involves specific content.
• The exact error message shown on screen, or a screenshot if the wording is hard to copy.
• Whether the issue happened on the website, the Android app, or during a Google or Facebook sign-in flow.
• If the issue involves a secret code or QR scan, say whether you were creating a trackable, activating it, browsing an active secret-code session, or attaching it to a note.

Do not send passwords, provider secrets, or full payment-card information in a support request.

Store and provider setup

The same LocationNotes site is used as the homepage, privacy, support, delete-data, and authentication-information surface for Google Play, Google OAuth, and Meta configuration. If you are configuring a provider, start from the Authentication page and use the exact URLs published there.