R7Check

Privacy

What we collect, and what we never do with it.

Last updated — 1 September 2026

In plain language

The public product pages set no cookies and use no local storage. An analytics session exists only in the browser tab’s memory and disappears when the tab closes. The cabinet uses one strictly necessary session cookie to keep you signed in, which needs no consent under any regime.

We record which country and city a scan came from, derived from the visitor’s IP address — never the raw address itself.

The exact method (a salted hash with a rotating salt, or truncation) is flagged for engineering to confirm before this line ships — a bare "hashed" claim isn’t precise enough to be defensible on its own.

What we collect

If you have an account. Your email address, your name if you give one, the interface language you choose, and a password stored only as an argon2id hash — the plaintext is never written down and cannot be recovered from what we hold. If you sign in with Google we receive your email address and name from Google, nothing else. We also keep which brands you belong to and your role in each.

When somebody scans a code. The country and city the request came from, the kind of device, its operating system and language, the page that referred it, and the moment it happened. We do not store the IP address: it is combined with a secret key, hashed with SHA-256, and truncated, so the result cannot be reversed into an address and cannot be matched against a hash computed by anyone else.

What a page does after it opens. Whether it was scrolled halfway or to the end, whether a video was started or watched through, whether a certificate was opened, whether a call to action was pressed. Each belongs to a session identifier that exists in the browser tab’s memory and is gone when the tab closes — it is never written to a cookie, to local storage, or to any device.

None of this identifies a shopper, and none of it is combined with anything that would.

What a brand publishes itself

Certificates, photographs, factory video, ingredient lists and product copy are the brand’s own content. The brand decides what goes on the page, and the brand is responsible for it being accurate and for holding the rights to publish it. We store and serve that content; we do not check it, and we make no claim about whether a document says what the brand says it says.

Where such content contains personal data — a name on a certificate, a face in a photograph — the brand is the controller of it and we are its processor. If you are named in something a brand published, ask the brand first; their contact details are on the page itself.

Processors we use

Hetzner Online GmbH (Germany) hosts the application and the database. Cloudflare stores and delivers images, video and certificate documents; the bucket holding certificates was created under Cloudflare’s European Union jurisdiction, so those files stay in the EU. Google Ireland Ltd delivers the email we send you — sign-in links, password resets and billing notices. Stripe Payments Europe Ltd handles payment: card details go to Stripe directly and never reach our servers.

Each of these is a processor acting on our instructions under a data processing agreement. We do not sell data, and we do not share it for advertising.

Retention periods

Individual scan and page events: twelve months. A scheduled job deletes them past that, automatically. What survives is the daily totals — how many scans a code got on a given day, from which country, on which kind of device — and those carry nothing about any one visitor.

Daily totals: for as long as the account exists. They are small, and a brand asking how last spring went should not be told the answer was thrown away.

Account and brand records: until the account is deleted, then removed within 30 days. Published pages go offline immediately on deletion.

Invoices and billing records: as long as tax law requires — in Poland, five years from the end of the year the invoice was issued. This is an obligation we cannot waive on request.

How to make a data request

Write to info@r7check.com. Under the GDPR you may ask for a copy of what we hold about you, ask us to correct it, ask us to delete it, ask us to restrict how we use it, object to a particular use, or ask for it in a portable form. We answer within one month; if a request is complex we may take two more, and we will say so before the first month is out.

We do not charge for this, and we do not require a reason. If you are unhappy with how we handled a request you can complain to your national supervisory authority — in Poland that is the President of the Personal Data Protection Office (UODO).

One thing we cannot do: shopper analytics carries nothing that identifies a person, so we have no way to find “your” scans among them, and no way to delete them individually. That is a consequence of not collecting the data in the first place.