Skip to content
BETA

Privacy Policy

Last updated November 12, 2026. See also our Terms of Service.

This policy explains what qrlaunch collects, from whom, and what we do with it. It covers two groups: people with an account, and people who scan a code made with qrlaunch.

The short version: static codes involve no data at all. Dynamic codes count scans using a hashed IP address, an approximate location and the type of device. We never store the IP address itself, and we do not sell anything.

1. Who is responsible

qrlaunch is operated by qrlaunch, based in Ontario, Canada. We are accountable for the personal information described here under Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA).

Questions, requests and complaints go to our privacy contact at privacy@qrlaunch.io.

2. Static codes made without an account

A static code is built in your browser. What you type into it, such as a link, a Wi-Fi password or contact details, is not sent to us and is not saved by us.

A static code points straight at its content. Scanning one does not pass through qrlaunch, so we record nothing about those scans.

3. Your account

When you create an account we keep:

  • Email address and name. To sign you in and to write to you about your account.
  • Password. Held by our sign-in provider, Amazon Cognito, in a form we cannot read.
  • What you create. Dynamic codes and their destinations, designs, campaigns, routing rules and any files you upload.
  • Plan and billing status. Your plan, renewal date and a customer reference from Stripe. Card details go directly to Stripe; we never see or store them.
  • Sign-in activity. When you last signed in.

Files you upload to use as a code’s destination can be opened by anyone who has the link or scans the code. Do not upload anything you would not publish.

4. What a scan records

A dynamic code sends the person scanning it through our redirect service on the way to its destination. Each scan records the following:

RecordedDetail
Which code, and whenThe code's short identifier, its owner and campaign, and the time of the scan.
A hashed IP addressThe IP address is turned into a keyed one-way hash before anything is saved. The address itself is never stored. The hash lets us count the same device once per day.
Approximate locationCountry, region and city, estimated from the IP address by our content delivery network. No GPS, street address or postal code.
DeviceThe browser's user-agent text (up to 512 characters) and what we read from it: phone, tablet or desktop; operating system; browser.
Referring pageThe address of the page that linked to the code, if the browser sends one.
Automation flagWhether the request looks like a bot or link checker, so it can be left out of the counts.
Destination chosenIf the code uses routing rules or an A/B test, which rule or version was used.

The browser’s language setting is read to choose a destination when the code’s owner has set a language rule. It is not saved.

We do not record the scanning person’s name, email address, phone number or precise location, and we do not try to work out who they are.

The owner of a code sees totals only: scans and unique devices per day, and breakdowns by country, city, device type, operating system and hour. They never see an individual scan, a hashed IP address or a user-agent.

Individual scan records are deleted after 90 days. The daily totals built from them contain no information about any one person and are kept for as long as the code exists.

5. Cookies

  • Sign-in cookie. Keeps you signed in to your account. Required; set only when you sign in.
  • Scan cookie (__Host-qr_visitor). Set on a scanning person’s device only when the code is running an A/B test, so the same person keeps seeing the same version and a completed action can be credited to it. It holds a random identifier, lasts 30 days and is not used on any other site.
  • Google Analytics. On our own website (not on scans) we use Google Analytics to see how the site is used, for example which code types people choose and download. It never receives the content of a code. You can block it with your browser’s settings or Google’s opt-out add-on.

6. Why we use this information

  • To run the service: sign you in, send scans to the right place, and show you your results.
  • To take payment and apply the limits of your plan.
  • To keep the service safe: detect abuse, automated traffic and harmful destinations.
  • To understand which parts of the product are used, so we can improve it.

We do not sell personal information, and we do not use scan data for advertising or share it with advertisers.

7. Where it is stored and who helps us

Accounts, codes, uploads and scan records are stored with Amazon Web Services in its Canada (Central) region, in Montréal.

Some companies process information for us, and some of that happens outside Canada, where it may be subject to the laws of those countries:

  • Amazon Web Services. Hosting and storage in Canada. Its worldwide delivery network receives each request at the location nearest the person and passes it on to Canada.
  • Stripe. Payments, invoices and card details.
  • Google. Website analytics, as described under Cookies.
  • Vercel. Serves this website and your dashboard.

We also disclose information when the law requires it, or to a successor if the business is sold, under the same commitments made here.

8. How long we keep it

  • Individual scan records: 90 days.
  • Daily scan totals: for as long as the code exists.
  • Account, codes and uploads: until you delete them or ask us to close your account.
  • Billing records: as long as tax and accounting law requires.

Deleting a code stops it redirecting for good. To close your account and have its contents removed, write to privacy@qrlaunch.io.

9. How we protect it

Information is encrypted in transit and at rest. IP addresses are hashed before storage. Access to production systems is limited to the people who operate the service and is logged. No system is perfectly secure; if a breach creates a real risk of significant harm, we will tell the people affected and the Privacy Commissioner of Canada.

10. Your choices and rights

You can ask to see the personal information we hold about you, have it corrected, withdraw consent, or have your account closed. Write to privacy@qrlaunch.io and we will answer within 30 days.

If you scanned a code and have a question about it, you can write to us as well. Because we store a hash and not your IP address, we usually cannot pick out your scans, and they are deleted within 90 days in any case.

If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada.

11. If you publish codes

People who scan your dynamic codes are your audience. You are responsible for telling them, where your own obligations require it, that scans are counted, and for the destination you send them to. Our Terms of Service say more.

12. Children

Accounts are for people aged 16 or older. We do not knowingly collect account information from anyone younger.

13. Changes to this policy

When we change this policy we update the date at the top. If a change affects how we use information we already hold, we will email account holders before it takes effect.