Geotrackable.com
Support requests work best when they identify the page, the related code or image, and the type of problem without exposing private secrets that should never have been copied into a ticket.
When a request is specific, support can move faster and you do not have to resend the same page path, code, or explanation over and over.
michael.kappel@Geotrackable.com
(630)362-7576
Use the support page first for the official email, phone, address, and guidance on when to use a threaded support request instead of a public report flag.
SupportUse the image and external-link documentation when the question is about how shared media or websites are verified, displayed, or reported.
About External LinksUse the legal pages when the question is about data handling, moderation expectations, export or deletion behavior, or the responsibilities that come with public content.
Privacy PolicyThe delete-data page explains exports, portable restore packages, permanent account deletion, and the public policy links used for account-help and provider setup.
Delete dataUse signed-in support requests when you need back-and-forth replies, status updates, or review history that stays attached to one issue inside Geotrackable.
The report flag on public pages and image galleries can send you into support with the page path, related reference, and suggested subject already filled in.
The owned support page is the best starting point when you are not signed in yet, need the official contact details, or want to decide between docs, legal pages, and support tickets.
If the problem is about a duplicate stop, the wrong page state, a group watch versus item watch question, or another workflow mismatch, support is still the right path because those issues often need exact page context.
If the page was in Latest and Greatest, No 3rd Parties, Google Maps first, OpenStreetMap first, or Hosted maps only, say so. That tells support whether the browser should have been allowed to call third-party maps or analytics at all.
If the issue came from importing or preparing an export, 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 records.
Passwords, one-time reveal screenshots, private QR values, and other secret access details should stay out of normal support messages unless support specifically asks for them.
Name the exact page or page section, whether the issue involved a public code, secret code, image, link, team, trackable group, quick stop, or full location note, plus the last step that worked before the issue started.
If the problem is about maps or privacy, say whether the page was in Latest and Greatest or No 3rd Parties, whether Google Maps first, OpenStreetMap first, or Hosted maps only was expected, and whether the consent banner had already been accepted.
If the problem 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 location notes.
If the question is really about monitoring, say whether you were following one item or a whole group. If it is about the route, say whether the confusing stop was a lightweight location report or a fuller location note saved at the same coordinate.
A saved route stop and a visible location note are not always the same thing, so clean page families make it easier to share, support, and explain the right page.
If the issue came from a public report flag, keep the prefilled page path and reference when you open the support request so support can inspect the exact content item faster.
