Draft for legal review. A production cookie scan and verified provider inventory are required before this policy is indexed.
Essential technologies
Essential technologies support functions such as secure sessions, authentication, consent storage, request protection, load distribution, and service reliability. They are required for the website or portal to work correctly and are not used as a substitute for optional marketing consent.
Removing or blocking an essential identifier through browser controls can cause login, portal, security, form, or consent functions to stop working. Where an identifier is required only for a particular secure feature, its use should remain limited to that feature.
Analytics technologies
Analytics may help RevoCompliance understand aggregate website usage, identify broken journeys, and improve content or navigation. Analytics should load only after the applicable consent and only when a verified analytics configuration is active.
Where analytics is enabled, collection should be configured to minimise unnecessary data, respect consent withdrawal, and use appropriate retention and access controls. An analytics identifier must not be described as anonymous unless its configuration and the surrounding data flow support that statement.
Marketing technologies
Marketing or advertising technologies, if introduced, must be documented and disabled until the appropriate consent is provided. No specific provider should be listed until it is verified in the production configuration.
A marketing preference should remain separate from the ability to use public content or an essential account feature. Any audience, conversion, or advertising use requires an approved purpose, duration, provider, data flow, and withdrawal process.
Managing and withdrawing preferences
You can accept or reject optional categories through the cookie banner. Essential technologies cannot be disabled through the banner because they support core operation and security. Browser settings may provide additional controls.
Changing a preference prevents future optional use where the website controls that technology; it does not automatically erase information already processed. Browser or device settings can be used to remove stored identifiers. Blocking all storage may affect secure or personalised features.
Third-party and embedded services
Some approved service providers may set or read technologies when their features are enabled. Examples can include security verification, payment, analytics, scheduling, video, or embedded media. Optional embeds should remain blocked until the relevant consent where required.
A production cookie inventory should identify the provider, identifier, purpose, category, duration, domain, data destination, and relevant policy before legal approval. Third-party terms can change independently, so the inventory and consent behavior require periodic review.
Duration and retention
A session technology normally expires when the session ends or after a defined security period. A persistent technology can remain until its configured expiry or until it is removed. Duration should be proportionate to the purpose and confirmed from the live production configuration rather than copied from a generic policy.
Consent and other legal grounds
Optional technologies are activated only after the required preference or consent. Essential technologies may operate where they are necessary to provide a requested service, protect the website, remember a consent choice, or maintain a secure account. The applicable legal analysis depends on the countries and production providers involved and must be approved before indexing.
Policy and inventory updates
This policy and the production inventory may be updated when website technology, providers, consent behavior, or legal requirements change. Material changes should receive a new effective date and legal review before the policy is indexed.
Cookie questions and preference support
Use the Contact page for questions about consent or website technologies. Include the page, approximate time, browser and the preference you expected. Do not send account passwords, payment information, or sensitive identity documents in an ordinary cookie-policy enquiry.