Privacy & data

Your records stay under your control.

This page explains the current beta's data behavior in plain language. It describes what the software does today; it is not a substitute for the final operator privacy notice required before a paid public launch.

Last updated: 19 July 2026

The short version

No sign-in requiredYou can run product checks and keep records only in this browser.

Sync is your choiceSigned-in records are stored only when you save or deliberately sync them.

No advertising profilesThe beta does not sell your data or use it for behavioural advertising.

Built-in controlDownload or restore a workspace backup, or delete cloud records from the workspace.

What data is handled

WhenDataWhat happens

Using the app anonymouslyProduct-check answers, product records and reusable contact profilesKept in this browser’s local storage. They are not uploaded by the app.

Using the beta websiteA random browser identifier and one-time events such as visiting, starting or completing a check, saving or importing products, and signing inThe identifier is generated in your browser, hashed before storage and used only for aggregate validation counts. The app does not store your IP address, browser details or product-check answers with these events.

Sending optional feedbackMarketplace, catalogue-size range and your answer about what could prevent useStored without your name or email and linked only to the hashed random browser identifier. Do not include personal, customer or order details in the text answer.

Signing inEmail address and, when available, display name supplied by the active authentication providerUsed to show your session and keep cloud records separated from other users’ records.

Saving or syncingSaved product checks and manufacturer or responsible-person profilesStored in the signed-in workspace so they can be loaded on another device.

Saving an optional sourceA source URL and the date you record checking itStored with the manufacturer record as your own review note. EU Listing Check does not visit or verify the page.

Joining plan early accessYour signed-in email, selected plan, current product-family count and request timeUsed only to measure plan interest and plan the beta. It does not start a purchase or subscription.

Why the beta uses this data

To create the checklist, reports and marketplace preparation files you request.
To save and sync records when you choose the cloud workspace.
To keep optional source notes that you deliberately save with a manufacturer record.
To measure voluntary early-access interest in a planned paid plan.
To measure whether visitors use the core workflow and to review anonymous product feedback before deciding what to build next.

The beta does not currently send marketing email, run third-party advertising or sell personal information.

Storage, deletion and copies

Browser records

Browser-only product records remain on that device until you delete them in the workspace or clear the site’s browser storage. Signing out does not remove browser-only copies. The private operator scorecard can reset validation counts and exclude its current browser identifier from future counts. Clearing site storage replaces that identifier, so the operator should exclude the browser again after clearing site data.

Cloud records and account deletion

Signed-in records remain available until you delete individual records, use Delete cloud data, or delete the EU Listing Check account. Deleting cloud data keeps the sign-in account. Deleting the account removes the EU Listing Check authentication user and cloud records. Neither action removes browser-only copies on a device.

Your own copy

Use Download workspace backup to save the products and contact profiles currently visible to your browser as a JSON file. Restore backup validates that file and adds only missing items to the browser; it does not overwrite existing records or upload restored items automatically.

Service providers and technical data

EU Listing Check uses OpenAI-provided site hosting. Email-link and Google sign-in are provided through Supabase, which also stores account-owned cloud records. These services may process necessary technical information such as requests, authentication cookies, device or network information, and security logs under their applicable terms and policies.

Read OpenAI’s privacy policy

Read Supabase’s privacy policy

The app itself does not add advertising trackers. Authentication services may use cookies needed to keep a user signed in and secure the session.

Before paid public launch

A final privacy notice must identify the responsible operator and privacy contact, confirm processors and international-transfer arrangements, specify formal retention periods, and explain how people can exercise applicable data-protection rights. Until then, this is an accurate beta data overview—not a finished commercial privacy notice.

Official background

EU transparency rules require organizations collecting personal data to give clear information about who is responsible, purposes, legal basis, recipients, retention and individual rights.

General Data Protection Regulation ↗European Commission guidance ↗