Privacy for trackables, locations, uploaded images, support requests, and public pages.
This page explains what Geotrackable stores, what can become public, how links and images are screened, how location data is handled, and how support and reporting fit into that flow.
Last updated: Wednesday, March 25, 2026
What we collect
- Account details such as your username, email address, linked-provider sign-in records, and security settings.
- Trackable, trackable-group, team, category, and mapped-location content that you create or help manage.
- Journey history, saved coordinates, public-or-private visibility choices, and related page metadata needed to show the route and enforce access rules.
- Uploaded image records, processed image files, and extracted image-location coordinates when an uploaded image contains usable GPS metadata.
- Support requests, replies, public-page reports, and system-error reports that you submit.
Why we collect it
- To run the website, protect accounts, and keep trackable, team, and location workflows functioning.
- To show the public pages and private workflows you intentionally create, including route maps, team pages, and profile pages.
- To screen and review uploaded content, outside links, abuse reports, bug reports, and support conversations.
- To troubleshoot errors, understand feature failures, and respond when someone reports unsafe, misleading, or inappropriate content.
Accounts and sign-in
A Geotrackable account is part of the shared LocationNotes account system. Depending on the sign-in path you use, your account can include local credentials and linked external provider records.
Your email address and sign-in settings stay in the signed-in account workflow. They are not copied onto your public profile page just because your profile or trackables are public.
Trackables, teams, locations, and public pages
When you create trackables, trackable groups, locations, teams, or profile content, Geotrackable stores the titles, descriptions, visibility settings, categories, ownership information, and related page data needed to render those features.
If you choose public visibility, that information can become visible to other visitors and may be indexed by search engines. Private pages are intended to stay limited to the people and workflows allowed by the product's access rules.
Location data and maps
Geotrackable stores location coordinates when you save mapped locations, log trackable journey stops, or choose to use image-location data from an uploaded photo. Those coordinates are part of the content record and can remain with the route history until the related content is removed.
When a page offers a map picker, the site first tries browser geolocation if you ask for current-location help. If browser geolocation is unavailable, the site can try an approximate map center using your network address during that live request.
That approximate network-based lookup is for map assistance, not for adding a precise saved stop by itself. The saved location is the coordinate you actually submit with the form.
Images and extracted image-location data
Uploaded images are screened before they are stored. After approval, Geotrackable processes them into managed JPEG variants used for thumbnails and page displays.
If the original image contains usable GPS metadata, Geotrackable can extract that latitude and longitude and store it with the image record. Some workflows can also use that extracted coordinate to help place related content on the map.
Image visibility follows the visibility of the page or parent item where the image is attached. Public team pages and public trackable pages can show their visible images to the public.
External links
When you add an external link, Geotrackable verifies the address before saving it. That verification can normalize the URL, attempt to read the page title for a starting description, and reject malformed links, localhost-style destinations, private-network targets, or pages that trigger the current adult-content safety signals.
On public pages, a verified outside link can open through a Geotrackable-owned exit page first so visitors can confirm the destination before leaving the site. Support and reporting paths can be used if an outside link later looks unsafe, deceptive, or broken.
Diagnostics and IP handling
Geotrackable stores diagnostic records when errors are reported or when the site captures application failures. Those records can include request URLs, route values, filtered request headers, browser user-agent information, exception details, and any explanation the user chose to submit with a report.
Raw remote IP addresses are not stored in new Geotrackable application error-log records, and common forwarded-IP headers are filtered out of stored error-log headers.
Network addresses may still be used transiently during live requests when the site tries to estimate an approximate map position after browser geolocation is unavailable.
Support requests, reports, and moderation review
If you submit a support request or use a report button, Geotrackable stores the issue type, your explanation, the related page URL or reference when provided, the conversation replies, and the review status needed to work the request.
These records help the service investigate inappropriate content, suspicious links, broken pages, privacy concerns, and bug reports.
Children and adult-managed participation
People must be at least 16 years old to operate their own Geotrackable account. Younger children can still participate only through adult-managed workflows such as family, troop, classroom, or other supervised use.
Adults remain responsible for deciding what is posted publicly, what location detail is shared, whether images are appropriate, and whether outside links are suitable for the intended audience.
Retention and deletion
Geotrackable keeps the data needed to operate the content you create, the routes you log, the support requests you submit, and the legal or safety review records needed to manage the service.
Some content may continue to exist when it is part of a shared team workflow or another user's visible route history. Use the delete-data guidance and the support page if you need help understanding a specific deletion scenario.
Contact and related help
Use the official support page for privacy questions, content review, or reporting. Support
You can also email privacy or support questions to michael.kappel@Geotrackable.com.