Onpack

Privacy

Onpack is free to use, and scan data is what pays for it. This page says exactly what a scan records, because a service funded that way should be plain about it.

What a scan records

When someone scans a code, Onpack writes one row containing four things:

Serialised codes additionally have their scan counted per serial, with the country and client kind, so that the same serial appearing in two distant places can be flagged as a likely copy.

What a scan does not record

Who sees it

A brand sees the counts for its own codes and nothing else. Onpack sees the whole set in aggregate. If a brand has configured a webhook, the scan is also sent to the address they chose, which is their system and their responsibility from that point.

Signing in

Accounts are handled by Clerk, which stores the email address or Google account used to sign in and sets a session cookie for the console. That cookie exists only on the console and never on a scanned product page.

What brands publish

A hosted product page contains whatever the brand wrote into it. Onpack does not add anything to it, and does not track the people who read it beyond the single scan row described above.

Removing data

Deleting a product removes its configuration. Scan rows are aggregate counts that are not tied to a person, so there is nothing in them to trace back to an individual. Write to hello@onpack.link with any question about this.

This page describes the behaviour of the running service. It was drafted from the implementation rather than by a lawyer, and it is not legal advice.