Privacy Policy

Effective 2026-11-04

1. Who we are

This policy describes how Workmain Inc. (Workmain, we, us) handles personal information on the website at metricverification.com, in the app, and in the verification service (together, the Service). The Service is for businesses and is directed to businesses in the United States. We operate it from the United States, and a business elsewhere that opens an account has its information handled there, under this policy. Such a business is responsible for its compliance with the laws that apply where it operates (section 1 of the Terms of Service).

2. What we collect

Contact information: name, email, company, job title, and your message, when you write to us or request a conversation, and the work email you log in with to open a demo that we share with your company, with the time you open it. Account information: your work email, the name of your company, and your name and job title, given at sign-up or by the person who adds you to an account, then your login email and the actions you take in the app. If you select Continue with Google, Google gives WorkOS the name, email address and profile picture of your Google account, and whether Google confirmed the email address. Google also gives us that information and the domain of the Google Workspace that manages the account. We use the email address, that confirmation and that domain to log you in or to make your account. When you make an account with Continue with Google, we use the name as your name on the account. Consent records: who agreed to the Terms of Service at sign-up or at a first login, or to a plan on a payment page, when, and to which wording and which version of the terms. Billing information: the plan of the company, its billing period and status, and its payments and invoices. Stripe collects card details (section 6). Reader information: the email addresses a company names on a share link, and the logins of those readers. Read-only keys: an API key that a company gives for one of its systems, so that we read the records a verification needs. Technical information: pages visited, browser type, referring page, and an approximate location derived from your IP address. When an AI assistant asks the Service about certificates, we receive its question and the IP address it came from. To limit misuse of sign-up and login, we also record each email address that asks for a code, with a keyed hash of the IP address it came from. To limit misuse of the contact form, we record the same keyed hash for each message. Business records: the records, screen recordings, system access, and statements a customer provides for a verification, which may include personal information about the customer's own employees or customers. A screen recording shows what is on the screen and carries the sound the microphone picks up, including the voice of the person making it. Public website content: when a person signs up with a work email, by the email code or with Continue with Google, the text of the public pages of the website at the domain of that email, which we read to suggest metrics to verify, and when a company opens an account, the text of the public pages of its website and its logo, which we read to propose the details of its company page.

3. Why we use it

To run the Service and your account, and to bill the plan. To perform the verifications a customer requests and to keep issued verifications sound. To answer you, to know when you open a demo that we share with your company, and to send the emails about your account, your plan, your recordings, and your verifications. To tell each address on a named share link, once, that a certificate it carried was withdrawn. To secure the Service, to limit misuse, and to meet legal obligations. We do not sell personal information, we do not share it for advertising, and we do not use business records for anything beyond the verification they were provided for.

4. Business records

When a customer provides records for a verification, we handle them as the customer's service provider. We use them only to perform the verification, we take no custody of raw records beyond a working file of extracts and notes and any screen recording, held as section 8 states, and we do not show them to anyone outside the verification. When a customer gives us a read-only key to one of its systems, we use it only to read the records that a verification needs. The customer is responsible for having the right to provide them. People whose information appears in a customer's records should direct requests about it to that customer.

5. What a shared certificate shows

A certificate shows the metric, its method, the types of data sources examined, the dates, and the name and job title of the person who submitted it. Underlying records are never shown. The customer decides who sees a certificate and where it appears.

6. Who we disclose it to

Service providers who process information for us. Except as this section states for Stripe, each provider may use the information only to serve us.

Vercel: Hosting of the website and the app, and cookieless analytics.
Supabase: Database and file storage.
WorkOS: Login by email code, and login and sign-up with a Google account.
Resend: Email: the login code, and the emails the Service sends about an account, its plan, its recordings, and its verifications, including the one notice to readers when a certificate is withdrawn, the notice to us when a demo is opened, and each message sent through the contact form.
Stripe: Payments, the billing of the plan, invoices, and the billing page where a company changes its card or cancels its plan. Card details go to Stripe and never reach us. Stripe also handles payment information as its own privacy policy states.
Google: The calendar that holds each call booked on the booking page, with the name and email of the person who books it and the name of the company, and video calls for Witnessed extractions. The name and email address of a Google account, the confirmation of the email address, and the domain of the Google Workspace that manages it, for a login or a sign-up with Continue with Google.
Anthropic: Software that reads, during a verification, the redacted text of the screens of a recording and, when our software misreads a number, an image of the one line of the screen that holds it. It also reads the public website of a company to suggest metrics to verify and for its company page.
GitHub: Servers that run our software when it reads screen recordings during a verification, and when it reads a company's public website for its company page.

