Skip to content

Privacy policy

Last updated:

This English version is a translation provided for information only. The Spanish version is the one that applies, and it prevails if the two differ: read it in Spanish.

This policy explains how personal data is processed in this application. This text is for information purposes and is not legal advice.

Data controller

Jaime Marín Romero. Contact email: contacto@quehaydetras.es. Further identifying details will only be added if they are legally required.

Public use without an account

To scan or look up a product you don't need to register and no personal profile is created. The scan history is stored only on your device (the browser's local storage) and photos of the barcode are processed in the browser, without being uploaded or stored.

The only exception: if you look up a code that is not in our catalogue, the application asks an external source for the product's name and brand. To prevent abuse of that lookup, the server calculates a value derived from your IP address with a secret key known only to the server and uses it as the key of some lookup counters, which are stored in the database and deleted in a daily purge once their period has expired (in practice, up to about 48 hours). Your IP is not stored in clear or linked to any other data of yours. That derived value is pseudonymised information, not anonymous. Legal basis: the controller's legitimate interest in protecting the service.

As with any web service, to respond to each request the hosting provider (Vercel) processes the IP address of the connection and other technical data of the request (for example, the address visited, the date and the browser), which may remain in its technical records (logs). How long those records are kept depends on the provider.

We also count visits with Vercel Web Analytics, without cookies and without storing anything on your device: the page visited, the referring page, the approximate country and the type of browser, operating system and device, grouped with an identifier that Vercel calculates from the request and renews every day. Your IP isn't stored and we only see aggregate figures. Legal basis: the controller's legitimate interest in knowing which parts of the service are used, in order to improve it. More detail in the cookie policy.

We also keep our own count of what is done, without anyone's data: how many product pages are looked up each day, how many we don't have, how many times “Let me know when it's verified” is pressed, how many accounts are requested and created, and how many visits come from an advert (from the campaign tag in the link, which is removed as soon as the visit arrives). Of the barcodes looked up that we don't have, we only store the code and when it was requested, to know which product pages to make. The IP, the browser and who did each thing aren't stored, and nothing is left on your device. Legal basis: the controller's legitimate interest in knowing what works and what is missing.

If, on the page of a product with no origin, you tell us what the label says, we only store the barcode, the text you write, the country if you choose one and the date: no account, no email, no IP. We ask you not to write personal data. To prevent abuse, submissions are limited per connection with the same pseudonymised counters described above. Only the administrators see it, and they review it before publishing anything; it is deleted when it is reviewed and, if nobody reviews it, after 90 days. Legal basis: the controller's legitimate interest in completing the product information.

Reader account

Anyone can create a reader account, free of charge and without waiting for approval, to follow products and get a notice when we verify where they come from. You must be at least 16 years old. To create it you give us your email and accept its terms; we send you a link to confirm it and choose your password. Until you open it, we store your email, an encrypted summary (hash) of the link's code (never the code itself), the version of the terms you accepted, the language of the page where you asked for it and, if you pressed “Let me know when it's verified” on a product page, that product's barcode. It is deleted in the daily purge after 24 hours (in practice, up to about 48 hours), whether you open it or not. The account is only created when you open the link, and the password is stored encrypted by the authentication provider (Supabase).

One email address is one account. A contributor account already includes everything a reader account has (following products, lists and notices), and if a reader becomes a contributor, it is the same account. If you request an account with an email that already has one, no other account is created and nothing is stored: we write to that email to tell you how to sign in.

With the account we process: your email; the sign-up and last sign-in dates, recorded by Supabase; the products you follow (their barcode, since when and whether we have already notified you); the lists you create (their name and the products you save in them); your email notice preference; the language we write to you in (that of the page where you asked for the account); the record of the terms you accepted (version and date); and the record of notices sent described in Weekly summary and email notices. What you follow and your lists are private: only you see them. The administrators see your email and that the account is a reader account. To prevent abuse, sign-up requests are limited per connection and per email with the same pseudonymised counters as password recovery: with a secret server key, without storing the IP or the email in clear.

