Last updated: November 11, 2026

This policy explains what personal information Metric Sensei collects, why, how long we keep it, who we share it with and the choices you have. Metric Sensei is a product of Mycrom Systems, 385 Ivy Mill Ct, Roswell, GA 30076, USA (“Metric Sensei”, “we”, “us”).

It covers two different roles we play:

Our own website and accounts. When you visit metricsensei.com, contact us, sign up or use the Metric Sensei admin, we decide how your information is used.
Data we process for our clients. When a business (our “client”) puts the Metric Sensei tag on its website or connects its ad, store, CRM or other accounts, we process that data on the client’s behalf, as our terms with the client describe. For that data the client is responsible for telling its own visitors and customers what it collects. If you visited a client’s website, please also read that business’s privacy policy, and send requests about your data to them first. We will help them answer.

Information we collect about you

When you contact us or book a demo: your name, work email, company, website and what you write in the form. The form’s contents are stored in our website’s database and emailed to our team.

When you create or use an account: your name, email address, the company or agency you belong to, your role, your sign-in method (password, passkey, authenticator app, or your company’s or Google’s or Microsoft’s sign-in), your time zone and display preferences. We keep a log of changes made by administrators in each account (who changed what and when), API keys you create (we store only a scrambled hash of each key, never the key itself) and usage counts for billing.

Billing: the agency or company you bill to, invoices and payment status. Card details are entered into fields hosted by our payment processor, Braintree (a PayPal service). Card numbers never reach our servers.

Support: what you send us, and, if you ask us for help inside your account, a record that our staff opened it, when and why.

Our website: our web host (WP Engine) keeps standard server logs (IP address, browser, pages requested, time) for security and troubleshooting. Our website uses no advertising cookies and loads no third-party trackers; fonts are served from our own site.

Data we process for our clients

Depending on the services a client turns on, the Metric Sensei tag and integrations process the following about the visitors and customers of the client’s website.

Attribution. Where each visit came from (campaign parameters such as utm_source, ad click IDs, the referring site), the pages visited and conversions such as form submissions and purchases. The tag stores a random browser ID in first-party cookies and browser storage on the client’s own website, and can recognize a returning browser from a hashed set of device settings. To follow a customer across devices, it groups browsers it believes belong to the same person, and devices that share a home internet connection into a household. Each visit and form submit is also written to a raw visit history with the visitor’s full IP address, network and device details, which the client’s administrators can search with Look up. If the client turns on contact matching, contact fields that a visitor types into a form (such as email, phone, name and postal address) are normalized and turned into one-way SHA-256 hashes in the browser before they are sent. The tag never reads passwords, payment fields or hidden fields, and never changes or blocks a form. If the client also turns on contact lookup, one readable copy of those details is encrypted in the browser with a key only Metric Sensei’s admin service can use, so the client’s administrators can look a person up.

Analytics. Page paths (without query strings), the referring site’s host name only, campaign parameters, time on page, scroll depth, clicks on outbound links and file downloads, and form submits (not the values typed). Clicks on call, email, text-message and WhatsApp links are counted with the phone number or email address that was clicked, which is the client’s own published contact detail, not the visitor’s. Events the client defines in its own code can carry up to 25 values; any value that looks like an email address or phone number is replaced with “(redacted)”. Smart Events are rules the client sets up without code (a click on a button, a form submit, a page view or a section coming into view); a match is counted with the label of the button or link. Smart Events never read form fields. For the Realtime report, Analytics and Attribution keep one short row per visitor per minute (pages, events, traffic source, country, device type and an approximate location to within about 10 km, with no visitor ID) for one hour. Analytics stores no IP addresses, full user-agent strings, query strings or form values. Without Attribution, visitors are counted with a daily anonymous hash that we cannot reverse; its random salt is deleted after two days.

Event forwarding. Unless the client turns it off for a website, events the Analytics tag counts are also passed to other analytics and advertising tags the client already runs on the same page (for example Google Analytics, Google Tag Manager or the Meta Pixel), under names that start with ms_. They are passed only with the visitor’s consent and never with an email address or phone number, and the receiving tool handles them under its own terms.

Session replay (an optional add-on). A recording of how the page looked and changed during a sampled share of visits. Everything typed into fields is masked, and by default all page text is masked too.

