Privacy Policy

What this page covers

Geoblip is a GPS geofence alert service. This page explains what data the marketing site and the product collect, who processes it on our behalf, and why. It applies to geoblip.com and the Geoblip app.

Site analytics

This site uses Umami, a self-hosted analytics tool we operate ourselves at umami.totumalabs.com. It does not use cookies and does not track visitors across other websites. To tell repeat visits apart without cookies, it hashes your IP address and browser user-agent together with a salt that rotates every day; the raw IP address and user-agent are not stored, and the daily hash cannot be linked back to you or to your visits on other days.

We use this data in aggregate only — page views, referrers, and which programmatic pages perform well — never to build a profile of an individual visitor. Our legal basis for this processing is legitimate interest in understanding and improving the site (GDPR Art. 6(1)(f)).

Signed-in product use

Once you are signed in to the Geoblip app, product usage is associated with an opaque internal account identifier rather than your name or email address, so that we can see how the product is used in aggregate and diagnose problems without building a marketing profile tied to your identity.

Who else processes data on our behalf

A small number of providers process data as part of running Geoblip. We list only the ones we actually use:

• Stripe — processes payments and subscriptions for paid plans. Stripe receives what it needs to process a payment; we do not see or store full card numbers.
• Google Maps — powers the map and zone-drawing tools inside the app. Loading the map means your browser talks to Google directly for map tiles.
• Amazon Web Services (AWS SES) — sends transactional and alert emails on our behalf (e.g. geofence entry and exit notifications).
• Amazon Web Services (AWS S3) — stores encrypted, continuously-replicated backups of the product database, so location and account data can be restored if a server is lost.

We run Geoblip's application servers ourselves. We are not naming a specific hosting brand or physical region for those servers on this page because we could not verify one with confidence at the time of writing — if you need that detail for your own compliance purposes, contact us and we will confirm it directly.

How long we keep things

Daily analytics identifiers are never stored in the first place — see above. Database backups are retained for a rolling seven days of change history, with a fresh snapshot taken every 24 hours; older backup history is deleted automatically as new backups are made.

Questions

For privacy questions, or to ask about hosting location for compliance purposes, contact support@geoblip.com.

For how the product itself works day to day, see how it works, or browse the glossary and supported devices pages.