Data & privacy

What AuthPlus records, where it goes, and how long it stays. Read this before deploying the app to customers.

What a verification records

Every completed scan or transfer writes one permanent line to the audit trail:

Recorded	Detail	Visible to
What was scanned	The code, and the item it belongs to when it is recognised	The code’s owner, administrators
The result	Authentic, a warning, or the reason it failed	Same
When	Server timestamp	Same
Who	The verifier profile	Same
The device	A stable device identifier, plus manufacturer, model and operating system	Same
Where	Network address, resolved town or city, and precise coordinates when location is used	Same

Warning · Failed scans are recorded too

A scan of an unknown or counterfeit code records the same device and location details as a successful one. This is deliberate — it is how counterfeit clusters are detected — but it means people scanning invented codes leave a trace. Records for codes that do not exist are visible only to administrators.

Note · No personal identity is collected from consumers

A consumer using the app is never asked for a name, an email address or an account. They are represented by an automatically generated device profile. The device identifier is nonetheless persistent, so scans from one phone are linkable to each other.

How location is determined

Source	When used	Precision
Device location (GPS)	When the verifier type requires it, and permission is granted	Precise — the actual position of the scan
Network address	Otherwise	Approximate — typically the town or the internet provider’s location

Warning · Town names are resolved by an external service

To turn coordinates or a network address into a place name, the app calls a third-party geolocation service directly from the user’s device. The user’s network address — and, where a precise fix was obtained, their coordinates — are therefore disclosed to that service on every verification. This must be declared in your privacy notice and, depending on your jurisdiction, may require consent.

Files and documents

• Uploaded files — logos, product images, certified documents — are stored unchanged, in their original form. They are not resized or re-encoded, so any metadata they contain (including photograph location data) is preserved.
• Certified content is additionally fingerprinted, and that fingerprint is what verification compares.
• When you verify a file from your own device, the file is not uploaded — only its fingerprint is sent. Verifying a link is different: the server downloads the file to fingerprint it.

Warning · Stored files are readable by anyone with the address

So that images and certified documents load for verifiers without a login, files are served publicly to anyone who knows their address. The addresses are long and effectively unguessable, but they are not secret and do not expire. Do not upload anything you would not be prepared to publish, and strip metadata from photographs before uploading if that matters to you.

Retention, archiving and deletion

AuthPlus is built to preserve evidence. The audit trail, in particular, is never edited or removed by the application.

Record	Can be removed?
Operations (verifications and transfers)	No — permanent
Brands, products, assets, contents, items, issuances, codes	Archived only, never deleted
User accounts	Archived only
Warnings	Closed, not deleted
Verifier accounts	Archived only
Code types, print templates, verifier types	Archived only
Generated label documents	Yes — deleted along with the stored file
Prohibited-name entries	Yes

Only two things can be removed outright, and neither is a record of anything: a generated PDF or CSV, which you can produce again at any time, and an entry on the prohibited-name blocklist. Everything else is archived.

Records are otherwise kept indefinitely: AuthPlus applies no automatic retention limit, and there is no self-service account deletion. Erasure requests are handled manually by the platform operator.

What is stored on your device

Stored	Why
A device identifier	Identifies the automatic verifier profile so scan history is continuous.
Verifier profiles and the active one	So you do not re-enter credentials at every launch.
Sign-in tokens	Keeps you signed in to the dashboard.
Language, theme, and the administrator’s owner filter	Preferences, per device.

AuthPlus uses no analytics, no advertising and no tracking cookies, and loads no third-party fonts or scripts. The only external call made by the app is the location lookup described in How location is determined.

Removing a verifier profile in the app removes it from that device only; the account and its history remain on the server.

Getting your data out

Codes can be exported as CSV per issuance (Labels & exports), and label sheets as PDF. There is no bulk export of operations, catalogue or account data from the interface — an operator with database access can produce one on request.