Privacy policy

We store your email address, a hash of your password (never the password itself), your name and optional phone number, your display preferences, and your notification choices.

We store security events: sign-ins, failed sign-ins, password and two-factor changes, and changes to your QR codes. These are visible to you under Security history.

Uploaded files — logos, PDFs, images, audio and video — are stored on this server (or the operator’s object storage) and served to people who scan the related code.

For dynamic codes we record the scan so the owner can measure their campaign. That record contains: the time, the country, region and city reported by the operator’s proxy or CDN, your device type, browser and operating system, your browser’s preferred language, the referring host if any, and the UTM parameters on the link.

We do not store your IP address in a readable form. It is salted and hashed with a server-side secret, which lets us count unique visitors without being able to identify you or reverse the value.

We do not use cookies to track you across sites. A short-lived cookie is set only when you unlock a password-protected code, so you are not asked again on every scan.

Bot and crawler traffic is excluded from analytics rather than recorded.

A code owner may add Google Analytics 4, Google Tag Manager or a Meta Pixel to the pages QR ALTRIX hosts for them. Those tools are operated by those companies under their own policies, and they load only when the owner has configured an id.

Redirect-type codes do not inject any third-party script: they pass UTM parameters to the owner’s own site.

Scan records on this install are kept until the code owner resets the statistics or deletes the code. The administrator can set an automatic retention period.

Account data is kept until you delete your account. Deleting your account removes the workspaces you own, their QR codes, designs, uploads and scan history.

Password-reset and email-verification tokens are deleted once used or expired.

Members of a workspace see the codes and analytics in that workspace, according to their role.

A platform administrator for this install can see accounts, workspaces and codes in order to run the service and handle abuse reports.

Nothing is sold, and nothing is shared with advertisers. Outbound email goes through the SMTP provider the operator configured.

You can see and correct your own data in Settings, export analytics to CSV or XLSX, and delete your account at any time.

If you scanned a code and want the record removed, contact the operator of this install; because IPs are hashed, you will need to describe the scan (code, approximate time) so they can locate it.

Passwords are hashed with bcrypt. API keys are stored only as hashes. Sessions are signed, HTTP-only cookies. Uploads are type-checked and SVG files are sanitised before they are served.

Database queries go through a parameterised ORM, and every request body is schema-validated before it reaches the database.