Privacy & compliance
Privacy and data
usage.io is built for privacy-friendly analytics: no cookies on visitors’ browsers, no advertising trackers, and reporting designed around aggregates in your dashboard.
This page summarizes practices described in our Privacy Policy and Disclaimer. It does not replace legal advice for your organization.
Design principles
- No cookies — the tracker does not set cookies or use
localStorageto identify visitors. - No fingerprinting profile — we do not build cross-site advertising profiles.
- Pseudonymization — network identifiers are not stored in raw form; see IP handling below.
- Your controls — path and IP exclusions, per-site data reset, and site deletion in the app.
Our marketing site and pricing comparison also describe cookie-free collection, optional Do Not Track handling, path and IP exclusions, and pseudonymized IPs with daily salt rotation.
What the tracker sends
On each page view the script sends a JSON payload to POST /ping. When the visit ends (tab close, navigation away, or SPA route change), it sends POST /exit with the same core fields plus visible seconds on the page.
| Field | Role |
|---|---|
| Page URL | Match your registered site and record path |
| Visit ID | Random identifier for that visit on the client (not stored in cookies) |
| User-Agent | Browser, device, and device type breakdowns |
| Language | Aggregate reporting |
| Screen and viewport size | Device insight aggregates |
cookieEnabled | Whether the browser reports cookies enabled (we still do not set cookies) |
| Timezone (IANA) | Used to infer country for geography reports |
We do not use the tracker to read form fields or page content.
More technical detail: Tracker reference.
IP addresses
We do not store raw IP addresses. When a page view is received, the address is replaced with a pseudonymized value using a cryptographic salt. Our privacy materials describe daily rotation of that salt so the same address cannot be linked across days for tracking purposes.
Unique visitor counts in the dashboard use pseudonymized values within each reporting bucket (day or hour, depending on chart mode).
Do Not Track
Unless you enable Collect Do Not Track traffic for a site, the script does not execute for visitors who have Do Not Track turned on in the browser. No ping is sent.
When collection is enabled, the snippet includes data-collect-dnt="true". Configure this in site settings only if your privacy disclosures cover it.
Aggregation and retention
Incoming events are processed into the charts and tables you see in the dashboard—page view totals, paths, browsers, devices, countries, and time on site.
Plan data retention (how long history is available) is defined on pricing:
- Starter — 1 year
- Growth — 3 years
See Plans and trials.
You can remove analytics for a site immediately with Reset data or remove the site entirely with Delete site in settings.
GDPR, cookies, and consent
Many sites run usage.io without a cookie banner for analytics alone because the script does not use cookies. You remain responsible for disclosures in your own privacy policy and for any other tools on your site that may require consent.
For GDPR-related questions, review our Privacy Policy and consult qualified counsel.
Account data
Account closure and deletion of personal information associated with your login are described in the Privacy Policy. For help, contact us.