Purpose of this policy
This policy explains the cookies and similar technologies used on the website, in the Objeqo application, and in the Chrome extension.
In particular, it describes Google Analytics audience measurement on the website’s public pages after consent. No behavioral advertising or marketing retargeting tool is enabled as of the date of this version.
Definition of cookies and similar technologies
A cookie is information stored on or read from a user’s device when they access an online service. The same rules may apply to other mechanisms used to store or read information, including localStorage, sessionStorage, certain identifiers, or an extension’s local storage.
These technologies may be placed by Objeqo or by a provider acting to deliver a requested feature.
Current consent status
Technologies necessary for authentication, security, interface preferences, continuity of navigation, and the operation of the Extension are used to provide the Service or a feature expressly requested.
Google Analytics is an optional audience measurement tool. Its tag remains disabled until the visitor accepts the analytics purpose through the consent banner. The option to refuse is presented at the same level as the option to accept, and refusal does not prevent access to the website or the Service.
Campaign attribution is an optional and separate purpose. It retains the first known page and the visit source to understand which campaign leads to a sign-up. It can be accepted or declined independently of Google Analytics.
These choices can be changed at any time using the “Manage cookies” button available on public pages. Declining audience measurement disables collection and triggers the deletion of Google Analytics cookies accessible from the Objeqo domain. Declining attribution deletes the corresponding temporary storage.
Web application storage
Authentication session
Storage location: browser local storage.
Data: technical tokens and information needed to maintain the authenticated session.
Purpose: maintain the session, renew the access token, and keep the User signed in when they return to the application.
Duration: until sign-out, revocation, or expiration of the session under the security rules configured by Objeqo, or until local storage is cleared. The access token is automatically renewed while the session remains valid.
Theme preference
Storage location: browser local storage.
Purpose: remember the light or dark theme chosen by the User.
Duration: until the preference is changed or local storage is cleared.
Active call
Storage location: temporary storage for the browser session.
Purpose: retain the current call ID across the preparation, launch, live, and report steps.
Duration: for the duration of the tab session, unless deleted earlier by the application.
Navigation state
Storage location: temporary storage for the browser session.
Purpose: temporarily preserve the relevant step or state when returning between pages in the flow.
Duration: for the duration of the tab session, unless replaced or deleted earlier.
Choices for optional purposes
Storage location: browser local storage.
Purpose: remember choices for Google Analytics and campaign attribution separately, so they are not requested again on every page.
Duration: six months from the time the choice is made, after which the banner is shown again.
First-visit attribution
Storage location: after campaign attribution is accepted, local storage and a first-party cookie are used as complementary fallback mechanisms.
Purpose: retain the first known page, the browser's referral source, and any campaign parameters present, so that this source can be linked to the account if the visitor chooses to sign up.
Data: page URL limited to UTM, gclid, and fbclid parameters; referrer without parameters or fragment; first-visit date; and the page where sign-up was initiated. No form content, email address, name, transcript, or call data is placed in this storage.
Duration: up to ninety days before sign-up. Temporary storage is deleted after being linked to the account or after campaign attribution is declined. Linked attribution is then retained for the lifetime of the account.
Free tool security
Keys: objeqo_ft_visitor and objeqo_ft_verified.
Storage location: first-party cookies strictly necessary for the security of free tools.
Purpose: objeqo_ft_visitor assigns the browser a signed random identifier to enforce quotas and prevent abuse of free tools. objeqo_ft_verified temporarily stores proof that a Cloudflare Turnstile verification was successfully completed for the same browser.
Data: random technical identifier, security signature, and verification expiration. These cookies do not contain any name, email address, form content, transcript, or call data.
Duration: up to twelve months for objeqo_ft_visitor and twenty-four hours for objeqo_ft_verified.
Google Analytics audience measurement
After acceptance, the Google Analytics tag is loaded on Objeqo's public website pages. It is used to measure pages viewed, visit sources, and configured navigation events to understand acquisition and improve the site.
Objeqo does not send Google Analytics the query parameters from page URLs. Private routes in the application, APIs, authentication callbacks, and technical Extension pages are excluded from measurement. This integration does not send transcripts, audio recordings, prompts, notes, or call content to Google Analytics.
Google Signals and advertising personalization signals are disabled in the tag configuration. This mechanism does not request or grant advertising consent.
Google Analytics cookies
Keys: _ga and associated cookies beginning with _ga_.
Storage location: browser cookies set only after acceptance.
Purpose: distinguish visits and retain the information needed to measure traffic to the public website.
Configured duration: up to thirteen months after creation. Under Objeqo's configuration, the duration is not extended with each visit.
Chrome Extension storage
The Extension uses local storage managed by Chrome to retain the information needed for sign-in, display, and call handling. It also uses a local browser database to temporarily secure the transmission of audio and transcripts.
- Sign-in session: technical information needed to link the Extension to the Objeqo account, retained until sign-out, session invalidation, or removal of the Extension;
- Interface preferences: theme, sounds, notifications, and widget display, retained until changed, reset, or the Extension is removed;
- Call state: ID, start time, duration, audio source, and command status, replaced or reset when the call ends;
- Assistance context: temporary information needed for live suggestions, reset when the call ends;
- Temporary transmission: audio fragments, final transcript segments, and pending synchronization information, deleted after successful transmission. If an error persists, they remain stored until a successful retry, a storage reset, or removal of the Extension.
Technologies not currently used
OpenAI is accessed by Objeqo's servers. This API integration does not directly place an OpenAI cookie in the User's browser through Objeqo pages.
Any change to this status will result in an update to this policy and, where necessary, a prior adjustment to the consent mechanism.
- no advertising pixel or retargeting tracker has been identified;
- Objeqo attribution storage does not send any data to an advertising network;
- no social sharing module that sets trackers has been identified.
Relevant service providers
Data processing associated with these service providers is described in greater detail in the Privacy Policy.
- Supabase: management of authentication and application sessions;
- Google Analytics: audience measurement on public pages after consent;
- Cloudflare, Inc.: security verification and abuse prevention for free tools using Cloudflare Turnstile;
- Google Chrome: provision of the Extension's local storage, under the control of the User's browser;
- Vercel Inc.: hosting, running, and delivery of the website and web application.
Manage or delete storage
The User can clear website data from their browser settings. This may sign them out, remove their theme, and interrupt continuity of an ongoing call or flow.
Extension data can be cleared by resetting its settings, signing out when a corresponding command is available, or removing the Extension from Chrome. Deletion may result in the loss of preferences and widget state.
Menus and labels vary by browser. A global technical refusal of all storage may prevent authentication and certain requested functions.
The “Manage cookies” button lets you reopen the choices for audience measurement and campaign attribution. Withdrawal of consent takes effect immediately for future collection for the relevant purpose.
Durations and review
Durations are listed above for each technology. They must be reviewed whenever the Supabase configuration, Extension, or navigation mechanisms change.
A storage audit is performed when adding or modifying an audience measurement service, third-party conversational support, integrated payment, advertising, or campaign tracking.
Policy updates
This policy may be updated to reflect a technical change, the addition or removal of a service provider, or a regulatory change. The update date is shown at the top of the page.
If a new tracker requiring consent is added, it will not be activated until the User has received appropriate information and made a choice.
Effective Date and Contact
This policy takes effect on August 20, 2026. Version: 1.4.
Any questions about cookies or local storage may be sent to privacy@objeqo.com or submitted via the Contact page.