Cookie Policy
Last updated:
Cookies and similar technologies (such as local storage) store information in your browser. This policy lists exactly what we use. It supplements our Privacy Policy.
1. This website
This marketing website’s own code sets no cookies, stores nothing in your browser, and loads no analytics, advertising or social-media tags. Our hosting providers add only what is strictly necessary to run the site:
- Cloudflare may set a security cookie (such as
__cf_bm) when it needs to tell people from bots. It does not track you across sites. - Our website platform’s error reporter may keep a random per-tab id (
__tyTelSid) in session storage when a page error is reported, and a one-time flag (__tyTelReload) if it reloads a page that failed to load. Session storage is cleared when you close the tab. It also writes and immediately removes a test key (__ty_test) to check that storage works.
If we add analytics to this site, we will use YOM in its default cookieless mode and update this page first.
2. The YOM dashboard
When you sign in to YOM, the dashboard stores the following in your browser’s local storage. They are strictly necessary for the service you asked for. No YOM cookies are set.
| Name | Type | Set when | Purpose | Lasts |
|---|---|---|---|---|
| yom_token | Local storage | You sign in | Keeps you signed in (session token) | Until you sign out; the token expires after 24 hours |
| yom_user | Local storage | You sign in | Your name and email for the interface | Until you sign out |
| yom_tenant | Local storage | You sign in | Which organisation you are working in | Until you sign out |
| yom_selected_project | Local storage | You pick a project | Remembers the selected project | Until cleared |
| yom_portal_session | Local storage | A client signs in to a client portal | Keeps the client signed in to the portal (session token) | The token expires after 12 hours |
If you choose Google sign-in, Google’s sign-in script loads from Google and Google may set its own cookies under its policy. Payment pages run by our payment providers may set their own cookies.
3. The YOM SDK on our customers’ sites
Our customers install the YOM SDK on their own websites and apps and decide how it is configured. The current SDK sets no cookies and sends requests without cookies. By default it is cookieless: until a visitor grants analytics consent it keeps no persistent identifier and writes nothing to the browser, and Do Not Track and Global Privacy Control are treated as a refusal. After consent, it may use:
| Name | Type | Set when | Purpose | Lasts |
|---|---|---|---|---|
| yom_visitor_<id> | Local storage | Only after the visitor grants analytics consent | Random visitor id, so returning visits are recognised | Until consent is withdrawn or storage is cleared |
| yom_session_<id> | Local storage | Only after analytics consent | Session id, last activity time and the landing referrer and campaign | Ignored after 30 minutes of inactivity; removed when consent is withdrawn |
| yom_consent_<id> | Local storage | Only when the visitor grants consent (and the site allows remembering it) | Remembers the consent choice | Until consent is withdrawn or storage is cleared |
| yom_fp | Local storage | Only after analytics consent, and only if the site owner turns on cross-site identity (off by default) | Hash of browser characteristics to recognise the same browser across that owner’s sites | Until storage is cleared |
The <id> suffix is a short hash of the site’s key, so two sites on the same domain keep separate entries. When a visitor withdraws consent, the SDK removes yom_visitor_<id>, yom_session_<id> and yom_consent_<id>.
If the site owner forwards conversions to Meta and the visitor has given marketing consent, the SDK may read (never set) Meta’s own _fbp and _fbc cookies so Meta can match the conversion. If the site owner enables browser forwarding to its own Google Analytics or Meta Pixel, those tags load only after marketing consent and may set their own cookies under Google’s and Meta’s policies. The site owner is responsible for its consent banner and for describing these in its own cookie notice.
4. Third-party cookies
We do not place advertising or cross-site tracking cookies on this website or in the dashboard. The only third-party cookies are the ones described above, set by Cloudflare, Google or payment providers when you use their features, and by tags a site owner chooses to load with consent.
5. Your choices
- You can clear cookies and local storage in your browser settings at any time; signing out of the dashboard also clears its session.
- On a site that uses YOM, use that site’s consent controls, or turn on Global Privacy Control in your browser.
- Questions: contact@aapastech.com.