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.
That request lets the map company see normal website request details such as your IP address, browser type, time of request, and which map area you asked to view. That is how browsers work, not a special Geotrackable trick.
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, or privacy situation.
SupportWhen Geotrackable shows a live 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 map to show.
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, 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.
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.
This software can support an optional Google Analytics tag, but no analytics browser requests are sent unless a measurement ID is configured for the host. If it is turned on later, the browser would load analytics code from Google and send page-view and browser metadata there.
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.
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.
