1.1 Accept all
Accept all turns on required storage plus optional preference and analytics categories that are available for the page.
COOKIE POLICY
Atom9 separates required storage from optional choices.
Atom9 uses cookies and browser storage for login, security, workspace routing, privacy preferences, interface preferences, and customer-app flows. Optional analytics and non-essential tracking stay separate from required storage.
Effective date
June 27, 2026. Required cookies and storage are used only where needed for service operation, security, authentication, user-requested settings, or legal records. Optional analytics and marketing storage require a valid choice where ePrivacy, GDPR, or local law requires consent.
Cookies 1
The privacy preference panel gives clear and reversible choices.
Choice modelRequired storage keeps the service working. Optional storage follows the user's choice.
RequiredAlways activeLogin, security, routing, OIDC return, and privacy preference records.
User choiceAccept, reject, or customizeThe preference panel stores the user's current decision.
OptionalOnly when allowedPreferences and analytics that are not necessary for the service.
Legal anchors: Cookies 1.1 to 1.4 define the choices, Cookies 2 defines categories, and Cookies 6 defines consent quality.
1.2 Reject optional
Reject optional keeps required storage active and turns off optional analytics and optional preference categories that are not needed to provide the requested service.
1.3 Customize
Customize lets the user choose optional categories while required login and security storage remains active.
1.4 Change later
Users can reopen privacy preferences from the footer, login page privacy links, or product privacy controls where available.
Cookies 2
Atom9 treats cookies by purpose, not by technical label alone.
2.1 Required storage
Required storage supports authentication, session security, CSRF protection, workspace routing, OIDC return paths, privacy records, and customer-app context.
2.2 Preference storage
Preference storage supports theme, layout, language, chat width, accessibility choices, and other settings that make Atom9 easier to use.
2.3 Analytics storage
Analytics storage supports product-quality measurement and page-use analysis. Analytics is optional where consent is required and is off until accepted.
2.4 Third-party storage
OIDC providers, embedded media, AI tools, payment providers, analytics, or customer-selected integrations can set their own storage under their own notices and controls.
Cookies 3
Atom9 uses small browser records to keep the product secure and understandable.
3.1 a9_session
Required HttpOnly session cookie that keeps a signed-in user authenticated. It cannot be read by normal page scripts.
3.2 a9_tenant
Required routing cookie that identifies the active Atom9 tenant or workspace context for authenticated requests.
3.3 a9_oidc_next
Required short-lived cookie that remembers the safe return path after an OIDC login flow.
3.4 a9_oidc_remember
Required short-lived cookie used only during OIDC login to carry the user's remember-me choice into the callback, then cleared.
3.5 a9.privacy.preferences.v1
Local browser storage for the user's privacy preference choice, including accept, reject, or customized category settings.
3.6 a9.marketing.theme
Preference storage for light or dark mode. Atom9 uses this to honour a user-requested interface choice.
Cookies 4
Required storage is necessary and does not require optional consent.
4.1 Required purposes
Required storage supports authentication, session continuity, security, fraud prevention, CSRF protection, load routing, workspace selection, customer-app context, privacy preference records, and legal or operational records.
4.2 Browser blocking
If a user blocks required storage in the browser, Atom9 or a customer app may not be able to sign the user in, protect the session, remember the selected workspace, or complete account actions.
4.3 Security priority
Atom9 does not disable required storage when doing so would weaken authentication, security, fraud prevention, legal records, or the integrity of user-requested actions.
Cookies 5
Sites built with Atom9 can require their own cookie notice.
5.1 Customer site storage
A customer site can use Atom9 login, booking flows, forms, embedded media, analytics, payment providers, chat widgets, maps, or customer-selected integrations.
5.2 Customer responsibility
The site owner controls its own service-specific cookie and storage choices, including optional categories, notices, consent wording, third-party providers, and withdrawal paths.
5.3 Atom9 tooling
Atom9 provides tools to generate, display, store, update, and evidence the notice and preference controls for customer sites.
Cookies 6
Atom9 designs consent controls to be clear, specific, reversible, and non-deceptive.
6.1 Equal clarity
Accept and reject choices are presented clearly. Optional choices are not hidden behind confusing wording or deceptive design.
- Required storage is explained separately from optional storage.
- Reject optional is available with comparable clarity to accept all.
- Customize explains optional categories before the user decides.
6.2 Specific purpose
Optional categories explain what they do. Analytics is separate from required login and security storage.
6.3 Withdrawal
Users can reopen preferences and change optional choices. Withdrawal does not affect required storage needed to provide the service.
6.4 Records
Atom9 keeps a local preference record so the banner does not repeatedly ask after a valid choice is made.