Privacy Policy
Last updated
This policy explains what personal data QRPetal (“we”, “us”) collects when you use qrpetal.com, the QRPetal app at app.qrpetal.com and short links on qrpt.link. It says why we collect it and what you can do about it.
We wrote it to meet Hong Kong’s Personal Data (Privacy) Ordinance (PDPO). For people in Europe and the UK, we also wrote it to meet the EU GDPR and UK GDPR.
The short version:
- We collect as little as we can. You can make a static QR code without an account, and we do not keep the photo you upload for that.
- Scan statistics never store IP addresses.
- We do not sell your data and we do not show ads.
- We use no tracking cookies.
- You can delete your account and data at any time.
1. Who is responsible
QRPetal is in charge of your data. In legal words, we are the “data user” (PDPO) and the “controller” (GDPR). QRPetal is a small business in Hong Kong, run by one person.
To reach us about privacy, email [email protected]. If you need our full legal name and postal address (for example, to send a formal letter), email us and we will give them to you.
2. What we collect and why
a) When you make a code without an account
| Data | Why | Kept |
|---|---|---|
| The photo, dot shape and text or link you send | To make your QR code and test it | Not stored. Used in memory, then thrown away when the code is done |
| A scrambled (hashed) form of your IP address, mixed with the date, and a counter | To apply the free daily limit and stop abuse | A few days, then deleted |
| Bot-check signals (IP address, browser details), handled by Cloudflare Turnstile | To tell people from bots | Handled by Cloudflare under its Turnstile privacy terms |
Your browser also keeps your unfinished design, photo included, on your own device. It never leaves your device unless you save it. See the Cookie Notice.
b) When you create an account
| Data | Why | Legal basis (GDPR) |
|---|---|---|
| Email address | To sign you in and contact you about your account | Contract |
| If you use “Continue with Google”: the basic profile Google shares (email, name, picture). Our sign-in provider keeps it. Our own database keeps only your email | To sign you in | Contract |
| Account ID, workspace, plan and usage counts | To run your account and apply plan limits | Contract |
| Saved designs: your photo (with location and other hidden photo data removed), dot shape, settings, link or text, preview and downloaded files | So you can come back, edit and download again | Contract |
| Editable codes: short code, title, destination link, status | To send scans to your link | Contract |
| Safety check results for destination links (from Google Web Risk) | To stop phishing and malware on our short links | Legitimate interests (keeping people who scan safe) |
| A record of important account actions (audit log), for example a code made, a link changed or a plan changed | Security and sorting out disputes | Legitimate interests |
| Emails you send us | To help you | Contract or legitimate interests |
c) When someone scans an editable code
When a phone opens a short link on qrpt.link, we record a scan event so the code’s owner can see statistics:
- the time of the scan;
- the country and region. Cloudflare works these out from the IP address. We never store the address itself;
- device type, operating system and browser type (from the browser’s user-agent);
- a visitor hash: a scrambled value made from the IP address, the user-agent, the date and a secret key. It lets us count “unique visitors per day”. It cannot be turned back into an IP address. Because the date is part of it, it changes every day, so it cannot follow the same person across days.
We do not store the IP address of people who scan codes. Bots are not counted. The code’s owner only sees totals (for example “80 scans from Hong Kong”), never single people.
Legal basis: legitimate interests (giving code owners simple statistics that respect privacy). People who scan a code can object by emailing us.
d) Payments
Payments go through Stripe, our payment provider. Stripe collects your card details itself. We never see or store your full card number.
We receive and keep only: your Stripe customer ID, subscription status, plan, renewal dates and invoice records. We never see your full card number.
Legal basis: contract, and legal duty (tax and accounting records).
e) Product analytics
We use PostHog to count events such as “opened the editor”, “made a preview”, “clicked upgrade” or “started checkout”. This tells us which parts of QRPetal work.
- PostHog keeps its data only in the open page. It sets no cookies and saves nothing in your browser.
- We do not link these events to your account or your email.
- We cut web addresses down before sending them, so sign-in codes and payment IDs never reach PostHog.
- PostHog is set to drop IP addresses.
- We never send PostHog your photos, links or payment details.
Legal basis: legitimate interests (making the product better).
f) Emails
- Service emails run your account: sign-in links, receipts, failed-payment notices, and security or policy notices. You cannot turn these off while you have an account.
- We do not send marketing emails today. If we add optional emails later (for example tips), each one will have an unsubscribe link.
g) Technical logs
Our own server logs each request: which page, the result and how long it took. These logs do not contain IP addresses or anything you sent. We keep only a fixed amount of them. When that is full, the oldest lines are deleted to make room. How long a line stays depends on how busy we are: when we are quiet, it can stay for a few weeks or more.
Cloudflare sits in front of our services and sees IP addresses to keep them safe and working. It handles them under its own terms.
Legal basis: legitimate interests (security).
h) Abuse reports
If you report a link, we keep your report. If you give your email address, we keep it too, so we can reply. Legal basis: legitimate interests (keeping the short domain safe).
3. What we do not do
- We do not sell or rent personal data.
- We do not use your photos to train AI models.
- We do not use advertising or cross-site tracking cookies.
- We do not make decisions with legal effects about you by computer alone. (An automatic link check can block a code. You can ask a person to review it.)
4. Who we share data with
QRPetal runs on its own server. Some jobs are done by other companies (“sub-processors”). They use data only on our instructions and under data processing agreements. The full list, with what each does and where, is on our sub-processors page.
In short:
- Cloudflare: website, app, short links, bot checks, email forwarding;
- Supabase: sign-in;
- Stripe: payments;
- Resend: sending email;
- PostHog: product analytics;
- Google: link safety checks, backup storage, our support inbox.
We may also share data if the law requires it, to protect people from harm or fraud, or if QRPetal is sold or merged. We would tell you first.
5. Where your data is stored
QRPetal is run from Hong Kong.
- Our API, database and saved photos: a server we run ourselves. No outside company hosts it.
- Backups: Google Cloud Storage, Taiwan.
- Sign-in: Supabase, Singapore.
- Website, app, short links and bot checks: Cloudflare’s global network.
- Payments: Stripe (global; see Stripe’s privacy policy).
- Sending email: Resend, from Tokyo. Resend keeps account data in the United States.
- Product analytics: PostHog, United States.
When data about people in the EU or UK goes to a country without an EU or UK “adequacy” decision, we rely on the European Commission’s Standard Contractual Clauses (and the UK Addendum). These are standard contract terms in our providers’ data processing agreements.
6. How long we keep data
| Data | How long |
|---|---|
| Photos sent without saving a design | Not stored (thrown away when the code is done) |
| Saved designs, photos, previews and downloaded files | Until you delete the design or your account |
| Editable codes and their settings | Until you delete the code or your account |
| Scan events and daily scan totals | 2 years, then deleted automatically |
| Usage counters (hashed IP) | A few days |
| Account details | While your account exists |
| Invoices and billing records | 7 years, because Hong Kong tax law says business records must be kept that long (Stripe keeps them too) |
| Audit log and abuse reports | Up to 2 years, longer if needed for an open dispute or legal claim |
| Our server’s request logs | A fixed amount (50 MB per service); the oldest lines are deleted when it is full |
| Backups | 30 days, then deleted |
When you delete your account, we delete your data straight away. The only things left are billing records we must keep, the audit log and abuse reports (kept as above), and backup copies, which are gone within 30 days.
7. How we keep your data safe
- Everything is sent over HTTPS (encrypted).
- Our server is not open to the internet. Traffic reaches it only through an encrypted Cloudflare Tunnel.
- Saved photos are private. Download links stop working after one hour.
- Only our API can reach the database.
- Disks and backups are encrypted.
- Passwords and keys are kept out of our code.
- We remove location and other hidden data from photos we store.
- Only the people who need access to run QRPetal have it.
No system is perfectly safe. If a data breach is likely to put you at risk, we will tell you, and the regulator where the law requires it.
8. Your rights
Wherever you live, you can:
- see the personal data we hold about you, and get a copy;
- correct it if it is wrong;
- delete your account and data (in Settings, or by emailing us);
- get a copy of your designs and codes: email us and we will send them (as a JSON file plus images);
- unsubscribe from any optional emails.
Hong Kong (PDPO). You can make a data access request or a data correction request. We will reply within 40 days, as the PDPO requires. The law lets us charge a fair fee for a data access request. In practice we do not expect to charge.
EU and UK (GDPR). You also have the right to limit or object to how we use your data (including where we rely on legitimate interests), to take your data elsewhere, and to withdraw consent where we rely on it. We reply within one month.
How to ask: email [email protected] from the email address on your account. We may need to check it is really you.
Complaints: please talk to us first. You can also complain to the Office of the Privacy Commissioner for Personal Data, Hong Kong (https://www.pcpd.org.hk), your local EU data protection authority, or the UK Information Commissioner’s Office (https://ico.org.uk).
9. Children
QRPetal is not for children under 16. We do not knowingly collect their data. If you think a child has given us personal data, contact us and we will delete it.
10. People in photos
If you upload a photo of other people, you must have their permission (see our Terms). If you are in a photo someone else uploaded and want it removed, email [email protected].
11. Changes to this policy
We will post any changes on this page and update the date at the top. For important changes we will also email account holders before they take effect.
12. Contact
QRPetal, Hong Kong [email protected]