Privacy policy

This policy covers personal data from our website, accounts, support, and customer analytics.

We act as controller for accounts, billing, support, security, and measurement of our service. We decide the purposes of that processing.

For customer analytics, the customer normally acts as controller. We follow its instructions under our Data Processing Agreement. Its visitors should also read its privacy notice.

Use our contact page for privacy requests. Identify the account or website concerned.

An account contains your name, email address, password hash, verification status, and workspace membership. If you enable two-factor authentication, we store its secret and recovery codes in encrypted form.

Session and security records can contain IP addresses, browser information, sign-in times, failed sign-in attempts, and account changes. These records help us protect accounts and investigate misuse.

Billing records can include customer references, subscriptions, invoices, payment status, card brand, and the last four digits. Stripe receives payment details through its checkout. Our application does not receive your full card number or security code.

The waitlist stores your email address for confirmation and access invitations. Contact messages pass to us by email. The contact form does not keep a separate message record in the application database. Our mailbox and mail service still process the message.

Where law requires a legal basis, the basis depends on the purpose:

• Contract: create accounts, provide the service, manage subscriptions, and answer service requests.
• Legitimate interests: protect the service, investigate abuse, maintain records, and understand how our service performs, subject to your rights.
• Legal obligations: keep financial records and respond to valid legal requirements.
• Consent: carry out an optional activity where consent is required.

You can withdraw consent for future processing. This does not change earlier lawful processing or remove contractual and legal obligations.

Measurements can include event names, times, page or screen paths, referring hosts, campaign tags, language, browser family, operating system, and device class. Location fields depend on the customer’s settings and available request information.

The service uses an IP address during receipt for functions such as location and stateless measurement. It does not store that address in ordinary analytics event records. This does not mean infrastructure or account security logs contain no IP addresses.

Before storage, page addresses lose query strings and fragments. Referrers reduce to host names. Custom-property filters remove certain sensitive fields and mask some personal values. Filters cannot detect everything. Customers must not send secrets or unnecessary personal data.

The tracking script does not set analytics cookies. Some modes use local storage for visitor and session identifiers. The cookie policy explains the entries and controls.

The default automatic mode selects stateless measurement for the European Economic Area, United Kingdom, Switzerland, and unresolved countries. Other regions can use device storage. Customers can select strict mode for all visitors.

Stateless measurement uses identifiers that change daily and differ between projects. It still counts activity. A hash or random identifier is not a guarantee that data falls outside privacy law.

Global Privacy Control and Do Not Track select stateless measurement unless the visitor later gives explicit consent. A tracker opt-out stops event transmission.

Customers can send their own user identifiers and traits when they enable identified tracking. Optional features can collect custom properties, revenue values, click positions, page-performance values, and additional location fields. The individual-view setting limits access to person views; it does not prevent every trait from being stored.

Optional widgets can record reactions, helpfulness answers, survey scores, and comments. Survey filters mask some email addresses, links, and long numbers. They do not make every comment anonymous. Do not put sensitive or unnecessary personal information in a comment.

A speed test records connection measurements, such as upload speed, download speed, latency, and connection quality. Its context can include network provider, location, device information, and a support code. If you choose to share your browser location, the service rounds its coordinates before storage. The browser permission request remains separate from general analytics settings.

The customer decides which widgets appear on its website. Its privacy notice should explain their purpose.

We can use DataVisitors to measure our public website and application. Application tracking uses route patterns in place of workspace or project names in page addresses. Preference storage remembers choices such as appearance and palette.

Our Inter font request discloses connection information, including an IP address, to rsms.me. Other providers receive data through relevant services, such as checkout.

If a customer connects Google Analytics or Search Console, we store an encrypted authorization grant and import the permitted reports. Customers can also direct data to exports, reports, webhooks, or their own connected tools.

We do not sell personal data or use customer analytics for advertising profiles. We do not combine customer projects into a cross-site advertising identity.

Authorized workspace members can access data according to their permissions. Customers control their public report links. Those links expose permitted aggregate results, so customers should share them carefully.

Hosting, network, backup, payment, and communication providers process information needed for their services. The subprocessor page describes identified providers and their functions. Some payment activities also fall under the payment provider’s own responsibilities.

Processing can occur outside your country. We do not promise exclusive processing in one country. Applicable law can require an adequacy decision, contractual safeguards, or another permitted transfer mechanism. Contact us for information about transfers concerning your data.

We can disclose information where a legal requirement applies or where necessary to protect legal rights and investigate abuse.

Ordinary analytics events receive a retention period when collected: Free 90 days, Starter 365 days, Growth 730 days, and Business 1095 days. A plan change affects new events. Storage maintenance applies expiry, rather than deleting each record at an exact second. Derived summaries can have a different expiry from individual events.

Stored person traits expire a year after their last update. Individual erasure requests run asynchronously. Removing a project stops new collection but does not immediately erase every stored measurement. Contact us about broader deletion requests.

Account records remain while needed to provide the account. Closing an account does not automatically remove all financial records, security records, or workspace data. Sign-in and activity records normally remain for three years. Financial records have no automatic deletion schedule. Waitlist entries remain until removal is requested.

Hourly remote backups normally retain thirty days. If a recent complete backup is unavailable, older backups remain until safe replacement resumes. Separate account-data archives can retain records for up to two years. We do not rewrite individual backups when a live record is deleted.

Depending on applicable law, you can request access, correction, deletion, restriction, portability, or objection to processing. You can also complain to the relevant data protection authority.

Account settings provide profile changes, exports, session controls, and account closure. We may verify identity before answering a request. For customer analytics, contact the customer first. Identify the website if you need our help.

DataVisitors provides a business service. It does not target children. Customers must not use it to collect children’s information unlawfully.

We publish policy changes on this page. Read it with the terms, cookie policy, and Data Processing Agreement.