Privacy Policy

Who is responsible

The operator's legal name, address, and contact details have not been added yet and must be completed before launch. For data about the visitors to a customer's website, the customer decides to install tracking and Metrivue processes the data for them; for account data, Metrivue decides how it is used.

Account data

• Email address, optional name, and time zone.
• A password hash. The password itself is never stored.
• Sign-in sessions: a hash of the session token, a shortened browser description, and timestamps. Raw session tokens are not stored.
• Security records: a salted hash of your IP address (not the address itself) used for rate limiting and an audit trail of sensitive actions such as sign-in and password reset.
• Emails we send for verification, password reset, and (unless you turn them off) alerts about high-severity issues on websites in workspaces you own or administer.
• Workspace invitations: the invited email address and role, plus a hash of the invitation link. Closed or expired invitations are deleted after 30 days by the daily clean-up job.
• Contact messages: the name (optional), email address, topic, and message you submit, plus a salted hash of your IP address. They are kept until deleted by the operator; no retention period has been set.

Website visitor data collected for customers

• Per event: time, page path without query string, hostname of an external referrer, UTM campaign values, a shortened user-agent string, and a one-way visitor identifier that changes every day.
• No IP address, cookie, local-storage value, full address with query string, or form content is stored.
• Visits that send Do Not Track or Global Privacy Control signals are not stored.

Availability checks

For each monitored website, Metrivue stores the time, result, HTTP status, response time, and error type of each check.

Why data is used

• To provide the account, sign you in securely, and send the emails you request.
• To produce analytics and health reports for the website owner.
• To prevent abuse, such as repeated sign-in attempts.

Retention

• Availability check history older than 90 days is deleted automatically.
• Expired sessions, expired tokens, rate-limit counters, and refused-request counters older than 90 days are removed by a daily clean-up job, once the operator has scheduled it.
• Analytics events are kept until the website or account is deleted, unless the operator has configured a retention period, in which case older events are deleted by the daily clean-up job. The operator must state the period here before launch.

Sharing

Data is stored on the hosting provider and sent through the configured email provider. A full list of processors will be added before launch. Metrivue does not sell personal data and does not show advertising.

Your choices

In Account settings you can edit your name and time zone, sign out devices, download your account data as a JSON file, and permanently delete your account. For anything else, see Data deletion.

Security

Passwords and session tokens are hashed, forms are protected against cross-site request forgery, and sign-in attempts are rate limited. No security audit or certification has been completed, and none is claimed.