Privacy Policy

Cabi is operated by EventBinder. This covers two different groups: the organisations who create QR codes and short links in the dashboard, and the members of the public who scan those codes. Most of what follows is about the second group, because they never chose to deal with us.

Scanning records that the scan happened, so the organisation that created the code can see how it performed. A scan record can include the code that was scanned, the time, an approximate country, whether the device was mobile, and the operating system family.

Scan records can also include an approximate region and city derived from your network, your network operator, the page that referred you, the destination you were sent to, technical details of the connection such as the data centre that served it and the HTTP protocol used, information derived from your browser's user-agent string, and an automated assessment of whether the request looks like a bot.

We do not ask for or record your name, email address or account. Scanning a code does not create an account and does not require one.

Your IP address is unavoidably visible to our servers when your device makes a request, in the same way it is to every website. What we do with it:

• New scan records store a one-way hash of the IP address, not the address itself. The hash is salted and the salt rotates daily, so the same address produces a different value on a different day.
• A small number of historical records created before this change still contain IP addresses in their original form.
• Our infrastructure provider retains request logs, which include IP addresses, for a short period as part of running and protecting the service.

We are spelling this out because “we never store IP addresses” would be easier to write and would not be true.

The first time you open a Cabi link, your browser generates a random identifier and stores it locally on your device. We convert it into a derived identifier and record that with your scans. It is not your name, and it is not shared across other companies' websites — but it is persistent, so repeat scans from the same browser can be recognised as the same device. Under data-protection law that counts as personal data, which is why it is stated here rather than buried.

Clearing your browser's site data for the link domain removes the stored identifier, and the next scan generates a new one.

We do not use browser fingerprinting — building an identifier from your device's characteristics — and we do not build advertising profiles from scans or sell scan data. A fingerprinting script previously used in this product has been retired and no longer runs.

Records created while that script was in use still exist and still contain the fingerprint data it collected. They are historical: nothing new is added to them.

Where a code sends you is chosen by the organisation that created it. Once you arrive, that destination is theirs, and its own privacy notice applies rather than this one.

For account holders we store what is needed to run the account: your username and email address, your organisation and role, your session, and any API keys you create. Passwords are stored only in hashed form (argon2), never in plain text. Server request logs are retained for operating the service.

The sign-in page loads Google's sign-in script from accounts.google.com for everyone who is not signed in, before you interact with anything — that is what puts the “Sign in with google.com” card on screen. Loading it means Google sees the request, including your IP address. It runs only on the sign-in page, never on a scanned link or anywhere inside the dashboard. If you sign in that way, Google tells us the account's identifier, email address, name and profile picture; we use the email address only to find your existing Cabi account and we do not create one from it.

We do not sell personal data. Scan data for a code is available to the organisation that created that code. We use infrastructure and email providers to run the service, and we may disclose data where the law requires it.

We do not currently operate an automated deletion schedule. In practice that means scan records and account data are retained indefinitely until deleted on request. We would rather state that plainly than publish a retention period we do not actually enforce; defining and implementing one is outstanding work.

Depending on where you live you may have the right to access, correct or delete personal data we hold about you, or to object to some processing. Scans are not linked to your name, so to act on a request about scan data we would generally need the per-device identifier described above — without it we may be unable to connect a request to particular records.

Contact hello@eventbinder.app.