Last updated 2026-10-13.
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.
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. The one exception is the campaign attribution id described below, which links the campaign that first brought you here to a later sign-up and subscription. Our legal basis for this processing is legitimate interest in understanding and improving the site (GDPR Art. 6(1)(f)).
On your first visit this site generates a random id, not derived from
your IP address, device or identity, and keeps it in your browser's
local storage together with the campaign tags of the link that
brought you (such as utm_source), the referring site and
the page you landed on. It is not a cookie. When you follow a link to
the Geoblip app, the id and campaign tags are added to that link, and
when you start a checkout the id and the campaign's source, medium and
name are passed to Stripe as the checkout reference. The Geoblip app
keeps its own copy of the id it receives this way, and our analytics
record it with the sign-up and the subscription. We use them only to
learn which campaigns lead to sign-ups and subscriptions. You can
remove them by clearing each site's data (local storage) in your
browser settings; otherwise they stay there.
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.
A small number of providers process data as part of running Geoblip. We list only the ones we actually use:
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.
Daily analytics identifiers are never stored in the first place — see above. The campaign attribution id stays in your browser until you clear it, with Stripe on the checkout it was attached to, and in our self-hosted analytics with the sign-up and subscription events for as long as we keep that analytics data. 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.
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.