← Back to OTRIA

Cookie notice

Last updated: 2 October 2026. This notice covers cookies and browser storage used to provide Otria’s comparison and account services.

Current use

Otria uses necessary storage for your chosen language, sign-in, comparison progress and returning from sign-in to a saved action. No advertising, analytics or cross-site tracking cookies are enabled in this launch. We use Vercel Web Analytics without analytics cookies to measure visits to public pages, referral sources, device types and countries. Query strings and URL fragments are removed, and private account, comparison-result and application routes are excluded. Invoice contents and form answers are not sent as analytics events.

Cookie inventory

otria_locale: Otria’s first-party language preference, up to one year after an explicit language choice. sb-<project-ref>-auth-token (including numbered chunks): Supabase session credentials set as first-party HttpOnly cookies by Otria, Secure over HTTPS and SameSite=Lax; the SDK cookie lifetime is up to 400 days and may be renewed, while token/session validity is separately controlled by authentication. Signing out removes the local session. A short-lived sb-<project-ref>-auth-token-code-verifier cookie may be used to complete email-link sign-in; it is removed after the exchange.

Browser storage

Session storage (this tab) holds otria.preview.journey.v2, offer-result/error caches, navigation history and any legacy Watch draft to preserve the action you request. Journey, error and offer-result data are accepted for up to 24 hours; changing the profile or starting again clears the comparison snapshot. otria.local.supply.v1 temporarily holds name, address and CUPS extracted from your own bill for an assistance prefill, accepted for up to 24 hours. Local storage keys beginning otria.account.continue. preserve a selected action across sign-in for up to 24 hours; they include the optional home nickname, address and CUPS alongside the selected offer, and are removed when consumed or when an expired record is read. These are application validity limits, not automatic browser expiry: unused entries can remain until you clear site data. Bank details are not stored there. Your own invoice is temporarily kept in this browser in IndexedDB, linked to this tab by otria.invoice.session.v1, for up to one hour so it can be reused after sign-in. It is cleared after successful attachment, sign-out, removal or restarting the analysis. Expired files are deleted when Otria is open or next visited; a closed browser cannot run deletion timers. The file is sent to Otria only when you consent to attach it to an assistance request, under that request’s existing 30-day retention policy.

Consent banner

Only storage needed for a service or preference you request is enabled, so an optional-cookie consent banner is not shown. Optional Watch and marketing consent are separate from cookie settings. If non-essential storage is introduced, it will stay off until you make the required choice.

Browser controls

You can remove cookies and local/session storage through your browser’s site-data controls. Signing out ends the local sign-in session; “Start again” clears comparison progress and temporary supply details. Clearing all Otria site data also removes unused sign-in continuation entries. Blocking necessary storage can prevent sign-in, saving progress or returning to your selected offer. Supplier websites have their own cookies and privacy choices.

Future changes

If analytics, marketing cookies, third-party embeds or other non-essential storage are added, OTRIA will update this notice and provide the required consent controls before activation.

Contact

For privacy questions, contact founders@otria.es. See the Privacy notice for more information about personal data.