Skip to content
metryo

Legal · Privacy

Privacy Policy

This policy explains what Metryo collects when you use our website and product, and what we do with it. The short version: as little as possible, never sold, deletable at any time.

01Who we are

Metryo provides privacy-first website analytics. When we say “we” in this document we mean the operator of metryo.io. When we say “you” we mean the account holder using Metryo to measure their website.

02Data we collect about you

Accounts are created by signing in with GitHub or Google, so we never handle a password. From that provider we receive your name, your email address and the URL of your profile picture, and we store those along with your plan. The picture is shown only to you, in your own dashboard, and is refreshed from the provider each time you sign in.

We keep operational records such as the websites you add, their settings, and monthly usage counters, because the product cannot work without them.

If you subscribe to a paid plan, we store the identifiers our payment provider gives us for your customer and membership records, the country your billing address is in, and a record of each payment, subscription change and refund request — including any reason you give us for cancelling. Card details never reach us: they are held by the payment provider, who is the merchant of record.

If you write to us through the contact form we store your name, email address, subject and message so we can answer and keep a record of the exchange.

We measure this website with Metryo itself, on the same terms described for your visitors below.

03Data we collect about your visitors

The tracking script collects: page path, referrer, UTM parameters, country and region, device type, browser and operating system with their major versions, device model where the browser reports one, screen size, the network operator that owns the visitor's address block, connection type and speed class, and the primary language from the request. Alongside those, each event carries a timestamp, a hashed visitor identifier, a session identifier and a traffic-quality verdict. It does not use cookies and does not follow visitors across other websites.

Two of those — the major Windows version and an Android device model — come from the browser's client-hints API, which is the only source for either, and neither is requested on a visitor's first pageview. The Data Privacy page describes every field, and what the script deliberately never reads, in full technical detail.

On paid plans the script also records clicks: elements you have marked in your own markup, links leading to another website, and links to downloadable files. A click is stored as an event name plus the properties you chose, and for links the destination domain, URL and visible link text. It never records keystrokes, form field values, mouse movement, or the contents of the page.

Visitor identity is approximated with a salted hash that rotates every month. Raw IP addresses and user agents are used in memory to compute this hash and traffic-quality signals, and are not stored with your analytics data.

04How long we keep data

Analytics events are kept for the retention period of your plan (30 days to 24 months). Expired events are cleared by a periodic sweep rather than at an exact deadline, so an event can briefly outlive its window before it is removed.

Deletion you ask for is immediate: you can shorten the retention window per site, delete a site's data, delete a site, or delete your whole account at any time from the dashboard, and each of those takes effect straight away.

Two exceptions to that. Deleting your account removes your profile, your websites and all of their analytics data at once, but records of payments, subscriptions and refunds are kept afterwards because tax and accounting law requires us to hold them; they are no longer linked to a profile once the account is gone. Messages you sent through the contact form are also kept, so that a support history does not disappear mid-conversation — ask us and we will delete them.

05Sub-processors

Each of these receives only what it needs to do its job, and nothing is shared for any other purpose: a cloud platform that hosts the application and serves the tracking script, a managed database host that stores your account and analytics data, an email provider that delivers our transactional mail, GitHub and Google for signing in, and — for paid plans only — our payment provider, which acts as merchant of record and receives your name, email address and billing details in order to take payment.

Geolocation and network classification run against databases held on our own infrastructure, so no visitor IP address is sent to a geolocation or IP-intelligence service. The hosting platform necessarily handles the connection itself, as any host does.

06Your rights

You can export any date range as a CSV of raw events straight from your dashboard, on every plan, and erase data with the built-in deletion tools. We do not sell personal data, we do not run advertising, and we only disclose data when legally required.

Questions? Email privacy@metryo.io — we answer privacy mail first.