Privacy for trackables, locations, uploaded images, support requests, and public pages.

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.

Public route pages can keep the saved stop even when a fuller location note later moves, goes private, or disappears. Geotrackable can then add whichever location notes are currently visible at that coordinate for the viewer who opened the page.

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.

Shared data, maps, and browser requests

Depending on the current privacy rule and the signed-in account preference, a Geotrackable page can try OpenStreetMap first, or stay on Geotrackable-hosted map tiles only. When a third-party map provider is actually used, that provider can see the request details needed to answer, such as IP address, browser headers, request time, and which map area was requested.

OpenStreetMap first is a preference, not a guarantee. If OpenStreetMap is unavailable, Geotrackable can fall back to hosted maps only. If the signed-in user chose No 3rd Parties, or this visit still needs GDPR-style consent, or the request came from a private-network or otherwise unresolved IP, Geotrackable forces hosted maps only and keeps the browser on Geotrackable-owned map URLs.

That visit-level prompt is mainly for signed-out or otherwise unresolved visits. Once you are signed in, the saved account settings win for that page load and the prompt is no longer the long-term source of truth for your trips.

That outside provider does not automatically get your whole private location note or team history just because a map is visible. It mainly receives the request needed to draw the map unless Geotrackable intentionally sends another lookup for a separate feature. For the deeper plain-language explanation of maps, Google Identity, Facebook Login , Google Analytics, email and text delivery providers, and hosting logs, read About Shared Data and About GDPR.

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.

Logs, deletion, and legal requests

Deleting live content does not always erase every short-term server log, database log, or backup copy at the same instant. Some operational records stay around until their normal rotation or retention window ends because real services need disaster recovery, security review, and audit trails.

Geotrackable does not automatically hand user data to outside requesters. If a valid warrant, subpoena, court order, judgment, or similar lawful demand requires disclosure, the request is reviewed and the response is limited to the records the law requires and the system actually stores. A legal hold can also delay normal deletion while the review is active.

Email and text providers

Transactional email is delivered through Mailgun so confirmations, resets, and support follow-up mail can arrive.

Text delivery is also planned through Twilio Messaging when that feature is enabled. At that point, phone numbers, message content, and delivery-status events will need to pass through Twilio to deliver the text.

Geotrackable currently uses Google Analytics for sanitized page-view data plus limited workflow events such as sign-in, account creation, provider linking, trackable creation, trackable-group creation, secret-code entry, activation, quick-stop saves, and full location logging instead of location-note text, secret codes, exact coordinates, names, or email addresses, but only when the site is configured for analytics and the current visit still allows browser-side analytics.

If the effective experience mode is No 3rd Parties, or the visit is in a consent-required region without granted consent, Geotrackable keeps browser analytics essential-only and does not load the Google Analytics browser tag for that request.

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.

Exports can include Quick Stops, route snapshots from full location notes, and in-scope trackable comments without promising that today's visible location notes are the same as the historical stop.

Portable shared-account exports are also the recovery and cross-site-transfer handoff package. The matching additive import flow keeps the target account settings, adds missing records, skips identical matches, and reports conflicting existing data instead of overwriting it automatically.

About Import and Export collects the full restore, duplicate-skip, team JSON, and image re-screening rules in one place.

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.