Temporary risk-reduction notice. This page provides interim operational information while a qualified post-cutover legal review is pending. It is not legal approval or legal advice, and it does not determine whether a particular customer deployment complies with GDPR or another law.
Configuration determines the processing scope
The data processed through Monolytics depends on how the customer configures the Service, the pages included in the recording scope, and the events or properties sent to Monolytics. Customers are responsible for identifying an appropriate lawful basis, providing required notices or consent, configuring masking and access controls, and verifying the setup before production use.
Monolytics can process data on behalf of a customer when that customer uses the Service on its website or product. The categories and sensitivity of that data vary with the customer’s implementation. Public marketing copy cannot establish the lawful basis, notices, consent requirements, retention choices, or access rules for an individual deployment.
Masking and verification before production
Configure masking and redaction controls for applicable input fields and verify the rendered capture before using Monolytics in production.
Also review the configured domains, routes, audiences, events, properties, retention needs, and account access. Repeat the verification when the site, instrumentation, recording scope, or privacy configuration changes.
Customer and data-subject requests
Visitors with a request about data collected on a customer’s site should first contact that site’s operator, which determines the purpose and configuration of the deployment. Customers and Monolytics account users can contact [email protected] about account data or assistance with a Service-related request.
Related information
The temporary wording on this page remains subject to the qualified post-cutover legal review. That review—not this page—must decide whether further legal or policy changes are required.