Metermark (“Metermark”, “we”, “us”) provides a service that measures how people and teams use AI coding tools, so organizations can see what their AI spend buys. This policy explains what we collect, why, and what we never keep. It applies to metermark.ai, the Metermark dashboard, the Metermark API and MCP server, and the Metermark agent that runs on a computer you control.
What we collect
Account information. When you sign in we receive your name, email address, and profile picture from the identity provider you choose (for example Google), plus an identifier for the organization you belong to. Sign-in is handled by Auth0 on our behalf at auth.metermark.ai.
Assessment requests. When you ask for an assessment we keep your email address and company name. We send a confirmation and at most two reminders, each with a one-click way to stop them. If you later sign up with that address, or a colleague at the same company domain does, we note the match so a person can follow up. Write to us to have a request deleted.
Usage metadata. The agent records, for each AI session it observes: who ran it, when, which tool and model were used, token counts (including how many thinking tokens each model response reported, never the thinking itself) and estimated cost, the kind of work inferred from the session, a small set of practice scores, counts of what the session produced (commits and pull requests, and how many documents, analyses, reviews, tickets, decisions and designs — never their names, paths or contents), when its prompts and tool calls happened as offsets from its start (never what they said), and the values of any labels your organization defines. This is the data the dashboard is built from.
Prompt samples in transit. To classify a session, a short sample of prompt text may be sent to our classification endpoint. It is processed in memory and discarded once the label is produced. We do not store prompts, responses, code, or transcripts.
Billing. Paid plans are billed by Stripe. We keep your Stripe customer and subscription identifiers; card details go to Stripe and never reach us.
Operational logs. Standard request logs (IP address, user agent, timestamps, request path) kept for security and debugging for a limited period.
What we never store
- The content of prompts, model responses, files, or source code.
- Screen recordings, keystrokes, or anything outside the AI tools the agent is configured to observe.
- Payment card numbers.
How we use it
To show you and your organization the dashboard, benchmarks, and recommendations; to run the API and MCP server you enable; to bill you; to keep the service secure; and to answer your support requests. We do not sell personal data and we do not use your data to train models.
Who can see what
Team-level views are the default. Person-level detail is limited to the owners and admins your organization designates, and every time one of them reads another person’s detail the read is recorded in an access log the organization can inspect. Cohort comparisons never name anyone below a minimum group size. Individual accounts contain only their owner’s data.
Where it lives and who helps us run it
Data is stored in the United States with the providers that run the service: Vercel (hosting), Neon (database), Auth0 (sign-in), Stripe (billing), Resend (email), PostHog (product analytics and error reporting for the website and dashboard), and the model provider used for classification, which receives prompt samples only in transit as described above. Each is bound by its own terms and security commitments.
Retention and deletion
Usage metadata is kept while your account or organization is active. An individual account can delete itself through the API at any time (DELETE /api/v1/me), which removes its data immediately; ask us to delete an organization and we remove its data within 30 days. In both cases we keep records we must keep for tax or legal reasons, and we remove the sign-in identity at our identity provider as part of the request. You can export your data through the API at any time (GET /api/v1/export).
Your choices
You can stop the agent at any time; nothing is collected while it is not running. You can sign out of every session, rotate or revoke API keys, and ask us to correct or delete your data. If you are in a region with statutory privacy rights, you may exercise them by emailing us.
Cookies and analytics
We use a session cookie to keep you signed in and a preference cookie for the dashboard theme.
We advertise on Google and LinkedIn and measure one thing there: whether an ad led to a new account. The website loads the Google tag and the LinkedIn Insight Tag, which set their conversion cookies, and when an account is created each is told a sign-up happened, identified by our internal account id, never your email or name. Our server also tells LinkedIn about the new account directly, through its Conversions API, with the same account id and a one-way hash of your email address (LinkedIn’s own matching key; the address itself is not sent) so that the sign-up counts once. We do not use them for remarketing or ad personalization. In the European Economic Area, the United Kingdom and Switzerland the Google tag runs without advertising cookies (Google estimates conversions instead) and the LinkedIn Insight Tag does not load at all; we tell those regions apart by your browser’s time zone. Google’s and LinkedIn’s use of this data is covered by their own privacy policies.
The website and the dashboard use PostHog, hosted in the United States, for product analytics and error reporting: which pages are viewed, what is clicked, which features are used, and the stack trace when something breaks. The website also counts installer and agent downloads (which build, the kind of client such as curl or a browser, and the country the request came from, never the IP address), and records sign-ups (with the sign-in method, such as Google or email and password), first syncs, and assessment requests against internal ids, never email addresses. Signed-out pages set no analytics cookie: PostHog keeps a visitor id in the tab’s session storage, which the browser discards when the tab closes, so the page you arrived on and a sign-up made from it count as one visit. Once you sign in, PostHog keeps an identifier in a cookie so we can see how the dashboard is used per account; it is tied to your internal account id and your organization’s plan, never to your email or name. We never send it prompts, session content, or the names of people in your organization. The agent on your machine sends nothing to PostHog or any other third party; its only network calls are to metermark.ai and the release store.
Changes
When this policy changes we update the date at the top and, for material changes, tell signed-in users in the dashboard.
Contact
Questions or requests: hi@metermark.ai.