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.
Cookie choices on Monolytics-owned domains
On monolytics.app, optional analytics and marketing storage starts denied. The self-hosted consent manager records the detailed choice in browser local storage. It also writes a functional preference cookie named monolytics_consent_v2 with an analytics flag (a0 or a1) and a marketing flag (m0 or m1). The cookie is scoped to .monolytics.app for up to 365 days so the saved choice can be read across Monolytics subdomains.
The Google Tag Manager container is requested only after analytics or marketing is granted. Changing a granted purpose to denied schedules a page reload so tags already loaded under the earlier choice are unloaded. Use the Cookie preferences link in the footer to review or change the optional-purpose choices.
Customer deployments
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.
The settings described above apply to Monolytics-owned domains. A customer must separately decide what notice or consent flow is appropriate for its own site and implementation.
Masking and verification before production
Configure masking and redaction controls for applicable input fields and verify the rendered capture before using Monolytics in production.
Related information
Questions about the Monolytics-owned-domain preference mechanism can be sent to [email protected]. The temporary wording on this page remains subject to the qualified post-cutover legal review.