How we protect your codes

Effective November 17, 2026

Each line on this page describes what runs today, and we change the page when that changes. Limits sit under the facts they limit.

Where your data is

QRCTools runs on Google Cloud in Iowa. Your codes, scan stats and form answers are in a database that Neon runs on Amazon's servers in northern Virginia, in the US. Firebase Authentication, a Google service, handles sign-in from US data centers. PostHog, in the US, counts visits to our site and which screens people open in the app. We don't offer a choice of region.

Limits

Google's network handles each request near the person making it, and it keeps copies of public pages around the world. Google keeps our app's request logs for 30 days and can store them outside the US. An AI app you connect keeps what it reads wherever that app runs.

How your data is encrypted

Your browser reaches our app over HTTPS, and we tell browsers to use only HTTPS for our address. Our app reaches the database over TLS, the standard encryption for data that moves between computers. Neon requires TLS on every connection. On disk, Neon encrypts your data with standard strong encryption (AES-256), and Google encrypts what it stores for us, including sign-in data.

Limits

We add no encryption of our own, so anyone with access to our database can read links, form answers and WiFi passwords. If a code is printed with an http:// address, its first request isn't encrypted, and we move it to https straight away.

Workspaces

Each workspace has its own codes, folders, people, brand kit, custom domains, workflows, scan stats and form answers. Someone outside can't open them in the dashboard, the API or an AI app unless a person in the workspace invites them or shares a folder. A code you can't reach looks the same as one that doesn't exist. Only your workspace's codes open on your custom domain. A code or folder can't move to another workspace, because QRCTools refuses.

Limits

Workspaces share one database and are kept apart by checks in our application. Anyone who has a short link can open it, and short links have no password. Someone given Manage on a shared folder can invite more people at view or edit codes.

Roles and shared folders

We check your role each time you or a connected app opens or changes something. On the free plan, a team workspace has owner, admin, member and viewer roles, and a shared folder gives someone view, edit codes or manage access. When someone leaves a team or is removed, they lose access at their next request in the dashboard, the API and any AI app they connected. The codes they made stay with the team.

Limits

A role covers a whole workspace, so staff who shouldn't see every client need separate workspaces. On the free plan, someone who can edit codes can delete them. Anyone with the member role can share any folder with an email address outside the team, at view or edit codes, and there's no setting to stop it. People a removed member shared a folder with keep that access until someone removes it. Invites a removed member sent stay open until someone cancels them. Files someone already downloaded stay with them. When two people edit one code, the later save wins.

Activity log

Each team workspace records changes to its codes, folders, workflows, people and settings, with who made each change, when, and whether it came from the dashboard, the API or an AI app. Owners and admins can read the last 30 days and download them as a CSV file. The log holds no IP addresses.

Limits

The log doesn't record sign-ins, downloads, API keys, connected AI apps, tag changes or blocks by our team. A bulk upload is one entry with a count for each 500 codes, and a workflow put on many codes is one entry with a count. Neither lists the codes. If our database has a problem at that moment, a change can go unrecorded. Personal workspaces have no log.

AI apps you connect

An AI app has your role in each workspace, so it can do only what you can. When you connect it, you can untick Make changes so it can only look. Disconnecting it in Settings ends its access at once. It can't delete codes, share folders, invite people, tag or move codes, set a code's own rules or form, read form answers or upload a CSV. When someone scans, fixed rules pick the page, and no AI is involved.

Limits

One connection reaches every workspace you're in and can't be limited to one. Team owners can't see or disconnect members' AI apps. Changes reach printed codes at the next scan, and there's no undo. We ask AI apps to check with you first, but the app decides. An app names itself when it connects, so check the Returns to line on the connect screen. Changing your password doesn't end a connection.

API keys and tokens

We keep one-way fingerprints of API keys and tokens, and the first few characters of a key so you can recognize it. We show a key once. A key can be read-only, and a revoked key stops working at once. Each key or connected app gets 120 requests a minute.

Limits

A key reaches every workspace you're in. Keys don't expire until you revoke them, and changing your password doesn't end them. Team owners can't see or revoke members' API keys.

Signing in

You sign in with an email address and password or with Google. Firebase Authentication handles passwords, and we never see them. You can turn on two-step sign-in, with a code from a phone app and one-time recovery codes. A session lasts 5 days. Signing out ends your sessions on every device.

Limits

Single sign-on and team sign-in rules aren't available yet. A session doesn't end when you stop using it. Signing out doesn't end API keys or connected AI apps. Revoke those in Settings.

People who scan a code

We don't store the IP address of anyone who scans. We use it for a moment to find the country, and then we drop it. Google runs the servers that carry the request, so Google sees the address too. Country is the finest location we record from a scan, and we don't collect GPS or city. Form answers are stored without IP addresses.

Limits

A form can ask people for anything you write into it. Scans and form answers are kept until the code or workspace is deleted.

What our team can see

One person at QRCTools can open a page that lists every account, code and team, to run the service and deal with abuse. That page doesn't show form answers or what's built into a code that can't change after printing, and it shows only the name and first few characters of an API key.

Limits

Anyone with access to our database can read those things, and 1 person has that access. We don't log when our team opens that page. Blocks by our team don't appear in a workspace's activity log.

How we change the service

Each proposed change goes through automated tools that check it and the software it uses for known security problems. Our repository doesn't stop a change from shipping when a check fails, and no person has to review a change before it ships. The secrets our app uses are kept in Google's Secret Manager. Our test system keeps a key for our database provider in GitHub. Our automated tests run on temporary copies of our database, so those copies hold customer data for up to 7 days.

Reporting a code

qrc.tools/report takes reports without an account.

Limits

We don't check links against Google's lists yet, so a harmful link isn't stopped when someone saves it.

Your data

You can download your profile and the folders and codes you made in your personal workspace as one file. Scan stats and form answers download from each code's page. You can download every code you can see in a workspace as one CSV file. You can delete your account in Settings, unless you own a team with other people in it. The privacy page lists what we keep.

Limits

There's no download of rules, forms or workflows. Firebase can keep sign-in data in its backups for up to 180 days after you delete. We can restore our database as far back as 30 days, and we can't restore one customer's data on request.

What we don't have

Single sign-on, team sign-in rules and checks of links against Google's lists aren't available today. Our app's pages have no Content-Security-Policy header. We have no data processing agreement, no written incident plan and no uptime commitment. Nobody outside QRCTools has audited it or run a penetration test on it, and we hold no security certification, so you won't see badges here.

Telling us about a problem

If you find a security problem, write to us through the contact form and say what you found.