Connected accounts. When a client connects an outside service (for example Google Ads, Meta, Microsoft Advertising, Google Analytics, Shopify, Salesforce, CallRail or WordPress), we read the reports and records the client authorizes, such as campaigns, spend, orders and leads, and, only with the client’s permission, make changes the client asks for. We keep copies of the records we read (such as orders, calls and leads, which often include an email address or phone number) so reports can cover past periods. Credentials for those services are encrypted with keys held in AWS Key Management Service.

Sending conversions to ad platforms. If a client chooses to report conversions back to an ad platform (from Attribution or from the Offline Conversions service), we send Google Ads, Meta, Microsoft Advertising or Google Analytics the conversion, its value and what they need to match it, such as an ad click ID or a SHA-256 hash of an email address or phone number. Before sending, we check the visitor’s recorded consent and the client’s do-not-send list, and we keep a log of each send.

Bot protection. Signals that tell automated traffic from people, so fake visits and form fills can be left out of reports.

Cookies and storage the tag uses on a client’s website. All are first-party (set on the client’s own domain) and none are used for advertising by us:

_msa_id: a random browser ID, kept up to 400 days.
_msa_t: the campaigns and ads that led to visits, kept for the client’s attribution window.
_msa_s: the current visit, ending after a period without activity.
_msa_x and _msa_p: short-lived notes that avoid sending the same IDs twice.
_msa_sb: only when the client serves the tag from its own domain. It is a copy of the browser ID that scripts cannot read, kept up to 400 days.

The same values are also kept in the browser’s local storage. Analytics sets no cookies of its own; it keeps its current visit in local storage. When a visitor follows a link between two websites that belong to the same client, the tags add short-lived parameters to the link (_msa, _msat and _msav) carrying the browser ID, the current visit and its campaign touches, so both websites count one visit; the tag removes them from the address once the next page has read them. We may add, rename or remove cookies and similar storage at any time as the Service changes; this list shows the ones in use when it was last updated.

Consent and opt-out. The tag can follow the consent banner on a client’s website (including IAB TCF and GPP banners), and the Analytics tag treats a browser’s Global Privacy Control signal as a refusal. Whether a banner is shown is the client’s choice and responsibility.

We do not sell personal information, we do not use clients’ data to advertise to anyone, and we do not combine one client’s data with another client’s to build profiles. The browser ID we use across our systems is never shown to clients or returned to browsers.

Sensitive information. Metric Sensei is not designed for sensitive information such as health, financial account, government ID, biometric, precise location, or racial, religious or sexual orientation data, and our terms forbid clients from sending it. If we find that it has been sent, we delete it.

How we use information

To provide, secure and support Metric Sensei and our website, and to keep accounts separate.
To answer you, schedule demos and send messages about your account, such as sign-in codes, invitations, alerts and reports you set up.
To bill for the services an account has turned on.
To find and stop fraud, abuse and attacks, and to meet legal obligations.
To improve the product, including training and testing the AI features that power it (see “The AI assistant” below).

Where the law asks for a legal basis (for example in the EU and UK), we rely on performing our contract with you, our legitimate interest in running and securing a business service, your consent where we ask for it, and legal obligations. For client data, the client chooses the legal basis and we act as its processor.

The AI assistant

If you use the AI assistant, your questions and the data it reads to answer them are processed by Anthropic’s Claude model through Amazon Bedrock, inside our AWS account. The assistant acts only with your own access, and anything that would change data waits for your approval. Amazon Bedrock does not use these prompts or answers to train its models. Please don’t type sensitive personal information into the assistant.

Improving our AI features. We may use data in the Service, including client data, assistant conversations and how people use our features, to train, test and improve the AI features and models that power Metric Sensei. We do not sell that data, and we do not use it to train models offered to anyone outside Metric Sensei.

Who we share information with

We use these service providers to run Metric Sensei. They may process personal information only to provide their service to us:

Amazon Web Services: hosting, databases, sign-in (Amazon Cognito), email (Amazon SES), encryption keys (AWS KMS) and the AI assistant (Amazon Bedrock). Our data is stored in the United States (US East and US West regions).
WP Engine: hosting for metricsensei.com.
Braintree (PayPal): card payments.
Cloudflare Turnstile: checks that a sign-up comes from a person.
Sign-in providers you choose, such as Google, Microsoft or your company’s identity provider, which tell us who you are when you sign in with them.

We may add or change service providers at any time as the Service grows. This list shows the main ones in use when it was last updated.

When a client connects an outside service or sends data to one (for example conversions to Google Ads or Meta), that data goes to the service the client chose, under that service’s terms. We may also disclose information to protect our rights, users or the public, or as part of a merger or sale of the business, in which case this policy continues to apply.

