This cookie policy explains how aeoora uses cookies and similar technologies such as localStorage. It covers our marketing website, the aeoora app at app.aeoora.com, and the tracking snippet that customers can install on their own sites. For how we handle personal data generally, see our Privacy Policy.
What cookies are
Cookies are small text files that a website stores in your browser. Similar technologies, such as localStorage, do the same job: remember something between visits. Some are strictly necessary for a site to work. Others measure usage or remember preferences. “First-party” means set by the site you are visiting; “third-party” means set by another service.
Strictly necessary cookies in the app
These cookies are required to sign you in securely. They do not need consent, and the app does not work without them.
- aeoora-access-token. A short-lived sign-in token that proves who you are on each request. Lasts about 1 hour.
- aeoora-refresh-token. An httpOnly cookie used to renew your session without signing in again. Expires after 30 days without use.
- aeoora-oauth-state. A security value used while signing in with Google or GitHub to prevent cross-site request forgery. Lasts 10 minutes.
- auth_next. Remembers the page you were trying to reach so we can send you back after you sign in. Short-lived and removed after sign-in.
Preference storage in the app
The app remembers your chosen theme (light or dark) in your browser so it looks the same next time. This is stored on your device and not used for tracking.
Analytics in the app
We use a product analytics service, hosted in the United States, to understand how the app is used so we can fix problems and improve it. It stores an identifier in localStorage and a cookie in your browser.
- Profiles are created only for signed-in users (“identified only”), so we can connect usage to an account when you need support.
- Automatic capture of every click is turned off. We record only the events we have chosen to track.
- Session replay may be used to diagnose usability problems. All form inputs are masked, so what you type is not recorded.
- We use this data only for product analytics, not for advertising, and we do not sell it.
You can opt out of analytics where the app provides a setting, by blocking analytics scripts in your browser, or by emailing support@aeoora.com.
Marketing website cookies
Our marketing website runs on WordPress. It uses:
- A necessary consent cookie. It stores your cookie choice so we do not ask you again on every page. It contains no personal data and lasts 12 months.
- Optional analytics cookies. The marketing website does not currently set any analytics cookies. If we add analytics in the future, they will be set only after you accept them in the cookie banner, and we will name the provider and its cookies here and in the cookie banner’s settings before we turn them on.
- Embedded content. If a page embeds content from another service (for example a video), that service may set its own cookies when you load it. We try to load such content only after you consent.
Some forms, such as sign-up in the app, use a bot protection check to block automated abuse. It is designed to work without tracking you across sites, but it may set or read technical data needed to run the check.
Website assistant
The chat assistant on our website keeps a random conversation ID and your recent messages in your browser’s localStorage (aeoora_chat_v1), so the conversation is still there when you move between pages. It sets no cookies. Clear your browser’s site data to remove it.
The aeoora tracking snippet on customers’ sites
Customers can add our snippet (t.js, loaded from api.aeoora.com) to their own website to see visits that come from AI assistants. By default it sets no cookies and does not store anything on the visitor’s device. It reads the page address and referrer to classify a visit.
If the site owner turns on conversion tracking, the snippet stores a random visitor identifier in the browser’s localStorage under the name aeoora_v, so a later conversion can be linked to an earlier AI visit. It supports consent modes: depending on the owner’s setup, the identifier is stored only after the visitor has consented, and it is not stored if consent is denied. The site owner is responsible for the consent banner and for informing their visitors; aeoora acts as their processor.
On Shopify stores, the same behavior applies, and the Customer Privacy API consent state is respected.
The WordPress plugin
The free aeoora WordPress plugin tracks AI-assistant referrals without cookies and without storing IP addresses, and it has no telemetry. It works with the WP Consent API where your site uses it.
How to control cookies
You can control cookies in several ways.
- Use the cookie banner on our website to accept or decline optional cookies, and change your choice at any time using the cookie settings link in the site footer, if shown.
- Change your browser settings to block or delete cookies and localStorage. Check your browser’s help pages for steps. Blocking necessary cookies will stop you from signing in to the app.
- Use browser privacy tools or signals such as Global Privacy Control, which we treat as an opt-out of optional analytics where we can detect it.
Changes to this policy
We may update this policy when our cookies or tools change. The effective date is November 13, 2026. We will update the cookie list and, where needed, ask for consent again.
Contact
Questions about cookies: support@aeoora.com. Postal address: aeoora, Hillside, New Jersey, United States.