Cookies

Cookies are small text files that a website or online service may store on a user's device. They can help a service maintain sessions, remember permitted preferences, support security, and operate technical functions.

Similar technologies may include browser storage, local storage, session storage, pixels, software-development-kit storage, or other methods that store or access information on a device.

Cookies and related identifiers do not always identify a person directly. However, technical identifiers may constitute personal data when they can be associated with an account, device, or individual.

This Cookie Policy should be read together with the Privacy Policy.

FERN RuleFinder may use cookies or similar technologies that are necessary to operate the platform and provide functions requested by the user.

Strictly necessary technologies may support:

- secure sign-in sessions;

- authentication;

- protected-page access;

- account permissions;

- security-related session state;

- prevention of unauthorized access;

- completion of user-requested platform functions.

Blocking strictly necessary technologies may prevent sign-in, protected workspace access, session continuity, or other essential functions from working correctly.

Authentication cookies or equivalent session technologies may be used to recognize a signed-in user and maintain secure access during an active session.

They may support account login, protected workspace access, session continuity, account-level permissions, security checks, sign-out, and session expiry.

Authentication information is used for operating and protecting the account and platform in accordance with the Privacy Policy.

Where implemented, functional technologies may remember permitted interface or workspace choices.

These choices may include display preferences, language or regional settings, navigation state, permitted workspace preferences, or cookie-consent choices.

Functional technologies that are not strictly necessary will be used only where legally permitted and, where required, after consent has been obtained.

Only preference technologies that are actually active should be identified as operational platform features.

FERN RuleFinder may process limited technical information required to diagnose errors, maintain reliability, protect platform security, identify failed requests, improve technical performance, and investigate operational incidents.

Technical logging does not necessarily involve cookies or browser storage. It should be described as cookie-based analytics only where cookies or similar device-storage technologies are actually used for that purpose.

If optional analytics or performance technologies are introduced, their provider, purpose, duration, and data use will be disclosed. Where consent is legally required, those technologies will not be activated before consent is obtained.

Some FERN RuleFinder functions may connect to external providers used for authentication, payment processing, hosting, infrastructure, email delivery, security, or technical monitoring.

When a user interacts with an external service, that provider may apply its own cookies or similar technologies under its own privacy and cookie terms.

The production Cookie Policy should identify only providers and technologies that are actually integrated. It should explain the provider, function, technology, purpose, duration, and whether consent is required.

A provider should not be listed merely because it may be used in the future.

FERN RuleFinder will maintain a factual inventory of active cookies and similar technologies used by the production platform.

The inventory should identify:

- the cookie or storage name;

- the provider;

- its exact purpose;

- its category;

- whether it is strictly necessary;

- its duration or expiry;

- whether consent is required.

The inventory must reflect only technologies that are actually deployed across public pages, account access, professional workspaces, payment flows, and mobile interfaces where applicable.

Until the technical inventory is completed, optional analytics, marketing, or preference technologies should not be represented as active platform features.

Users can review, block, or delete cookies through their browser settings.

Most browsers allow users to:

- view stored cookies;

- remove existing cookies;

- block selected cookies;

- block all cookies;

- receive notifications when cookies are set.

Blocking strictly necessary technologies may affect sign-in, protected account access, session continuity, and other essential platform functions.

Where FERN RuleFinder provides a cookie-preference control, users should be able to review and change their non-essential choices through that control.

Non-essential cookies and similar technologies will be used only where legally permitted and, where required, after valid consent has been obtained.

Consent must involve a clear and informed choice. Continuing to browse without an affirmative action will not by itself be treated as consent for non-essential technologies where affirmative consent is required.

Where consent is used, users should be able to withdraw or change that consent.

Withdrawal does not affect processing that was lawful before the withdrawal.

Cookie rules and personal-data rules are related but distinct.

Where information collected through cookies or similar technologies constitutes personal data, it will also be processed under an appropriate legal basis and in accordance with the Privacy Policy.

The applicable legal basis may depend on the category of technology, whether it is necessary for a requested service, the purpose of the processing, whether valid consent is required, and the applicable jurisdiction.

The policy should not state that every essential technology relies on one single legal basis. The appropriate basis must be determined for each processing purpose.

Cookies and similar technologies should be retained only for as long as necessary for their stated purpose.

The production inventory should distinguish between:

- session technologies that expire when the browser or session ends;

- persistent technologies retained for a defined period;

- consent-preference records;

- technologies controlled by verified external providers.

Retention periods should be reviewed whenever platform functionality, providers, or processing purposes change.

This Cookie Policy may be updated to reflect changes in platform functionality, cookies or similar technologies, external service providers, technical operation, or legal requirements.

Material changes will be published on this page with an updated revision date.

Questions about cookies, privacy, or related platform practices can be submitted through the Contact Support page.

The request should include a clear description of the question and identify the relevant page, account feature, or device environment.