TrackedQR

Privacy

This page says what we keep about two groups of people: our customers, and the people who scan our customers' codes. We keep as little as we can.

Last changed on 13 November 2026.

Who we are

TrackedQR is run by [LEGAL NAME], [REGISTERED ADDRESS] (company number [COMPANY NUMBER]). Write to us at [CONTACT EMAIL] about anything on this page.

People who scan a code

When someone scans a changeable code, we record one scan with:

  • the time
  • the country, region and town, which Cloudflare works out from the connection (not a street address)
  • the kind of device (phone, tablet or computer), its system and its browser, from the name the browser sends
  • whether it is the first scan from that phone on that day, or a repeat
  • whether it came from the code or from its short link

We do not keep IP addresses, the full name the browser sends, or any cookie. We cannot tell who scanned a code, and we cannot follow a person from one code to another.

To tell a first scan from a repeat, we make a one-way code (a hash) of the IP address, the browser name, the code and a secret that changes each day. It is kept for 24 hours only, and never with the scan.

The business that made the code sees these counts. Single scans are kept for 25 months; after that only the daily totals stay, and they hold nothing about a person.

People who use a code's page

  • A feedback form keeps the stars and the comment you write, with the time. We do not ask for your name. Do not write personal details in the comment.
  • A video page from YouTube or Vimeo loads their privacy player. When you press play, their rules apply.
  • "Report this code" keeps the reason you write, with the time, so we can check the code. Once we have dealt with a report, it is deleted 2 years after it was made.

People who use the free code maker

Our free API makes a fixed code from a text or a link. To give each connection its free amount a day, we keep a count under a one-way code (a hash) of the IP address, made with a secret that changes each day, never the address itself. The count and the secret are deleted after 2 days. We do not keep the text or link of the code.

Our customers

  • Your email address, to sign you in and to send you the emails you ask for (sign-in links, link alerts, reports, trial reminders).
  • Your workspace, your codes, their content and design, your templates and the files you upload.
  • Your plan's state. Paddle, our payment partner, takes the payment and keeps the card details; we never see them.
  • A record of sign-ins for 30 days, so you stay signed in.
  • The API keys you make and the apps you connect, like Claude or ChatGPT: their names, when they were last used, and a one-way code (a hash) of each key and token, never the key or token itself.

We keep these while you have an account. When you delete your account on the account page, we delete them, apart from what the law tells us to keep for tax.

Who else handles the data

  • Cloudflare runs our servers, our database and our email, and checks some forms for bots (Turnstile).
  • Paddle sells our plans as the merchant of record, so it handles payments, receipts and VAT.
  • Google Web Risk checks the links in our customers' codes against a list of unsafe sites. Only the link is sent.

Why we may use the data

For customers: to give you the service you pay for (a contract). For scans: the business that made a code has a fair reason to count its scans, and we do that for them, in the small way this page says. For safety checks and reports: to keep people safe from unsafe codes (a fair reason of our own).

Your rights

You can ask us for a copy of your data, ask us to correct it or delete it, and object to its use. Write to [CONTACT EMAIL]. If you are not happy with our answer, you can complain to the Information Commissioner's Office (ico.org.uk).