Privacy Policy

Last updated: 9 September 2026

hitglance is a web analytics service built to count visitors without identifying them. This policy explains what we store about the visitors of websites that use hitglance, what we store about you as an account holder, how long it is kept, and how to delete it. It applies to hitglance.dev, the tracking script, the API and the hitglance mobile app.

1. Visitors of websites that use hitglance

If you are visiting a website that has the hitglance script installed, this section is about you. We never learn who you are.

What is collected

For each page you view, the script sends a small request to our servers. From it we record:

• The page path (for example /pricing). Query strings are not stored, except for the UTM tags below.
• The referrer (the site you came from), reduced to its hostname and classified into a source such as Search, Social or Email.
• UTM campaign parameters (utm_source, utm_medium, utm_campaign) if present in the URL.
• Country, region and city, derived from your IP address by our hosting provider at the edge. Precise location is never collected.
• Device type (desktop, mobile, tablet), browser family and operating system, derived from the browser's User-Agent string.
• How long the page stayed visible, in seconds, so that visit duration and bounce rate can be computed.
• Custom events that the website owner has chosen to send (for example signup) and, for websites that connect Stripe, the amount of a completed checkout.

How visitors are counted

To tell repeat views from new visitors within a day, we compute a visitor identifier as a cryptographic hash (SHA-256) of a server-side secret, the current date, the website's ID, your IP address and your User-Agent string. The identifier changes every day and differs for every website, so it cannot be used to follow you across days or across sites. The inputs to the hash are not stored, and the hash cannot be reversed.

What is never stored

• Cookies or any other identifier placed in your browser. hitglance sets no cookies and reads none, so no consent banner is required.
• Your raw IP address. It is used in memory to derive the daily hash and the country, and for rate limiting, and is then discarded.
• Browser fingerprints, persistent device identifiers, or cross-site profiles.
• Personal data such as your name or email address. We ask website owners not to put personal data into page URLs or event names.

Automated traffic

Requests recognised as bots, crawlers, AI scrapers, link-preview fetchers, headless browsers or traffic from datacenter networks are not recorded as visits. We only keep a per-website daily count of how many such requests were dropped and why.

Opting out

Setting localStorage.setItem('hitglance_ignore', '1') in your browser on a given site stops the script from sending anything from that browser. Because we store no identifier for you, there is nothing to delete or export on a per-visitor basis; the data cannot be tied back to you.

2. Account holders

If you sign up for hitglance to track your own websites, this section is about you.

What we store

Cookies on hitglance.dev

The dashboard uses one strictly necessary session cookie to keep you signed in, and a short-lived cookie during Google sign-in to protect against cross-site request forgery. There are no advertising, marketing or third-party cookies. The public website itself is measured with hitglance, cookielessly.

Email

We send email only for password resets and, if you opt in under Settings, a weekly report every Monday. You can turn the report off at any time in Settings. We do not send marketing email.

Google sign-in

If you choose to sign in with Google, we receive your Google account identifier and email address. We use them only to create or link your hitglance account. We do not access any other Google data.

3. The mobile app

The hitglance app for iOS and Android is a read-only companion to the web dashboard. It signs in with an API token that you create in Settings and stores that token in the device's secure storage (Keychain on iOS, Keystore on Android). If you enable the app lock, Face ID, Touch ID or your passcode is checked by the operating system; biometric data never leaves your device and is never sent to us. The home screen widget caches your latest headline numbers on the device. The app contains no advertising, no analytics SDKs and no third-party trackers. The demo mode works entirely offline with sample data.

4. Retention and deletion

• Analytics data is kept for as long as the website remains in your account so that you can see long-term trends.
• Deleting a website deletes all of its analytics data.
• Deleting your account (Settings → Delete account, or DELETE /api/auth/account) removes your account, your websites and all of their analytics data immediately and permanently.
• Sessions expire after 30 days of inactivity. Password reset links expire after use or after one hour.
• Dropped bot-traffic counts and rate-limit counters contain no personal data.

5. Who we share data with

We do not sell data, do not share it with advertisers, and do not use it for anything except providing the service. The only parties that process data on our behalf are:

• Cloudflare — hosts the service, the database and the tracking script, derives country from IP at the edge, and delivers our email.
• Google — only if you choose to sign in with Google.
• Stripe — only if you connect Stripe; Stripe sends us completed-checkout events and we send nothing to Stripe.

If you create a public share link for a website, anyone with the link can view that website's analytics. You can revoke the link at any time.

6. Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, or to object to its processing. Account holders can view and delete everything themselves from the dashboard, or export it through the API. For anything else, or to make a request as a website visitor, email us and we will respond within 30 days.

7. Security

All traffic is encrypted in transit with HTTPS. Passwords, sessions and API tokens are stored only as hashes. The hashing secret used for visitor identifiers is kept outside the database. The tracking script and the service are open to inspection; if you find a security issue, please report it to the address below.

8. Children

hitglance accounts are not intended for children under 16. We do not knowingly collect personal data from children; if you believe a child has created an account, contact us and we will delete it.

9. Changes to this policy

If we make material changes we will update the date at the top of this page and, for changes that affect account holders, notify you by email before they take effect.

10. Contact

Questions and requests: privacy@hitglance.dev.