We update this list when a provider changes. We also disclose information when the law requires it, to protect the rights, safety, or property of Workmain or others, and to a successor in a merger, acquisition, or sale of assets. The last two cases do not apply to the working file of a verification, which goes to a third party only as section 6 of the Verification Methods states.

7. Cookies

The app sets a cookie to keep you logged in, which lasts up to 30 days. It also sets cookies for the steps of a login or a sign-up, and each of those lasts up to 30 minutes. We set no advertising cookies and use no advertising trackers. No other party collects information about your activity across other sites through our website or the app. The payment page of Stripe and the login page of Google are their own pages, under their own privacy policies. Because we do no cross-site tracking, we do not respond to Do Not Track signals. Our analytics are cookieless.

8. Retention

Account information is kept while the account is open and for one year after. The record of each consent given at sign-up, at a first login, or on a payment page is kept for three years after it was given, for one year after the plan stops, or for one year after the account closes, whichever ends last. Records of the plan and its payments are kept for as long as tax and accounting law requires. The record of each code sent at sign-up or login, and the keyed hash recorded for each message sent through the contact form, which we keep to limit misuse, are deleted after one day. If a person who cannot already log in asks for a code at sign-up and does not open an account, WorkOS keeps the email address for up to one year. When Google gives us the information of a person who cannot already log in, we instruct WorkOS to delete the user record that it made from that information. A read-only key is kept until the company removes it, asks us to delete it, or closes its account. Each verification, and the working file behind it, is kept while its certificate stands and its account is open, and for three years after, so that it can be defended if questioned. The working file holds the observation log described in the Verification Methods, what our software found in a screen recording, and, for a screen recording, the hashes that identify it. These stay after the recording is deleted. Other raw records are returned or deleted when the verification issues. A screen recording is kept until every metric it covers has a verification issued on or after the day it was made, or until 30 days after it was made if that comes first, and is deleted within one day after. When our software reads a screen recording, it reads it on GitHub's servers, which delete their copy when the reading ends. Backups of our database hold no screen recording. Anthropic deletes what we send it, and what its software returns, within 30 days after it receives or makes it, except where Anthropic keeps it longer to enforce its usage policy or to comply with the law. Reader information is kept for the same period as the account information of the company that named the reader. Technical logs are kept for up to one year. Contact information is kept while we are in touch. After these periods we delete or de-identify the information.

9. Security

Information is encrypted in transit and at rest, access is limited to the people who need it, and logins run through a dedicated authentication provider. Security documentation is available to customers on request. No method of storage or transmission is completely secure.

10. Your rights

You may ask to see the personal information we hold about you, to correct it, to delete it, or to receive a copy. Email hello@metricverification.com. A person on the account of a company can also ask for a copy of the information of the company at the same address, and a person on the account who may do so can close the account from the Settings page in the app (section 10 of the Terms of Service). Before a company pays for its plan, a person on its account closes the account by email to the same address. We check the request against the account or contact it concerns and answer within 45 days. After a request to delete, we may keep the records that the law requires or that a legal claim needs, such as records of billing and consent. We will not treat you differently for making a request. We give these rights to everyone, wherever they live.

11. Children

The Service is for businesses and is not directed to anyone under 18. We do not knowingly collect their information.

12. Changes

We may change this policy. When we do, we update the date at the top of this page and email every person on each account about material changes.

13. Contact

hello@metricverification.com. Workmain Inc., 2261 Market St STE 85849, San Francisco, CA 94114.