Privacy Policy
Last updated 17 November 2026
Dataa is website analytics built to collect as little as possible. This page explains what Dataa collects about the people who use it, and about the visitors to their websites. Dataa is run by [Legal name], based in [Country] (“we”).
Two kinds of people
Customers are people with a Dataa account who add Dataa to their websites. For their account data, we decide how it’s used. Visitors are people browsing a customer’s website. For visitor data, we act on the customer’s behalf: the customer decides to use Dataa on their site and is responsible for telling their visitors about it.
Visitors to websites that use Dataa
When a page with the Dataa script loads, it sends us:
- The page address, the address of the site that linked to it, and campaign tags in the link (such as utm_source).
- Browser, operating system and device type, worked out from the browser’s user agent and screen width.
- The country, region and city, looked up from the IP address by our hosting provider. The city is kept with its approximate position (to about 10 km), to show visitors on a map.
- The number of the network the visitor’s connection belongs to (for example, a mobile carrier or a hosting provider), to tell likely bots from people.
- How far down the page the visitor scrolled, how long they stayed, and named actions such as a form sent, a file downloaded, a link to another site, or a purchase.
No cookies. Dataa sets no cookies. No IP addresses are kept: the IP address is used for a moment to find the country and city and, together with the user agent, to make a code that changes every day, so a visit can be counted once. The address itself is never written down.
What’s stored on the visitor’s device. To recognise returning visitors, the script keeps a random ID in the browser’s local storage (sharx_v). It isn’t linked to a name or email. Customers can turn this off with one script setting, and then it isn’t stored. A visit ID (sharx_s) lives in session storage, which the browser clears when the tab closes. The script may also keep a note of purchases already counted (sharx_paid) so a reloaded page isn’t counted twice, and, if a customer’s site chooses to, its own opaque user ID (sharx_u). Anyone can stop being counted on a site by clearing these.
Faces and names. The dashboard shows each visitor with a cartoon face and a made-up first name, chosen from their random ID. They don’t describe the real person.
Pages loaded by bots, such as search engine crawlers, are recorded separately, with only the bot’s name, the page and the country, and kept for 1 year.
Kept for 3 years, then deleted automatically. A customer can ask us to delete a website’s data sooner.
Customers
- Account: your email address and password (stored only as a secure hash), or your Google account if you sign in with Google.
- Your websites and settings: the domains you add, conversions you set up, and API keys you create (stored only as a hash).
- Billing: your plan and subscription status. Payments are handled by Polar, which acts as the seller and processes your card. We never see or store card details.
- Errors: when something goes wrong in the app, a report of the error, including the page and browser, is sent to Sentry so we can fix it.
We use this to run your account, bill you, keep the service working and secure, and answer you. We don’t sell it and don’t use it for advertising.
We keep account data while your account exists, and delete it when you ask us to close it, except what we must keep for tax and accounting.
Who processes data for us
- Vercel: hosts the website and the app (United States).
- Supabase: accounts, websites and settings.
- Tinybird: visit data (Amazon Web Services, United States).
- Polar: payments and invoices.
- Resend: sends our emails to you (confirming your address, resetting a password, your Free Starter Plan). It receives your email address and nothing about your visitors.
- Sentry: error reports.
- Google: only if you choose to sign in with Google.
Some of these providers process data in the United States. Where the law requires it, they do so under safeguards such as standard contractual clauses.
Your rights
Depending on where you live, you can ask to see, correct, export or delete your data, or object to how it’s used. Email us and we’ll answer within 30 days. Visitors: as we only hold a random ID and no name, the quickest route is usually to ask the website you visited, who can ask us to delete its data. You can also complain to your local data protection authority.
Security
Data is sent over encrypted connections, access to accounts and data is limited to what each part of the service needs, and secrets are kept on the server. To report a security problem, email us.
Changes
If we change this policy, we’ll update the date above, and email customers about important changes.
Questions? Email [support email].