Geotrackable.com
Maps, sign-in helpers, and normal website hosting all need some shared data to do their job. This page explains what that means in plain language for families, clubs, classrooms, and other Geotrackable users now that the site can switch between Latest and Greatest, No 3rd Parties, and hosted-map fallbacks.
When browser-side third parties are allowed, the map provider can still see normal website request details such as your IP address, browser type, time of request, and which map area you asked to view. When the stricter path wins, Geotrackable can stay on its own hosted map URLs instead.
Privacy explains the formal rules for maps, providers, logs, deletion, and legal requests without putting every technical detail on one long legal page.
Privacy PolicyTerms covers the responsibilities that come with using outside map, sign-in, and hosting services as part of the Geotrackable experience.
Terms of ServiceUse support or delete-data when the question is not just theory and you need help with a real account, route, export, deletion, restore, or privacy situation.
SupportSigned-in users can choose Latest and Greatest or No 3rd Parties, then decide whether Google Maps, OpenStreetMap, or hosted maps should load first when the stricter rule is not already forcing hosted maps only.
AccountUse the GDPR guide when you want the visit-level consent prompt explained in plain language, including the signed-out testing path and why saved account settings take over after login.
About GDPRUse the import/export guide when you need the restore and transfer rules, duplicate-safe additive import behavior, team JSON handoff, or image re-screening details.
About Import and ExportWhen Geotrackable shows a live third-party map, your browser has to fetch map code, tiles, or place results from a map provider such as Google Maps Platform or OpenStreetMap resources. Without that outside request, there is no live third-party map to show.
If the signed-in user chose Hosted maps only, chose No 3rd Parties, or the current visit still needs consent, Geotrackable can serve map tiles through its own /maps/tiles/{z}/{x}/{y}.png route. That keeps the browser on Geotrackable-owned URLs while the hosted map stack does the tile work behind the scenes.
The map provider can usually see the same kind of envelope information every website sees for a resource request: your IP address, browser headers, when the request happened, and which map area or place lookup was requested.
The map company does not automatically get your whole private location note, your team membership list, your current visible location-note read model, or every page detail just because a map is visible. They mainly get the request needed to draw the map itself unless Geotrackable intentionally sends another lookup for a separate feature.
Google Maps first and OpenStreetMap first are preferences, not guarantees. Geotrackable falls back to the other allowed provider when the preferred one fails, and it forces Hosted maps only when consent-required, private-network, or unresolved visits need the stricter path.
The bottom-of-screen privacy prompt is the visit-level version of that decision. Once someone signs in, the saved account settings take over and the prompt is no longer the durable rule for later pages on that account.
If you use Google Identity or Facebook Login sign-in, your browser is sent to that provider so it can handle the login. The provider can see that you are signing in to Geotrackable, and Geotrackable receives the provider identifier plus the basic profile data that provider returns for account creation or account linking, such as approved name or email details.
Geotrackable currently uses Google Analytics for sanitized website analytics only when the site is configured for analytics and the current visit still allows browser-side analytics. In those cases, the browser loads analytics code from Google and Geotrackable sends 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. Geotrackable is designed not to intentionally send location-note text, secret codes, exact coordinates, names, or email addresses to Google Analytics.
If the effective experience mode is No 3rd Parties, or the visit is in a consent-required region without granted consent, Geotrackable keeps analytics essential-only and does not load the Google Analytics browser tag for that request.
Normal websites keep operational logs too. Web servers, app logs, security records, and database logs can keep timestamps, request paths, status codes, and technical troubleshooting details so the service can stay online and abuse or bug reports can be reviewed.
Readable JSON is for review. The portable ZIP is the handoff package for restoring the same shared account later or moving route-friendly personal data between hosts. The export still keeps the full manifest even when the current additive import intentionally leaves some target-account settings alone.
That additive import checks matching records by content instead of exported IDs, adds missing records, skips identical matches, and reports conflicting existing data instead of overwriting it automatically.
Geotrackable currently uses Mailgun for transactional email. That means email addresses, delivery headers, the message content needed for delivery, and delivery-status events can pass through Mailgun so confirmations, resets, and support follow-up messages can arrive.
Geotrackable also has Twilio Messaging support ready for future text alerts. When that goes live, the phone number, message content, carrier-routing details, and delivery-status events will need to pass through Twilio so the text can be delivered and tracked.
Deleting live content does not always erase every short-term log or backup copy at that same instant. Some server logs, database transaction logs, and backup sets may stay around until their normal rotation or retention window ends. That is part of running a real service, not a promise to keep a second public copy of your data.
Geotrackable does not keep an automatic handoff pipe for law enforcement or private requesters. If a 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 has. That usually means the same stored account, content, support, and audit records a user could request through export tools, plus any logs or backups that have to be preserved for the review.
