What Tallyo collects, and what it never does
The whole point of the product is that this page is short.
Stored, per pageview
- The page path, and the hostname it was on
- The referrer's hostname, with any query string and fragment removed
- Campaign parameters from the URL (
utm_*and the like), by name, and nothing else from the query string - Country and first-level region, looked up from the address on our server and then discarded
- Browser family, operating system family, and device type (desktop, mobile, tablet)
- How long the page was on screen with someone at it, in seconds
- A visitor identifier that is valid for one day
Never stored
- IP addresses
- User-agent strings
- Cookies, local storage, or anything else in the visitor's browser
- Screen size, language, timezone, installed fonts, or any other fingerprint
- Full URLs with their query strings
- Any identifier that follows a person across days or across sites
How visitors are counted without any of that
Each day the server generates a secret it never writes down. A visitor's identifier is a hash of that secret, the first part of their network address, their browser family and the site they are on. The same person on the same site is the same identifier for the day, which is what makes "visitors" and "sessions" countable; tomorrow the secret is gone and so is any way to connect the two days. Nothing about the hash can be reversed into an address, and a site cannot recognise a visitor it saw last week.
Consent
Because nothing is stored on the visitor's device and no personal data is retained, Tallyo does not require a cookie banner or a consent prompt under the ePrivacy Directive or the GDPR for the analytics themselves. Whether the rest of your site needs one is a question about the rest of your site. We are not lawyers, and this is not legal advice.
Where the data lives, and who can see it
On our servers in the United States. Your organization's members see your organization's sites and nothing else; a member can be limited to particular sites. You can export every event as CSV at any time, and delete a site — and everything ever collected for it — from the dashboard.
The code
The server that does all of this is published, so the claims above can be checked rather than believed. It is licensed under the Functional Source License; every version becomes Apache 2.0 two years after release.