Privacy Policy
Plain English · Last updated November 20, 2026 · Operated by Rex Lexington Labs
The short version
- We do not sell your data and we do not share it for advertising. No ad pixels, no third-party analytics, and no tracking cookies.
- When someone opens our website (not a QR code), we note the page, the time, the site that linked to us, their country, and a rough device type. No name, no cookie, and we do not store their IP address. These notes are kept for 12 months.
- When someone scans a code, we record the time, their country, a rough device type, and a scrambled (keyed-hash) version of their IP address. We do not store the IP address itself.
- The scrambled IP and browser values are deleted after 30 days. Older scan rows are deleted automatically based on the code owner’s plan.
- Account holders: we keep your email, your codes, and your plan. Card details go straight to Stripe; we never see them.
- Questions or requests (access, deletion, correction): email qr@rexlinc.com.
1. Who we are
Rex QR is a dynamic QR code service run by Rex Lexington Labs (“we”, “us”). Printed codes point to short links on q.rexlinc.com; the dashboard lives at qr.rexlinc.com. For the personal information described here, we are the “controller” (GDPR) or “business” (California).
Contact: qr@rexlinc.com. This policy covers three groups of people: account holders (people who sign up and create codes), visitors (people who open our website), and scanners (people who point a phone at a printed code).
2. What happens when someone scans a code
A scan opens q.rexlinc.com/…. Our server looks up where that code points and immediately sends the visitor there with a temporary redirect. Nothing is shown, nothing is installed, and we set no cookies on this path. We do not load advertising pixels or analytics scripts there.
After the redirect is sent, we record one small scan event so the code’s owner can see whether a flyer or sticker is working. If recording ever fails, the visitor still reaches the destination. The destination website is run by someone else and has its own privacy practices; this policy does not cover it.
3. What we collect, why, and where it comes from
| Information | What exactly | Why we use it |
|---|---|---|
| Account details (account holders) | Email address; your plan; a password (stored only in scrambled form by our sign-in provider, so we cannot read it); Stripe customer and subscription IDs; the IP address and browser of signed-in sessions, kept by our sign-in provider. | Sign you in, run your account, apply plan limits, and keep the service secure. |
| Your codes (account holders) | Each code’s name, short link, destination URL, active/paused status, creation and edit times, and total scan count. | Make the redirect work and show your dashboard. |
| Website visits (visitors) | The page opened (homepage, sign-in, privacy, or terms), the time, the website that linked here (or a short label on a link we shared), country, and a rough device type. No name, no cookie, and no IP address. | See which of our pages are used and which sites send people to us. |
| Scan events (scanners) | Time; which code; country (looked up from the IP by our hosting provider; no GPS and no city); device type (mobile, tablet, desktop, bot, unknown); whether it looks like a link-preview bot; a keyed hash of the IP address; a keyed hash of the browser’s user-agent text. | Show code owners scan counts and charts, filter out preview bots, estimate repeat scans, and spot abuse or flooding. |
| Homepage demo | If you change the live demo on our homepage, we store the address you entered (it is public and resets after 30 quiet minutes). We keep a keyed hash of your IP for up to a day to limit repeated changes. | Run the demo and prevent abuse. |
| Payments | Handled by Stripe. We receive your plan, billing status, and Stripe IDs. We do not receive or store card numbers. | Charge and renew subscriptions. |
| Your address and the sign-in or account emails we send you, plus anything you send us (for example to qr@rexlinc.com). | Sign-in links, important account notices, and support. | |
| Technical logs | Our hosting and database providers log requests (such as IP address, browser, time, and errors) to run and secure their services. | Reliability, security, and debugging. |
We collect account information from you directly. Visit and scan information is collected automatically from the request when a page is opened or a code is scanned. We do not collect anything considered “sensitive” personal information, and we do not knowingly collect information from children.
4. How we protect scanner IP addresses
When a scan arrives, our server briefly handles the visitor’s IP address in memory. Before anything is saved, we turn it into a keyed hash (HMAC-SHA-256 using a secret key stored separately from the database). Our database never stores the IP address itself. Without our secret key, a stored value cannot be turned back into an IP address, not even by trying every possible address.
The same address always produces the same value, which is how repeat scans are recognised. That also means this value is still treated as personal information under some privacy laws, so we delete it after 30 days (see section 8). Because many people share one IP address (offices, schools, phone carriers), a repeated value means “same network”, not necessarily “same person”; any “unique scanner” figure is only an estimate.
5. Cookies
We only use essential cookies: the sign-in cookies that keep you logged in to the dashboard, and a short-lived access cookie while the site is in private preview. They are needed for the service you asked for, so no cookie banner is required. We use no analytics cookies, advertising cookies, or cross-site tracking. The website visit notes above do not use a cookie. Short-link redirects set no cookies at all.
6. Why we may use your information (legal bases)
If you are in the EEA or UK, we rely on these legal bases:
- Contract — to create your account, provide codes, redirect scans, and handle billing.
- Legitimate interests — to keep the service secure, stop abuse and flooding, filter bots from charts, count visits to our own pages, and give code owners basic scan statistics. We keep this data minimal and short-lived to balance it against people’s privacy. You can object (see section 10).
- Legal obligation — to keep tax and accounting records and to respond to lawful requests.
We do not use consent as a basis. Visit notes and scan statistics are part of running the service, not optional advertising.
7. Who we share information with
We do not sell or “share” personal information (as those terms are used in California law) and we do not use it for targeted advertising. We use a small number of service providers who process data only to help us run Rex QR:
| Provider | What they do | What they handle |
|---|---|---|
| Vercel | Hosts the website and short-link service (United States) | Requests, including IP address, browser, and a country lookup; their own request logs. |
| Supabase | Database and sign-in (AWS, US East) | Account details, codes, scan events, website visit notes, sign-in sessions. |
| Stripe | Payments and the billing portal | Payment details, billing email, subscription records. |
| Google (Web Risk) | Safety check of destination web addresses | The destination address of a code, when it is saved or edited and during periodic re-checks, to see if Google lists it as phishing or malware. We do not send your name, email or any scan information. |
| Resend | Sends sign-in and account emails | Your email address and the email content; delivery logs kept about 30 days. |
| Forward Email | Mailbox for qr@rexlinc.com | Messages you send us. |
We may also disclose information if the law requires it, to respond to valid legal process, to investigate fraud, phishing or abuse (including to affected brands or security organisations), or to protect people and our service. If Rex QR is ever sold or merged, information may transfer to the new owner, who must honour this policy.
8. How long we keep information
| Information | How long |
|---|---|
| Account details and your codes | While your account exists. Deleted within 30 days of a verified deletion request, except what we must keep by law (below). |
| Website visit notes | 12 months, then deleted automatically. |
| Scan totals (the running counter on each code) | While the code exists. |
| Scan detail rows (time, country, device type, bot flag) | Free plan: 30 days · Starter: 12 months · Pro: 24 months. A nightly job deletes older rows. If you move to a shorter plan, rows beyond the new window are deleted the same night. |
| Keyed hashes of IP address and browser (scan events) | 30 days on every plan, then the values are erased from the row. |
| Homepage demo and rate-limit counters | Up to 1 day. |
| Billing and tax records | As long as tax and accounting law requires. Stripe keeps its own records under its policy. |
| Support emails | As long as needed to help you and handle follow-ups. |
| Provider logs and backups | Kept by our providers for short periods set by them (days to a few weeks). |
9. Where your information is processed
Rex QR is operated from the United States for customers in the United States, and your information is stored and processed in the United States. If you use Rex QR from another country, you understand your information will be transferred to the US. For EEA/UK users, our main providers rely on the EU–US Data Privacy Framework and/or Standard Contractual Clauses for these transfers; ask us if you would like a copy of the safeguards.
10. Your rights and choices
Depending on where you live, you may have the right to:
- know what personal information we hold about you and get a copy (including in a portable format);
- correct information that is wrong;
- delete your information;
- object to or ask us to restrict certain processing (EEA/UK);
- opt out of the sale or sharing of personal information. We do neither, so there is nothing to opt out of;
- not be treated worse for using these rights.
How to ask: email qr@rexlinc.com from the address on your account. We confirm your identity by replying to that address. Account holders can also pause or edit codes in the dashboard at any time. We respond within 45 days (one month for EEA/UK requests). You may use an authorised agent; we will ask for proof they act for you.
If you scanned a code: we cannot tell who you are from our records. If you give us the IP address you used and roughly when, we can check whether a matching scan record exists (within the 30-day window) and delete it.
If you only opened our website: the visit note has no name and no IP address, so we usually cannot find one person’s visit in order to delete it. Email us anyway and we will do what we can.
If we say no: reply to our message to appeal, and we will review it again. You can also contact your state attorney general or, in the EEA/UK, your local data protection authority (in the UK, the Information Commissioner’s Office).
Do Not Track / Global Privacy Control: we do not track you across other websites or sell data, so these signals do not change what the visit note contains. We treat them as an opt-out request regardless.
11. Children
Rex QR is for adults. Accounts require you to be at least 18 (see our Terms). We do not knowingly collect personal information from children under 13. If you believe a child has given us information, email us and we will delete it.
12. Security
We use encrypted connections (HTTPS), database access rules so each account can only see its own codes and scans, keyed hashing of IP addresses and browser values, short retention, and a limit on who can reach production systems. No service is perfectly secure. If a breach affects your information, we will notify you and regulators as the law requires.
13. Changes to this policy
We will update this page when our practices change and change the “Last updated” date. For material changes affecting account holders, we will also email the address on your account before they take effect.
14. Contact
Rex Lexington Labs (Rex QR) · qr@rexlinc.com · qr.rexlinc.com
To report a short link that points to phishing, malware, or other abuse, email the same address with the link; we review reports and pause codes that break our Acceptable Use rules.