Use this page when you need direct help, want to report a page, image, or external link, or need the official Geotrackable contact details.
Signed-in support requests keep the conversation threaded inside Geotrackable. Email and phone are still available when you need a direct contact point or cannot sign in yet.
Use signed-in support requests for account help, content review, workflow bugs, privacy questions, and follow-up conversations that need replies from support inside the product.
This is the best path when you want to track the status of a report or keep all of the replies in one place.
The flag button on public pages and image galleries opens a prefilled support path for page issues, inappropriate content, feature requests, and misleading or unsafe links.
If you are not signed in, this support page still gives you the official email and phone contact points so you are not dropped straight into a login wall without context.
Include the exact page URL or path, any related code or image id, what you expected to happen, and whether the issue involved a public page, private workflow, image, or external link.
Do not send passwords, one-time secret reveal screenshots, or private QR values unless support explicitly asks for them.
Email: michael.kappel@Geotrackable.com
Phone: (630)362-7576
Mailing address: 1331 S. 51st Ave Cicero, IL 60804
If an external website looks misleading, unsafe, broken, or no longer appropriate, use this support page or a public-page flag to send the link for review.
If an uploaded image exposes a secret code, child-identifying detail, private address, or other content that should not stay public, report the image from the page where it appears or contact support directly.
Use documentation pages when you are trying to understand how a workflow is supposed to behave. Use support requests when you need human follow-up, account help, or content review. Use the public report flag when the issue is tied to one specific page, image, or shared item.
That keeps feature questions, privacy concerns, content reports, and workflow bugs from getting mixed together in a single vague message.
