Bug report

Report a problem in LocationNotes

Use this form when the website or app is not behaving the way you expected and you are not already on a tracked error page.

LocationNotes is used for field documentation, project coordination, internships, research, and campus work, so support requests are often easiest to resolve when they include the exact page, team, note, or code involved.

Bug report

Report a problem in LocationNotes

Use this form when the website or app is not behaving the way you expected and you are not already on a tracked error page.

What is a Support Request? explains the different support-request types, when to use report buttons instead, and how status tracking works.

Only subject and description are required. The other fields are optional but can help support answer faster.

Open the general support form instead.

Signed-out requests are allowed, but add a contact email if you need a reply.

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, Experience and privacy mode, preferred map source, and time zone.
• Account security for password changes, password reset links, email changes, and linked-provider management.
• Support Tickets for tracked request status and super-admin resolution notes when you submitted while signed in.
• 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, compliance, 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.
• What is a Trackable Group? for shared defaults, activation dashboards, item batches, and grouped ownership workflows.
• What is a 3rd Party? for the current map, analytics, hosted-map, and provider-sharing rules.
• What is an External Link? for verification, adult-content screening, exit-page behavior, and export or deletion coverage.
• What is an Image? for galleries, moderation screening, resized delivery copies, reporting, and parent-page visibility rules.
• What is a Support Request? for general help tickets, tracked status, reply expectations, and when to use a report button or error ticket instead.

Images and uploads

Images can be attached to profile pages, notes, team pages, trackables, and trackable groups. The same parent item that controls who can open the page also controls who can open the images.

• Uploads are screened before save, and the service stores only resized JPEG copies instead of keeping the original upload as a downloadable website file.
• Image cards on public or shared pages can show the reporting control so unsafe, misleading, or misplaced uploads can be sent into the same moderation workflow as other content reports.
• Signed-in users who want one note per image can use Bulk Image Upload from the My menu to review metadata, map pins, and one shared category before saving.
• What is an Image? and Image API endpoints cover gallery rules, file variants, upload routes, and delete behavior.

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, commented on, and logged directly on the journey map when a simple location report is enough. When the question is about a route, include whether the issue is with the saved stop snapshot, the current visible notes at that coordinate, or the note access that should have come from an unlocked trackable.

• 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.
• Think of trackables and trackable groups as Visible Once Accessed or Always Visible To Everyone. A signed-in account that unlocks a Visible Once Accessed trackable can keep reopening it later without the secret code again.
• My Journeys shows journey-ready trackables you own, your teams own, or can still reopen after secret-code or QR access.
• A trackable may be unactivated, personally activated, or team-activated. Unactivated items cannot create new map activity or receive comments.
• Anonymous trackable comments and direct map reports are allowed only when this browser already has active access to that specific trackable or the caller resends its exact secret code or private scan access. Anonymous posts can only be removed later by the trackable owner or current team admins.
• Authenticated trackable API flow walks through lookup, activation, note attachment, direct reporting, moderation, and cleanup for signed-in clients.
• Anonymous trackable API flow walks through secret-backed comment and map-report posting without an account, including the friendly no-self-delete limitation messaging.
• Trackable API error reference lists machine-readable error codes and the most common reasons a trackable action failed.
• Export and deletion questions are easier to answer when you say whether you expected a direct location stop, a note-backed stop snapshot, the current notes-at-coordinate read model, or the separate note-link records in account or team export.
• If the question is about restore or transfer, say whether the source was account JSON, the portable ZIP with or without images, or a team JSON export, and whether the target account already had matching categories or notes.
• Trackable groups can provide fallback item title, description, and default link values while the group page shows which items are still waiting for activation.
• Changing a trackable from one group to another is a detach-first workflow. The full group-specific rules live on the Trackable Group guide.
• Trackable API docs cover create, lookup, activation, direct journey-stop logging, comment rules, 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
• Meta data deletion instructions URL: 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.
• If the issue is about maps or privacy mode, say whether the page was trying Latest and Greatest or No 3rd Parties, and whether you expected Google Maps, OpenStreetMap, or hosted maps only.
• If the issue is about restore or transfer, include whether the source file was account JSON, the portable ZIP with or without images, or a team JSON export, plus whether the target account already had matching categories or notes.
• 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.