Legal basis: performance of the relationship you start when you create the account (providing the service you ask for). Retention: while the account exists. You can delete it from My account; what you follow, your preferences and the notice record are deleted with it. If you also want to suggest products, take the Academy courses with their exams or take part in the Community, you can apply to be a contributor.

Contributor applications (before an account is created)

To apply to be a contributor you must be at least 16 years old. If you apply for contributor access through the public form (/unirse), the following data, which you provide voluntarily, is processed:

  • email address;
  • province and town;
  • the version of the contribution terms you accept and the date of acceptance, which is the moment you confirm your email address;
  • once registered, the date of the application, its status (pending, approved or rejected) and the date your email was verified;
  • minimal technical information to prevent abuse of the form (submission limits per IP address) and, if the geographic check is enabled, an approximate signal of the connection's country (see below).

Purposes: processing and assessing your application, checking that whoever sends it controls the email address given, preventing abuse of the form, detecting possible inconsistencies between the approximate location of the connection and the Spanish details declared (only as a signal for the manual review), managing your account and letting you know if the application is approved, and keeping a record of the decision (who reviewed it and when).

The application may be rejected: sending it doesn't guarantee access. The review is manual. Only authorised administrative staff can access the applications; they aren't visible to other users or to the public. This data isn't used for advertising purposes and isn't sold or passed on to third parties for that purpose.