Requests from governments and law enforcement

We do not give any government or law enforcement agency access to client data unless the law requires it, for example under a valid subpoena, court order or warrant. When a request concerns a client’s data, we first point the requester to the client. If we must answer ourselves, we:

check that the request is valid and challenge it if it isn’t;
disclose only the minimum the law requires;
tell the client before disclosing, unless the law forbids it or there is an emergency involving risk of serious harm, and tell them afterwards once we are allowed to.

How long we keep it

Account information: while the account is open. When a client account is deleted, all of its data is deleted from every Metric Sensei service, including tracking data, reports, recordings and connected-account credentials.
Visitor records for attribution: removed after the client’s chosen retention period without a new visit (three months unless the client sets otherwise).
Raw visit history for attribution, including IP addresses: up to 95 days.
Analytics events: 25 months. Realtime rows: one hour.
Copies of records from connected accounts (orders, calls, leads): about 25 months.
Session recordings: 30 days.
Administrator activity log: one year.
Contact form messages: until they are no longer needed to answer you, and no longer than two years.
Billing records: as long as tax and accounting law requires.

Copies in short-term backups are kept out of use and disappear as those backups expire.

Security

Encryption: data is encrypted in transit (HTTPS) and at rest. Credentials for connected services are encrypted with keys in AWS KMS.
Hashed secrets: API keys and sign-in tokens are stored only as hashes.
Separation: each client’s data is kept separate.
Sign-in: supports passkeys and two-step verification. Changes to API keys need a fresh sign-in.
Staff access: our staff can open a client’s account only while helping that client, for up to one hour at a time, with a stated reason that is recorded in the account’s activity log.
Redundancy: the service runs in two separate US regions so it keeps working if one fails.

No system is perfectly secure. If a breach affects client data, we will tell the affected clients without undue delay, and people affected as the law requires. To report a security problem, email us at the address below.

Your rights and choices

Depending on where you live (for example under the EU and UK GDPR, or the California CCPA/CPRA and other US state privacy laws), you may have the right to know what personal information we hold about you, to get a copy, to correct it, to delete it, to object to or restrict some uses, and to withdraw consent. We do not sell or share personal information for cross-context behavioral advertising, and we do not use sensitive personal information to infer characteristics about you. We will not treat you differently for using these rights.

To use them, email us at the address below. We will confirm your identity before acting, and we aim to answer within 30 days of receiving a request, and always within the time the law sets. You may use an authorized agent, who must show us your signed permission. If we turn a request down, we will say why, and you can appeal by replying to our answer; we will review the appeal and answer within the time the law sets. In the EU or UK you may also complain to your local data protection authority.

Requests about a client’s visitors and customers. For data a client collected on its website or from its connected accounts, the client decides on the request and we act on its instructions. If you send such a request to us, we pass it to that client and help them answer. Before anything is shared or deleted, your identity is confirmed in one of these ways: you click a one-time link we email to the address in your request, you open a link on the client’s website in the browser concerned, or the client confirms who you are by its own means. Because most of what we hold about a visitor is a hash, an ID or a visit record, we answer a request to correct such data by deleting it. After a deletion we keep a record that the request was handled (dates, counts and hashed identifiers, nothing readable) for 24 months, and keep a hash of the email address and phone number on that client’s do-not-match list so they are not matched or sent to ad platforms again. Totals that identify no one are kept. We cannot recall conversions already sent to an ad platform; the client can ask that platform to delete them. Clients handle these requests in their Metric Sensei account, on the Privacy requests screen.

You can also block or delete cookies in your browser, use a browser that sends Global Privacy Control (the Analytics tag treats it as a refusal), and unsubscribe from report emails with the link in each one. Browsers’ older “Do Not Track” setting has no agreed meaning, so we don’t act on it.

International transfers

Metric Sensei is run from the United States and stores data there. If you are outside the US, your information is transferred to the US. Where the law requires it, we use the European Commission’s standard contractual clauses or another lawful transfer mechanism.

Children

Metric Sensei is a business service and is not meant for anyone under 16. We do not knowingly collect personal information from children. If you believe a child has given us information, contact us and we will delete it.

Changes to this policy

We will post any change here and update the date at the top. If a change materially affects how we use information we already hold, we will tell account administrators by email before it takes effect.

Contact us

Mycrom Systems (Metric Sensei)
385 Ivy Mill Ct, Roswell, GA 30076, USA
Email: [email protected]

Privacy Policy