Privacy Policy
In short. Gaugemint is a privacy-friendly web analytics service. Our tracking script sets no cookies and stores nothing in your visitors' browsers. On websites we do not keep visitors' IP addresses and we do not follow anyone from one day to the next or from one website to another. The one exception is an optional mode for apps that a site owner builds and runs themselves, described in section 2a, where the app's own random install id is kept (as a keyed hash) so the owner can count active installs and retention. We never sell data or use it for advertising. For people with an account, we keep what we need to run the account: an email address, a hashed password, your site settings and your billing status.
1. Who we are
Gaugemint is operated by KreativeKoalaSolutions LLC, 5900 Balcones Drive, Ste 100, Austin, TX 78731, USA ("we", "us"). You can reach us at hello@guagemint.com.
This policy covers two groups of people:
- Account holders: people who sign up to Gaugemint to measure their own websites ("site owners"). For this data we decide how it is used.
- Visitors to a website that uses Gaugemint. The site owner decides to measure their site and what to send us, and we process the data on their behalf, following the limits described below.
2. Visitors to a website that uses Gaugemint
When a page with our script is viewed, or the site owner sends us an event, we receive and keep these things:
- the page address, without the query string (the part after "?") and without the fragment (the part after "#");
- the address of the previous page (the referrer), also without its query string;
- campaign tags in the address (utm_source, utm_medium, utm_campaign, utm_content, utm_term), which are read first and kept as separate values;
- the name of the event, and any extra properties or revenue amount the site owner chooses to send;
- the visitor's approximate location (country, region, city), worked out from the IP address with a database that runs on our own servers, so the address is not sent to any other service;
- browser, operating system and device type, read from the browser's user-agent string;
- the time of the visit.
We also compute a visitor identifier: a one-way hash of the IP address, the browser's user-agent string, the website and a secret random value that changes every day. The daily secret values are deleted after about two days. That means we cannot turn the identifier back into an IP address, we cannot recognise the same person on a different day, and, because the website is part of the hash, we cannot recognise the same person across different websites.
What we do not keep: IP addresses, the full user-agent string, query strings, fragments, names or email addresses (unless a site owner sends them as custom properties, which our Terms forbid). Our script does not set cookies and does not save anything in the visitor's browser (it only reads an optional opt-out switch and the browser's Do Not Track and Global Privacy Control signals), so no cookie banner is needed for it. Our script sends nothing for a visitor whose browser sends Do Not Track or Global Privacy Control, unless the site owner has turned that off for their site.
The IP address and user-agent string are used in memory, at the moment the request arrives, to compute the identifier and the location, and are then discarded. The limits that stop abuse of sign-up, log-in, password reset and share links keep the caller's IP address in memory (not in our database) for up to an hour. Routine operation of our hosting infrastructure can include short-lived technical logs that contain IP addresses.
2a. Apps measured in product mode (optional, first-party apps)
A site owner can switch one of their sites to product mode to measure an Android or React Native app that they build and run themselves. This is off by default and is not used for websites. In this mode the section 2 statements about identifiers change as follows.
- Install id. The app creates a random install id the first time it runs and keeps it in its own private storage on the device. It is not a hardware, advertising or account identifier. We never store the id itself: we store only a keyed one-way hash of it that includes the website name, so the same install on two different sites gives unrelated values and we cannot compare installs across sites.
- What we keep per event: that hash, the event name, any properties the app owner chooses to send, the app version, build, platform, operating system version, a random id for the app session if the app sends one, the time, and the approximate location (country, region, city) worked out from the IP address.
- What we do not keep or use: the IP address (used in memory only to work out the location, then discarded) and the user-agent string (not used to tell installs apart and not stored). The app owner must not send typed text, names, email addresses or other personal data.
- Daily counts. To show active installs and retention without keeping every event, we keep one small row per install per day (the hash, the day, how many events, platform, app and operating system version and country). These rows are kept for the period the site owner sets, 400 days by default. Individual events are kept as in section 7.
- Because the install id lasts until the user resets or removes it, the app owner can recognise the same install on different days. That is the purpose of the mode. A person who does not want this can use the opt-out the app should offer: it stops sending and deletes the id on the device.
- Erase. The app can send an erase request for its own install id, which deletes that install's events and daily rows from our systems. Copies in backups remain until the backups expire (section 7).
The app owner decides whether to enable the mode, tells their users that the app uses it, and is responsible for offering the opt-out and erase options in their app.
3. Account holders
If you create an account we keep:
- your email address and, if you confirm it, the fact that you did;
- your password, only as a salted one-way hash (we cannot read it);
- your sites (domain name, time zone) and settings such as goals, funnels, share links and email-report preferences;
- API keys, session identifiers and one-time links (verification, password reset), only as one-way hashes;
- usage counts (how many events your sites sent this month) so we can apply the limits of your plan;
- your plan and subscription status, and, if you signed up with one, the invite code you used. Payment card details are handled by our payment processor and never reach our servers.
We send you emails to run the service: confirming your address, resetting your password, notices about your subscription, and the summary reports you switch on. Reports are off until you turn them on, and every report contains an unsubscribe link.
When you log in we set one cookie, sid. It keeps you logged in for up to 30 days, is only sent to our service over HTTPS (it is marked Secure, HttpOnly and SameSite), and is used for nothing else. We do not use advertising or analytics cookies, and we do not use third-party trackers on our own pages.
4. How we use data
- to provide, secure and support the service, including preventing abuse and spam;
- to apply plan limits and to bill for paid plans;
- to contact you about your account;
- to meet legal and tax obligations.
We do not sell personal data, we do not share it for advertising, and we do not build profiles of individual visitors.
5. Who else handles data
We use a small number of service providers to run Gaugemint. They process data only to provide their service to us:
- a hosting and infrastructure provider, which runs our servers and stores our database in the United States;
- an email delivery provider, which sends the emails described above;
- a payment processor, which collects payments and keeps card details;
- an object-storage provider, which holds encrypted off-site copies of our database;
- a domain-name (DNS) provider. It only answers requests for our domain's address; visitor traffic and tracking data do not pass through it.
We may also disclose information if the law requires it or to protect our users and our service.
6. Where data is stored
Our servers are in the United States. If you or your visitors are in another country, the data is transferred to and stored in the United States.
7. How long we keep data
- Visitor events: deleted automatically after 90 days. Deleting a site in your account deletes its events straight away.
- Backups: we keep daily database backups for up to 7 days on our server and encrypted off-site copies of the database for up to 35 days, and our hosting provider keeps disk snapshots for up to 5 days. When we upgrade the database structure we also keep a restore point of the previous database on our server until we remove it. Data you delete, including a deleted account, can therefore remain in a backup for up to 35 days, and in such a restore point until it is removed.
- Account data: kept while your account exists; an account whose email address is never confirmed and that has recorded no events is deleted after 14 days. You can delete your account yourself under Account, Delete account: your sites, their events, share links, API keys and sign-in data are deleted immediately and any subscription is cancelled. You can also email us and we will delete it within 30 days. We keep no invoices or card details in our own database; the records the law requires us to keep for tax and accounting stay with our payment processor.
- Daily visitor secrets: deleted after about two days from our live database. They are part of the backups described above, so a copy can remain in a backup for up to 35 days.
- Apps in product mode (section 2a): the daily per-install rows are kept for the period the site owner sets (400 days by default); an erase request from the app deletes an install's rows and events immediately.
8. Security
All connections use HTTPS. Passwords, API keys and one-time links are stored only as hashes, and share links are stored encrypted. We limit sign-up attempts and other sensitive requests. Sign-up is open to anyone, with email confirmation. No system is perfectly secure, but we work to protect the data we hold. Please tell us at hello@guagemint.com if you find a security problem.
9. Your choices and rights
Account holders can delete their account themselves under Account, and can ask us to access, correct, export or delete their data by emailing us. Depending on where you live, you may have further rights, such as objecting to processing, and we will honour them where they apply.
Visitors to websites: because we keep no IP address and no identifier that lasts beyond a day, we generally cannot look up the data of one particular person. Users of an app in product mode (section 2a) can ask the app owner to use the app's erase option, which deletes their install's data. If you have a question about data collected on a website, please start with that website's owner; we will help them with any request they send us.
We answer requests within 30 days.
10. For site owners
You are responsible for telling your own visitors that you use Gaugemint, for any notice or consent the law requires where you operate, and for not sending personal information (such as email addresses, names or ID numbers) in event names, properties or page addresses. If you enable product mode for your app, you are also responsible for telling your users, for offering an opt-out and an erase option in the app, and for never sending typed text or personal data.
11. Children
Gaugemint is meant for businesses and is not directed to children under 16. We do not knowingly create accounts for them.
12. Changes to this policy
If we change this policy we will update the date above and, for material changes, tell account holders by email or in the dashboard before the change takes effect.
13. Contact
KreativeKoalaSolutions LLC, 5900 Balcones Drive, Ste 100, Austin, TX 78731, USA
hello@guagemint.com