IP address: to limit abusive submissions, the server calculates a value derived from your IP address with a secret key known only to the server, which is used as the key of some submission-limit counters. Your IP is not stored in clear, and that value is not stored in your application or in the email verification record. The counters that include that value are stored in the database and deleted in a daily purge once their period has expired (in practice, up to about 48 hours; this isn't a guaranteed exact period). When the verification link is confirmed, a further per-IP limit is also applied, which is only kept temporarily in the server's memory. Any data derived from an IP should be considered pseudonymised technical information (potentially re-identifiable), not anonymous.

Geographic check of the connection: it is currently disabled: no signal is calculated and no country is stored. If an administrator enabled it, when you send the form an approximate estimate of the country your device connects from would be used, calculated by our hosting provider from the connection's IP address. It would be compared with the fact that the province chosen is Spanish, to detect possible inconsistencies. It is only a signal for the manual review: it doesn't block the application, isn't used for automated decisions and doesn't presume bad intent. The estimate may not be accurate: using a VPN, a proxy, roaming, company networks or other factors can produce incorrect results. Your IP is not stored in the application: what is stored is a signal (compatible, not matching or undetermined) and, where there is one, the estimated country (two-letter code). Until you confirm your email they are stored in the verification record and deleted with it; when you confirm it they are copied to the application and kept while the application exists.

Legal basis: management of the application and prevention of abuse (the controller's legitimate interest and/or steps prior to a possible contribution relationship).

Retention: rejected applications are deleted automatically once more than 30 days have passed since the rejection; the deletion is carried out in a daily task, so it may take about one more day. Applications pending review aren't deleted automatically. Approved applications are kept as a record of the application and of the contribution terms you accepted (including the authorisation to publish your contributions): while your contributor account exists and up to 5 years afterwards, which is the limitation period for personal actions (Article 1964 of the Spanish Civil Code). After that period they are deleted. An administrator can delete an application at any time. The email verification records are kept as described below.

Email verification for applications

The application isn't registered until you confirm your email address. When you send the form, we send you an email with a personal link that is valid for 60 minutes and can only be used once. Opening the link doesn't confirm anything on its own: confirmation happens when you press “Confirm my email”, which is when you choose your password. Until you confirm, the form doesn't create any account. When you confirm, your account is created with our authentication provider (Supabase), with the password stored encrypted, but locked: you can't sign in and don't have contributor permissions until an administrator approves the application. If it is approved, it is unlocked and we let you know by email (through Resend, without any sign-in link); if the application is rejected or deleted, the account is deleted.

While the confirmation is pending, a verification record is temporarily stored with: your email address (as you wrote it and in a normalised form to avoid duplicates); the province and the town; the version of the terms you ticked in the form and the date you ticked them; the language of the page, to write to you in it; a value derived from the link (a one-way cryptographic summary) that allows it to be checked without storing the link or its code; the dates on which the record was created, the link expires and the last email was sent; the number of emails sent; and, if the geographic check is enabled, the signal and the approximate country of the connection for the last email.

If you ask for another email, the previous link stops working and the record is updated with the details of that new email. Up to 3 emails can be sent per record, with a minimum wait between them, within a window of 24 hours counted from its creation; when that window ends, a new request starts the count again. It isn't a rolling window of 24 hours.

When you confirm the email, the verification record is deleted and your application is registered with the verification date; that same moment is recorded as the date on which you accepted the terms. If you don't confirm it, the record is deleted automatically once more than 24 hours have passed since its creation and the link has expired. That deletion is carried out in a daily task (and also when the form is used), so it may take up to about 48 hours from its creation. This isn't a guaranteed exact period.

The verification email is sent through an external provider (Resend); see what data it receives in the Providers section.

Legal basis for the verification: checking that the email address belongs to whoever is applying to contribute and preventing applications in the name of third parties, as part of managing the application (the controller's legitimate interest and/or steps prior to a possible contribution relationship).

Contributor and administrator data

For contributor and administrator accounts, the following is processed:

  • email address;
  • name, if provided;
  • the language we write to you in (that of the page where you applied to contribute);
  • authentication credentials (the password is managed and stored encrypted by the authentication provider, Supabase);
  • user identifier and authorship of changes (user_id, created_by, updated_by, verified_by) and dates, to keep the history of changes traceable;
  • the data of your PRO programme: the record of your PRO points (which product and which part of its page each point comes from, the date from which it counts, whether it has been used to earn or renew PRO and, if the administrators revoke one, the date and the reason); the PRO periods you earn with them; if the administrators grant it, free PRO, with the date it was granted, the date it ends and the reason the administrators record; and your balance of dish viewings (see Dish photos). The administrators can see this record; in your panel you see your points and your PRO, and you can ask for a copy of all of it (see Rights). It is deleted when you delete your account (the entry in the record of free PRO grants remains, without your identifier);
  • technical records (logs), which may include the IP address, generated by the hosting and database providers;
  • usage counters linked to your user identifier, which limit the number of product data lookups from external sources (per minute and per day). They are deleted in a daily purge once their period has expired (in practice, up to about 48 hours; this isn't a guaranteed exact period);
  • the invitation, account creation and confirmation dates, and the date of the last sign-in, recorded by the authentication provider (Supabase);
  • the status of the invitation and of the account (pending, accepted, used, revoked or deactivated), calculated from those dates and from the account's permissions;
  • activity indicators calculated from the contributions (number and status of the proposals, products contributed and date of the last contribution) and from the last sign-in, with reference periods of 7 and 30 days.

The account status and the activity indicators are calculated on the server and only administrators see them, for the purpose of managing the contributions (following up invitations, accounts and contributions). For this, browsing, scans, location and device are not recorded. Legal basis: the controller's legitimate interest in managing the contributions.

Evidence photos (contributors)

Contributors can provide photos of a product in the catalogue (its barcode, the label where the origin or the nutrition table can be read, or the pack) as evidence of its data. With each photo we process: the image; an identifier of the evidence; the product it refers to; the date; the account that sent it; what it shows; the optional note you write and, if you send it with a correction of the product page or with its label nutrition, which proposal it goes with.

Purpose: to review it internally in order to check the origin and the reliability of the information provided. If it goes with a correction or with a label nutrition, its acceptance is also what makes that proposal earn its PRO points (see Dish photos, below, for the viewings they give). The photo is not published on the product page, does not verify or accept the product page on its own and is not used for anything else.

Who can see it: only the person who sent it and the authorised administrators. It is kept in a private storage area of our database and storage provider (Supabase), in the European Union (Ireland, region eu-west-1), with no direct access: the application (hosted on Vercel) only serves it to those people, after checking who is asking.

Metadata: before storing it we remove the camera data that comes with the file, including the location. This does not remove what can be seen in the image: that is why we ask you to photograph only the product, without people, documents, payment details or other personal data.

Retention: each evidence photo is deleted, at the latest, one month after it is sent (the same day of the following month), whatever its status: awaiting review, accepted as evidence, rejected or withdrawn. Accepting it does not extend that period. If it is rejected, you withdraw it or your account or the product is deleted, it stops being available at that moment, and its final deletion takes place within the same period.

Deleting it means removing the photo from storage, from the internal bin and from its backup, if it has one, and also deleting the note you wrote and the digital fingerprint of the image. A daily automatic task does this, starting a few days before the month is up so that it can be repeated if something fails; if even so it is not completed in time, an alert is raised so that it can be resolved.

Afterwards only a minimal record of the review is kept, like the rest of the change history: which account sent it, for which product, what type of photo it was, the dates, the status, the reason, when it was deleted and, if you sent it with a proposal, which one it went with (so that the proposal keeps counting in your PRO programme). It cannot be used to rebuild the photo. Database backups do not contain the photos, but those made before it was deleted may contain the full record, note and fingerprint included, until they are deleted after 30 days (see Retention); if one of those backups ever had to be restored, the notes and fingerprints of photos already deleted or expired are not recovered.

Photos on product pages: evidence photos are never published. The product photo published on its page is a separate category, with its own notice and an express authorisation when sending it: see Product page photos, below.

Legal basis: the performance of the contributor contract (the terms you accept when joining): providing evidence is part of contributing, and reviewing it is how we check what you provide. You can withdraw yours at any time.

Your rights: you can withdraw your pending photos from the product page and, from there, ask for accepted ones to be withdrawn. If you are no longer a contributor, or for any other right (access, erasure, objection…), write to the controller's email address given at the beginning (contacto@quehaydetras.es). You can also complain to the Spanish Data Protection Agency (AEPD).

Weekly summary and email notices

If you have an account, we send you one summary a week at most, and only when there is something to tell you: the products you follow that have been verified since you started following them (with their name and what we know about their origin) and, if you are a contributor, the proposals (about the origin or the label's nutrition information) that have been approved or rejected since the last summary (with the product name and, for rejected ones, the reason the administrators wrote) and, about your PRO programme, that you are short of points to renew it or that it is about to expire.

In addition, important notices don't wait for the summary: those about your account (confirming your email, creating a new password or that your application has been accepted) are sent when you ask for them or when it happens, and, if you are a contributor, those about your PRO programme are sent when each thing happens, each in its own email: that you have earned PRO with your contributions (also if you earn it while you have free PRO, with the date it will start), that it has been renewed, that you have got it back, that the administrators have given you free PRO (with its dates) and that your PRO has ended (this last one, in the nightly check, because it ends at a set time rather than because of something done). If one isn't sent, it is retried that night. For all this, your email, what you follow, your proposals and their status, your PRO points and the dates of your PRO period and of your free PRO are used.

To avoid repeating notices, a record of what has been sent is kept (your user identifier, the type of notice, its reference, which is the date of the summary or of the PRO period or the code of the product verified, and when it was sent) and, for each notice about your PRO programme, its type and its reference (the period, the grant or the date your PRO ended), its result (pending, sent, failed or skipped, for example if you have turned notices off), the number of sending attempts and when it was sent. It is only used by the server that sends the emails (the daily task and, for PRO notices, also at the moment they happen); nobody else sees it in the application. It is deleted when the account is deleted.

You can turn them off (the summary and the notices about your PRO programme) whenever you like in “My profile → Email notices” (contributors) or in My account (readers), or from the email itself: each one has the Unsubscribe button at the bottom, which doesn't require signing in (the link is signed for your account and only works for that), and your email program may also offer you one-click unsubscribe. The emails don't contain images or external resources, and we don't measure whether they are opened or which links are clicked. Legal basis: the controller's legitimate interest (informing you about what you asked to follow, the outcome of your contributions and your PRO programme), with your right to object by turning them off.

Contributors' personal data (lists and favourites)

Contributor accounts have a personal area. The lists (including the favourites list) are linked to your user identifier and are private: only you can see and manage them. They aren't shown to other contributors or shared between accounts. They are deleted when the account is deleted.

The nutrition information shown on the product page comes from Open Food Facts (ODbL licence) and is looked up on the server from the barcode; it doesn't involve sending personal data to that service.

Product page photos (contributors)

Contributors can send photos of the pack for the public page of a product in the catalogue: the front and, since 8 November 2026, the back, with its label, and, only if the nutrition table is somewhere else on the pack, one of the table. All of them are stored and published on the same page. With each one we process: the image, the product, the date, the account that sent it and when it authorised its publication. Before storing it we remove the camera data that comes with the file, including the location; that does not remove what can be seen in the image, so we ask that it shows only the product, without people, documents or other personal data.

Purpose and legal basis: showing the product on its page. The basis is the performance of the contributor contract: by sending it, ticking the box, you grant us the licence of use described in the terms (free and for any use; you remain its author). Until the administrators approve it, only the sender and the administrators can see it; once approved, anyone can see it on the page and it may appear in search engines. We never use Open Food Facts photos on product pages.

Retention: the approved one is kept for as long as it is part of the page, with a backup in private storage at the same provider (Supabase, in Ireland). If it is rejected, withdrawn or replaced by another one, it is deleted at once, together with its backup, and only a record of the submission remains (the account, the product, the dates and the status). If you delete your account, your pending photos are deleted and the published one stays on the page, with none of your details on view. You can withdraw yours while it is waiting for review; if any personal data of yours can be seen in a published one, write to the controller's email and we will withdraw it.

Reading with artificial intelligence (since 8 November 2026): the administrators may run the photos of a product page, yours included, through an artificial intelligence service (see Providers) to read the data on the label (the origin, the companies, the nutrition table, the ingredients and the other product details). Only the image is sent, already without the camera data; never your name, your email or your account. A person always reviews what is read before it is saved. The photo stays stored and published on the page, as explained above; reading it makes no other copy. For each reading we keep a minimal record (date, purpose, which administrator asked for it, the service and its usage), without the photo or what was read, and it is deleted after 13 months. The basis is the same as for the photo: the contributor contract (terms 1.11).

Dish photos (PRO contributors)

Since 9 November 2026, anyone with PRO can run the photo of a dish through an artificial intelligence service (see Providers) to estimate which foods are on it and how many grams; the nutritional values come from a public table (USDA FoodData Central), not from the AI. The photo is reduced in your browser and the camera data is removed; only the image is sent to the service, never your name, your email or your account. It is not kept anywhere (not in the database, the records or the backups): it is read and discarded. That is why we ask that no people or other personal data appear in it.

For each reading we keep a minimal record (date, purpose, which account asked for it, the service, the result and its usage), without the photo or what was read, and it is deleted after 13 months. And, to keep your balance of dish viewings, a record linked to your user identifier: each viewing you earn with a PRO point (which product and which part of its page it comes from), each one you use when reading a dish (and whether that reading worked), each one given back to you if the reading fails and, if the administrators revoke the point that gave it, the one withdrawn if you had not used it yet, with its date. Only you and the administrators can see it; it is kept while you have your account, even if you lose PRO, and it is deleted when you delete it. The basis is the contributor contract (terms 1.12).

Academy and Community (contributors)

Reading the Academy and the Community is free and doesn't require an account. The participation features are only for contributors and also process the following data, always because you decide to use them:

  • Progress in the Academy: the courses you make progress in, the lessons you mark as read (with their date) and your exam attempts (answers, mark and date). You and the administrators see them; nobody else.
  • Completion records: when you pass the final exam, a record that you have completed the course is issued, with a verification code (it isn't a qualification or an accreditation). It has its own page that only those who have its link can see (it doesn't appear in search engines or listings) and that shows the name, the course, the mark and the date.
  • First name and surname for the completion records: they are optional and only requested if you want a completion record. They are used only to print them on your completion records and on their verification page. They aren't shown on your profile, in the Community or anywhere else. You can change or delete them in “My profile”; without them, your completion records are no longer shown. Legal basis: your consent, which you withdraw by deleting them.
  • Community: the questions and answers you publish are public and may appear in search engines. They are shown with the avatar you choose (a character from the catalogue, never a photo) and as «Colaborador» (Contributor) or «Equipo» (Team); never with your name or your email. Your votes are counted without showing who voted. The reports you send are only seen by the administrators. What is moderated is hidden from the public, but kept with the reason for the moderation. You can edit and withdraw what you publish: what is edited is marked as edited, and what is withdrawn is no longer visible and is kept hidden, like what is moderated. A question that already has answers from other people isn't withdrawn (so that they don't disappear): you can edit it or ask us to withdraw it. If you want us to delete completely something you withdrew, write to us.

Legal basis for the above, except the name for the completion records: performance of the contribution relationship (providing the service you use). Retention: while your account exists. When you delete it, your progress, your exams and completion records, your name for the completion records, your avatar, your votes and your reports are deleted. What you published in the Community (questions and answers) stays published as «Cuenta eliminada» (Deleted account), without your avatar or anything that identifies you, so that the answers other people gave to your questions don't disappear. If you also want us to withdraw the text of any post, write to us saying which one, before or after deleting the account. Backups may contain your data for their retention period (see Retention).

Purposes

  • providing the product lookup service;
  • verifying that whoever applies to contribute controls the email address given;
  • managing contributor accounts and their contributions;
  • managing the contributions administratively (invitations, account status and contributor activity);
  • keeping the information traceable and intact (who entered or checked each piece of data and when);
  • providing the Academy (progress, exams and completion records) and the Community (questions, answers, votes, reports and their moderation) to contributors;
  • informing contributors of the outcome of their contributions and of their PRO programme (weekly summary and PRO programme notices by email, which they can turn off);
  • providing PRO contributors with the reading of a dish photo with artificial intelligence and keeping their balance of dish viewings;
  • providing the reader account: following products and giving notice when they are verified;
  • ensuring the security of the service.

Legal basis

  • managing the relationship with contributors and administrators: performance of that relationship and/or legitimate interest;
  • traceability of changes and security: the controller's legitimate interest;
  • inviting contributors by email: the data subject's consent when accepting the invitation;
  • verifying the email of the applications and managing the contributions administratively: the controller's legitimate interest and/or steps prior to the contribution relationship;
  • photos provided by contributors (evidence and product page photos): performance of the contribution relationship;
  • Academy and Community: performance of the contribution relationship; first name and surname for the completion records: consent;
  • reader account: performance of the relationship you start when you create it;
  • visit counting without cookies and our own count of what is done (without personal data): the controller's legitimate interest;
  • PRO programme (the record of points and their revocations, the PRO periods and free PRO): performance of the contribution relationship;
  • weekly summary and PRO programme notices by email to contributors: the controller's legitimate interest, with your right to object by turning them off in “My profile”.

For the public product lookup, the application doesn't ask for consent: it doesn't store personal data from that use in its database or use non-necessary cookies. The hosting provider's technical records are described in Public use without an account.

Retention

Account data is kept while the account is active. The history of changes is kept to ensure traceability, with no maximum period set. When an account is deleted, the direct references to its identifier in the products and in the history of changes are emptied; however, the copies of previous data that the history itself keeps and the backups may still contain that identifier, so anonymisation isn't guaranteed. The email verification records of the applications are deleted when they are confirmed or, if they aren't confirmed, within about 48 hours at most from their creation (see Email verification for applications). Contributor applications are kept as stated in their section, and evidence photos as stated in theirs (Evidence photos).

Backups: every day a backup of the whole database is made, which includes the account data (with the email address) and the applications to be a contributor (with the email, the province and the town). It is stored in private storage of the database provider (Supabase), not publicly accessible. In addition, a second copy is set up in private storage of the project's repository (GitHub); when it cannot be made, only the copies already made exist, and they are deleted in the same way. Each copy is deleted automatically once more than 30 days have passed since its creation (the most recent one is always kept); the deletion is carried out in the same daily task, so it may take about one more day. While a copy exists, it may contain data from accounts or applications that have already been deleted.

Providers (processors)

External services that process data on the controller's behalf to provide the service. They aren't part of the application's own database.

  • Supabase: database, authentication, storage and sending the invitation emails to contributors (through its authentication service).
  • Vercel: hosting the application, visit counting without cookies (Vercel Web Analytics, see Public use without an account) and, if the geographic check is enabled, the approximate estimate of the connection's country from the IP address.
  • Resend: sending the verification email for contributor applications. For each email it receives the recipient's email address; the content of the email (subject, text and HTML), which only includes the notice of the application, the verification link and its expiry (it doesn't include your province or your town); and a technical identifier of the email (linked to the verification record and to the email number) that prevents duplicate emails. It also sends the notice that an application has been accepted (without any sign-in link), the link to confirm a reader account sign-up (or, if that email already has an account, the notice of how to sign in), the weekly summary and the PRO programme notices described in Weekly summary and email notices (email, product names, rejection reasons, products verified and the dates and points of your PRO programme, with a technical identifier for each PRO notice that prevents sending it twice) and, when someone requests it in “Forgot your password?”, the email with a personal link to create a new password, single-use and valid for 60 minutes. That link is only sent to active accounts, and the page gives the same answer whether or not the email given has an account. Your IP isn't sent to it. In this flow it isn't used for advertising or tracking: the application doesn't enable open or click tracking. Resend may keep the content of the messages sent according to its service and configuration; how long it keeps them, the sending region and the applicable contractual safeguards are pending confirmation.
  • Groq: artificial intelligence service that reads the photos of a product page's label when the administrators ask for it (see Product page photos) and the photo of a dish sent by a PRO contributor (see Dish photos). It receives only the image, without the camera data, and no account data. It may keep or use what it receives under its terms; the contractual safeguards and the region of processing are pending confirmation.
  • GitHub: stores, in private storage of the project's repository, the second backup described in Retention (when it is made), which contains the whole database. Only whoever administers the repository has access, and each copy deletes itself after 30 days.

External sources of product data

Open Food Facts is an open product database (ODbL licence). It isn't a provider that processes personal data on the controller's behalf: the application only sends it the barcode (EAN), from the server, to complete commercial data and nutrition information, and doesn't send it personal data. Part of the product information may come from this source; the rest is entered and reviewed by the administrators and the authorised contributors.

International transfers

The database (Supabase) is hosted in the European Union (Ireland, region eu-west-1). The application hosting (Vercel), the sending of emails (Resend), reading labels and dishes with artificial intelligence (Groq) and the second backup (GitHub) may involve processing outside the European Economic Area, with the safeguards that each provider offers under the GDPR.

Rights

You can exercise the rights of access, rectification, erasure, objection, restriction and portability by writing to the controller's email given at the start of this policy. You will receive an answer within one month. If you have a reader account, you can delete it yourself in My account: the account, what you follow, your lists and your notices are deleted immediately (in the backups, within 30 days at most). Where processing is based on your consent (for example, the contributor account), you can withdraw it at any time, without affecting what was processed before. You can also lodge a complaint with the Spanish Data Protection Agency (AEPD).

No automated decisions producing legal effects on you are made and no profiles are built: the review of contributor applications is always manual.

Contact

For any privacy matter, contact the controller through the email given in the Data controller section.