← MetricMind

Privacy policy

Last updated 22 October 2026

MetricMind is a web analytics service with a built-in AI analyst. This policy covers two groups: customers (people with a MetricMind account) and visitors of websites that use MetricMind. For visitor data, the website owner decides what is collected and is the controller; MetricMind processes it on their behalf.

What we collect about website visitors

  • No cookies. The tracker stores a random visitor ID in the browser's local storage and a random session ID in session storage (it expires after 30 minutes of inactivity). Clearing site data or calling mm.optOut() deletes them and stops measurement.
  • Page and event data: page path and title, referrer (without its query string), UTM tags, custom events and the properties the website chooses to send, Web Vitals and JavaScript error messages.
  • Device data derived from the request: device type, browser, operating system, language, timezone, screen size and country. The raw user agent is parsed and discarded.
  • IP addresses are never stored. The IP is used once to look up the country (with the offline IP Geolocation by DB-IP database, licensed CC BY 4.0) and then discarded. Requests to MetricMind's collection endpoints are not written to access logs.
  • If a website calls mm.identify(), it links the visitor to its own user ID and may send traits such as an email address. That is the website's choice and responsibility; MetricMind stores those traits only for that website.
  • If a website connects Stripe or Paddle, MetricMind receives payment amounts, currency and customer IDs, plus the visitor and session IDs the website attached to the checkout.
  • Short links record a click with country, device, browser, operating system and referrer domain; no IP address or user agent is kept.

What we collect about customers

  • Account details: name, email address, password (stored only as an argon2id hash) or the identity returned by GitHub or Google sign-in (account ID and verified email).
  • Organization data: websites, members and roles, settings, API keys (stored only as hashes), payment-provider webhook secrets, and the business context you give the analyst.
  • Sign-in sessions (a random token in an httpOnly cookie, stored only as a hash) and failed sign-in attempts, kept for rate limiting.
  • Waitlist sign-ups: the email address you enter.

The AI analyst

When you ask the analyst a question, or when it investigates a change on a schedule, it runs queries on your website's data and sends the results to an AI model provider to write its answer. Results are mostly aggregated metrics; some queries return individual events with their random IDs and custom-event properties. Traits sent with mm.identify() (such as email addresses) are never sent to the AI model. We don't use your data to train models, and our AI provider processes it only to produce the response.

Where data is stored and who processes it

  • Hosting: Hetzner Online (Germany, European Union).
  • AI model provider: for analyst answers, investigations and site research, as described above.
  • Email: Resend, for account emails (invitations, password resets, sign-in links) and the alerts and briefings you turn on.
  • Sign-in providers: GitHub and Google, only if you choose to sign in with them.
  • Payment providers: Stripe or Paddle, only if a website connects them.

We don't sell data and don't share it with advertisers.

Retention

  • Analytics events are kept while the website's account is active; customers can export them at any time (Settings → Data export).
  • Uptime checks are kept for 400 days, short-link clicks for 25 months, MCP tool calls for 13 months.
  • When a customer deletes a website or their account, its data is deleted within 30 days, including from backups.

Your rights

You can access, correct, export or delete your account data, and object to or restrict its processing. Visitors of a website that uses MetricMind should contact that website first, since it controls the data; we will help it respond. For anything else, or to complain, write to contact@clodevo.com. You can also contact your data protection authority.

Security

Traffic is encrypted with HTTPS. Passwords, sessions, API keys and one-time links are stored only as hashes. Every customer query is restricted to the websites of their own organization at the database level.

Changes

If we change this policy in a way that matters, we'll tell customers by email before it takes effect.