Agorà storage transparency

This notice explains how AGORÀ may use cookies, local storage, and similar client-side technologies.

AGORÀ may store small amounts of information on a user’s device or access information already stored there in order to run the service, keep sessions secure, remember choices, and support platform functionality. Some storage is strictly necessary for the service to work. Other storage may require consent where law requires it.

Strictly necessary Some storage may be required for login, security, session continuity, and delivery of requested features.

Preferences AGORÀ may remember user choices such as theme, language, interface state, or legal acknowledgment state.

Consent-based If AGORÀ later enables non-essential analytics, advertising, or optional tracking, consent should be obtained where required by law.

Cookies & Storage Notice

Effective date: 2026-03-18
Version: 2026-03-18-v1
This page should be aligned with the real technologies and storage keys used by the live service.

Contents

1. What this notice covers 2. Types of storage AGORÀ may use 3. Categories of cookies and storage 4. Current or expected AGORÀ uses 5. Third-party services 6. User choices and controls 7. Consent and withdrawal 8. Changes to this notice

1. What this notice covers

This page explains how AGORÀ may use browser cookies, local storage, session storage, or similar device-side technologies. These technologies may be used to recognize a browser session, preserve settings, keep security state, and support requested features.

This notice should be read together with the Privacy Policy and Terms of Service.

2. Types of storage AGORÀ may use

Cookies — small text files stored by the browser;
Local storage — browser-based key/value storage that may persist beyond the session;
Session storage — storage that may last only for the current browser session;
Similar technologies — comparable methods used to store or access data on the device where technically applicable.

AGORÀ may use one or more of these methods depending on how the platform is implemented over time.

3. Categories of cookies and storage

Category	Purpose	Typical examples	Consent status
Strictly necessary	Needed to provide the service requested by the user or to ensure basic security and technical operation.	Authentication state, CSRF protection, login continuity, abuse prevention, load balancing, essential session handling.	Usually not consent-based where the law recognizes them as technically necessary.
Preferences	Remember user choices for convenience and interface continuity.	Theme mode, language, accessibility settings, dismissed notices, UI layout preferences.	May be treated as essential or consent-based depending on necessity and local law.
Functional	Support optional platform features requested by the user.	Saved draft continuity, remembered view state, interactive feature persistence.	Depends on whether the function is necessary for the requested service.
Analytics / measurement	Understand usage patterns and improve the service.	Traffic measurement, page interaction metrics, feature usage statistics.	Consent should be obtained where required before activation.
Advertising / tracking	Deliver ads, limit repetition, or measure advertising performance.	Ad-related identifiers, attribution signals, cross-context tracking technologies.	Consent should be obtained where required before activation.

4. Current or expected AGORÀ uses

Based on the current AGORÀ pages and expected service design, AGORÀ may use or later use storage for items such as:

Theme preference — for example remembering light or dark mode;
Terms acknowledgment state — for example storing whether a user has accepted a displayed legal version;
Session continuity — where needed to keep the user signed in or preserve a valid session state;
Security state — to help prevent abuse, replay, or unauthorized use;
Feature continuity — such as preserving a requested user interface state or unfinished draft interactions where implemented.

If AGORÀ later enables analytics, advertising, or optional cross-site tracking tools, the live service should display an appropriate consent mechanism before activating them where the law requires it.

5. Third-party services

AGORÀ may rely on third-party services for hosting, authentication, maps, content delivery, security, or future features. Some third-party services may independently store or access information on the user’s device, or receive technical information from the browser as part of delivering their service.

If AGORÀ uses such services, the live version of this page should name them clearly where appropriate and should explain whether they are strictly necessary, optional, or consent-based under the applicable legal framework.

6. User choices and controls

Users may manage some storage technologies through browser settings, privacy tools, or device controls. Depending on the browser, users may be able to delete cookies, block certain storage, clear local storage, or limit some tracking technologies.

Blocking or deleting storage may affect platform functionality. For example, users may need to sign in again, reselect preferences, or lose continuity in requested features.

8. Changes to this notice

AGORÀ may update this Cookies & Storage Notice to reflect changes in technology, legal requirements, or platform functionality. The current version should always be available on this page.