Cookie notice
Optional usage analytics — updated 6 November 2026
If you allow analytics, Microsoft Clarity measures page visits, clicks, scrolling and comparison steps to help us understand where visitors stop. Recordings have their page contents masked. Account, admin, sign-in, replacement-link, identity, payment and document-download pages are excluded. We send only predefined step names, not invoice contents, filenames, answers, email addresses or account identifiers. Clarity receives technical information such as device, browser, page URL and a pseudonymous session identifier. URLs with unrecognised parameters are excluded.
Your choice is stored in otria_analytics_v1 for 180 days across otria.es and app.otria.es. Clarity is not loaded before permission or after rejection. When allowed, _clck and _clsk cookies associate visits and sessions. Advertising storage is denied. You can reject optional analytics or change your choice using Cookie settings at the bottom of public and comparison pages. This does not affect your comparison, account or Watch.
Microsoft processes Clarity data under its privacy statement, including international processing. See Microsoft’s information about cookies and retention. Existing cookieless public-page measurement by Vercel remains separate.
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
Comparison progress and selected-action handoffs can remain in this browser for up to 24 hours of application validity. A handoff may include the home label, address and CUPS needed for the action you chose. Expired records are removed when Otria next reads them; closing the browser does not run deletion timers. Locally extracted identity numbers, bank details and the invoice file are held temporarily in page memory for at most one hour while the page is active. This describes local retention, not a promise that invoice contents never leave the device: unresolved details can trigger transmission of page images and text to OpenAI, as explained in the privacy notice. Reloading or returning from sign-in may require you to select the invoice again. Temporary data is cleared after use, cancellation or logout. Legacy stored invoice files are removed when Otria next opens. Separate document-storage and supplier-application actions follow their stated authorization and retention rules.
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.
Contact
For privacy questions, contact founders@otria.es. See the Privacy notice for more information about personal data.