Legal notice
Origen is provided by ZERTIDOX S.L., Spanish tax number B93867711, at Via Laietana 59, 08003 Barcelona, Spain. Registered with the Barcelona Mercantile Registry, sheet B-662228, first registration dated 12 August 2026.
General and privacy contact: info@zertidox.com.
Zertidox's published corporate data-protection and DPO contact channel is also info@zertidox.com.
Origen identifies products through barcodes, QR codes containing product identifiers, and name, brand or model searches. It consults Open Food Facts, Open Beauty Facts, Open Products Facts, Open Library and Wikidata. Text matches require checking that they refer to the product. Barcode prefixes, brand or author nationality, and publisher addresses are not used to infer the manufacturing country.
Third-party data and photographs retain their licences and attribution. Each record identifies and links to its source. Their availability does not grant rights over trademarks or other protected elements they contain.
Privacy and browser storage
Information used
Camera and photographs. Codes and label text are read in your browser. Origen does not upload scanner video or selected photographs to its server and does not recognise objects by their appearance. Text is read locally using Tesseract; its resources are downloaded from Origen hosting and may be stored in browser cache. You can review and edit the text before starting a search.
Lookups. The identifier, language and, when you choose a text search, the name, brand or model you confirm are sent to the Origen server and the queried catalogues. Search text is part of a URL and may appear in technical hosting and provider logs. Enter only the product information you wish to look up. Origen does not keep its own text-search history; technical logs follow the retention conditions described in this policy.
External images and links. Your browser requests product photographs directly from the source domains. Those providers may receive your browser's IP address and HTTP metadata. Opening an external link also subjects that visit to the destination site's terms.
History. History is initially disabled. Enabling it stores up to 40 records in this browser. Origen does not synchronise history through an account. Disabling it prevents new writes; existing records remain until you delete them, newer records replace them or the browser clears its data.
Sharing and contacting us. Sharing passes the product name, code or link to the service you choose through your device, or copies the link to your clipboard. Emailing support sends us your address and message. Avoid unnecessary information.
Android and iPhone apps. The Android app shows this same website inside the app and is governed by this policy without differences. The iPhone app reads the code with the phone's camera and the image never leaves the device. To look up a product it sends the code and language, or the text you type to search for it, to the Origen server, like the website, together with technical connection data (IP address, operating system and app version). Its history is stored only on the phone, up to 100 products, with no account or sync; you can delete it in the app or by uninstalling it. The app uses no advertising identifiers, does not track you across apps and includes no analytics or advertising SDK. Links to this website open in the system's built-in browser. Shopping lists in the iPhone app are stored only on the phone, with no account or sync. Origen Pro is an optional in-app purchase in the iPhone app handled by Apple through the App Store: Origen does not receive your payment details or identity; the app only asks Apple whether the purchase is active on your account.
Browser extension. When you click it, it reads the product barcode on the page you have open and sends it to the Origen server as a normal lookup, with the same technical data. It does not read other tabs or pages, keeps no history and uses no cookies or identifiers.
Usage measurement. Each lookup that gets an answer, and each product picked from a text search, adds one to a monthly counter, split by channel (web, Android or iPhone). The signal carries no product code, cookie or identifier, and the counter stores only monthly totals, deleted after 400 days. Like any request, it reaches the hosting provider with the technical metadata described above; Origen does not link that metadata to the counter.
Purposes and legal bases
Answer requests, display records, retain requested history, respond to communications and protect service availability and security.
The requested service and its support rely on GDPR Article 6(1)(b). You enable optional history through consent, Article 6(1)(a). Security and abuse prevention rely on the legitimate interest in keeping the service available, Article 6(1)(f). Data is minimised for that purpose: the shared counter does not identify visitors and is not used for advertising or profiling. Retention required by a legal obligation relies on Article 6(1)(c). Usage measurement helps us understand how much the service is used and decide how it evolves. It relies on Zertidox's legitimate interest, Article 6(1)(f); it identifies no one and stores nothing on your device.
The reviewed implementation includes no user accounts, advertising or analytics SDK; the only payment is the optional Origen Pro purchase in the iPhone app, handled by Apple. The usage measurement described is first-party and aggregated. Requests are not used to make decisions about people with legal or similarly significant effects.
Providers and retention
Vercel Inc. provides hosting and infrastructure. Its DPA applicable to the Pro plan governs processing as a processor; certain service or account data is processed under its own responsibility. Origen's function is configured in Paris, but Vercel and its subprocessors may process data in the United States and other countries. The DPA incorporates standard contractual clauses for the relevant transfers. You may request information and a copy of applicable safeguards through our privacy email.
Upstash Inc. provides Redis for request limiting and for the monthly usage counter. The rate-limit counter stores reservation timestamps and random identifiers only, without product codes, photographs, history or visitor IP addresses. Reservations stop counting after 60 seconds. The key expires after 61 seconds without new reservations; if a source cooldown applies, expiry is its remaining time plus 61 seconds, up to 361 seconds when set. These are active-key expiry periods, not a guarantee about every provider backup. The selected database is in Frankfurt with no read replicas. This location does not mean that all provider processing takes place exclusively within the EU. Its terms incorporate a DPA and transfer safeguards where applicable. The usage counter holds only monthly totals per channel, with no codes, IP addresses or identifiers, and each month expires after 400 days.
Open Food Facts, a French association, maintains Open Food Facts, Open Beauty Facts and Open Products Facts and acts as controller for its own services. It receives requests from our server; loading photographs sends HTTP data directly from your browser. Its policy states that visit logs containing IP addresses are retained for three years. See https://fr.openfoodfacts.org/privacy.
Additional sources. Open Library, an Internet Archive service, and Wikidata, a Wikimedia service, receive requests from the Origen server and operate under their own policies. They do not receive the label photograph from Origen. See https://openlibrary.org/privacy and https://foundation.wikimedia.org/wiki/Policy:Privacy_policy. Opening their external links connects your browser directly to those services.
Support email is received and stored with Proton AG, as confirmed by the controller. Its DPA governs its business service; the Mail privacy policy states storage in Switzerland, Germany or Norway, with backups retained for up to 30 days. Our own support-message retention is defined below; backup periods do not replace that criterion.
Local history has no automatic expiry. You can delete it in the application or clear browser site data.
Records are cached to reduce requests. Responses can be reused for five minutes in browser caches and 24 hours in server or shared caches, with an additional revalidation window. These are freshness settings, not verified physical-deletion deadlines.
Hosting runtime logs are retained for 30 days under the verified Observability Plus configuration. No log-export destinations are configured. That period does not describe every category of provider data.
Other provider access or security records are retained as needed to operate and protect their services and meet legal obligations; the 30-day runtime period does not automatically apply to every category. Origen configures no log exports and maintains no separate visitor or profiling database.
We will retain Origen support communications while handling the request and for a maximum of 12 months after closing it. Unnecessary information will be deleted earlier. If a legal obligation or a specific claim requires retaining particular data, only that data will be kept, with restricted access, for the period required for that purpose, documenting the reason and duration.
Cookies and browser technologies
The application uses local storage for history preferences and records, and resource caches for offline operation. Its service worker does not store API responses, although HTTP caching may apply.
The application installs no advertising or analytics cookies and includes no tracking SDK. Usage measurement uses no cookies or browser storage. History storage is enabled only when you request it. The private preview also uses Vercel's technical authentication under its terms. Image and hosting providers operate under their own policies; any new technology will be assessed before use, and prior consent will be requested where required.
Your rights
Where applicable, request access, correction, erasure, restriction, objection or portability at info@zertidox.com. You may withdraw consent without affecting earlier processing. You may complain to the Spanish Data Protection Agency or another competent authority.
The company cannot remotely delete history held only in your browser; you can delete it in the application.