Last updated: 14 November 2026
Privacy Policy
This policy explains what personal information Baobab QR collects, why, and what you can do about it. It is written for South Africa’s Protection of Personal Information Act (POPIA) and, because people in the EU and the UK use Baobab QR too, for the GDPR and the UK GDPR.
1. Who is responsible
Ruan Francois (Pty) Ltd, trading as Baobab QR (registration number 2026/367652/07), is responsible for your information. Our Information Officer is Ruan Viljoen. Email privacy@baobabqr.com about anything in this policy.
2. What we collect about you as a customer
- Your email address, and a scrambled (hashed) copy of your password, which our sign-in provider keeps. Nobody can read your password, not even us. Where our sign-in provider offers it, a new password is checked against passwords known from data breaches: only the first 5 characters of the password’s SHA-1 hash go to the Have I Been Pwned service, never the password.
- Your workspace’s name.
- If you invite someone to your team, their email address, the role you chose and who invited them, so that we can email them the invitation. The invitation names you by your email address, and your workspace by its name.
- Everyone in a team sees the email addresses and roles of the others in it. Someone you invite sees your email address and your workspace’s name.
- If you make codes from a CSV file, each row’s link, name and folder, and whether its code was made or why not.
- If you make an API key, its name, who made it, and when it was made and last used. We keep only a scrambled copy of the key, which can’t be turned back into it.
- If you connect another app to your account, such as a design tool, which app it is, what you allowed it to do, and when you connected it and it last used your account. We keep only scrambled copies of the keys we give the app, which can’t be turned back into them. The app uses what it sees of your codes under its own privacy policy.
- If you add a public name in Settings, anyone who checks one of your codes on our Check a code page sees it.
- If you verify your website’s domain in Settings, anyone who checks one of your codes that goes to it on our Check a code page sees that you control it.
- Your codes: where they lead, the files and photos you upload, the details you put on contact cards, and their design, logos included.
- When you download a link, WhatsApp or contact card code from our free tools, the code is saved in your account with what you put in it and its design, so that it works. Until you download it, nothing you type into a free tool is sent to us. Wi-Fi, email, text and event codes are made in your browser and never sent to us.
- The emails you send us.
- If you agree in writing that we may show a sentence you wrote about Baobab QR, we show it on our website, word for word, with your first name and your business’s name. Ask us at any time, and we take it down.
- Your plan and payments, from Paddle: amounts, dates and currency, never your card details.
- If you press Tell me when Plus and Pro launch, we keep that request with your email address, email you once the day they launch, then delete it.
- Technical logs, which Cloudflare, and Supabase for signing in, keep for up to 7 days, and which hold network (IP) addresses. Our own logs hold no IP addresses and no personal details, and our database holds no IP addresses.
- To show prices in rand to visitors in South Africa, our website uses the country Cloudflare estimates from your network address while it answers you. We don’t keep it.
3. What we record when someone scans a code
When someone scans one of our codes, we record what the code’s owner has chosen to record:
- the country, region and city, estimated from the network, and the type of device, its operating system, its browser and its first language;
- the date and time of the scan;
- a visitor code that changes every day, so that nobody can be followed from one day to the next or linked back to a person.
We don’t store IP addresses or use cookies when someone scans a code. Nor do we fingerprint devices. With Count only, we record only that the code was scanned, and when. With tracking off, we record nothing, though an App download code still reads the phone’s type to send it to the right store.
Single scans are kept for 3 months. Totals by day, and by hour of the day for the busiest times, are kept for the life of the code, cities included; a code’s owner sees a city only once it has 10 scans in the period.
4. People who report a code
If you report a code, we keep your report, your email address if you give it, and a code made from your network address with a key that changes every day, never the address itself. The report may be read by Anthropic’s AI as part of our safety review. We keep reports for 2 years, then clear your email address and the report’s details.
5. When something goes wrong or people get stuck on our website
When something goes wrong on our website or dashboard, your browser tells us what failed and where: the kind of error, the page and the step, the type of browser and device, and your plan if you’re signed in. It never sends what you typed, and we don’t keep your IP address, your account or a cookie with it. We keep these reports, grouped by day, for 90 days.
To see where people get stuck, our website also counts how often visitors reach each step of making a code or an account, such as pressing Download, by day, page, type of device and, if you followed one of our own links, such as a post or an ad, which one. The counts hold no IP address, no cookie, no account and nothing you typed, and we keep them for 90 days.
6. Why we use it
- To provide the service you signed up for (our contract with you).
- To keep the service safe and prevent abuse, such as phishing codes (our legitimate interest).
- To meet tax and other legal duties (a legal obligation).
- To show your words on our website, if you agreed in writing (your consent, which you can withdraw at any time).
- To measure our ads with the Meta Pixel (in the EU, the EEA, the UK and Switzerland, your consent, which you can withdraw at any time; elsewhere, our legitimate interest in knowing which ads work).
7. Who processes it for us
- Cloudflare: hosting, our network and email routing, and Turnstile, which checks that a person rather than a bot is signing in or reporting a code.
- Supabase: our database and sign-in, in the EU (Ireland).
- Resend: sending our emails.
- Google: Web Risk checks the addresses your codes lead to, including a WhatsApp code’s phone number and the websites on contact cards, and its Gmail holds our support inbox and our company mailbox. If you use Read a QR code, your picture stays on your device. If you press Check this link, we send that link to Google Web Risk to check it, and we don’t keep it.
- The public domain registries: we look up when the domain of a code’s link was registered.
- Anthropic: its AI drafts replies to support emails, reading the email and the sender’s account details (the plan, the billing status and its dates, whether a refund is available, the number of codes, and any held, blocked or locked codes with the reasons we gave), and helps review codes held for a safety check, reading the text of the page a code leads to. Under its commercial terms it may not train its models on this, and it deletes it within 30 days, unless it has to keep it longer to enforce its usage policy or by law.
- GitHub: our code and backup workflows, with no customer data in our code.
Replies to support emails may be written by an AI assistant. Each such reply says so, and you can ask for a person at any time by replying with the word “human”.
Paddle, our reseller and the Merchant of Record, processes payments as a separate controller under its own privacy policy.
8. International transfers
Our database, the files you upload and our email sending are in the EU (the database and email sending in Ireland). What each code needs to work (where it leads, or a contact card’s details) is also kept on Cloudflare’s worldwide network so that scans are fast, and Cloudflare handles requests in whichever of its data centres is nearest. Our other providers are in the EU and the United States. All of them work under data processing agreements and the standard contractual clauses (POPIA section 72; GDPR chapter V).
9. How long we keep it
- Account information: for as long as your account exists. Deleting your account removes it at once, unless the law requires us to keep it, and our backups roll it off within 30 days. The email confirming the deletion, and our email provider’s copy of it, are kept for up to 30 days.
- Invitations to a team: until 30 days after they are accepted, cancelled or expire. The invitation email, like our other emails, keeps the address for 30 days.
- Files for bulk creation: 30 days after their codes have been made. The codes stay in your account like any other.
- API keys: for as long as your account exists. A revoked key stops working at once.
- Connected apps: for as long as your account exists. An app you remove in Settings stops working with your account at once.
- Deleting a code removes what it held, its history and its scan totals, and clears our safety records of it, except links we blocked for safety, which we keep so they can’t be used again, and anything the law requires us to keep.
- Reports of problems on our website: 90 days.
- Counts of the steps of making a code or an account on our website: 90 days.
- Support emails: 2 years, then anonymised.
- Your words on our website: until you ask us to take them down. The email in which you agreed, kept in our company mailbox: while we show your words, then 2 years, like other emails you send us.
- Payment records: as long as tax law requires. Paddle keeps its own.
10. Your rights
You can ask to see, correct or delete your information, object to or restrict how we use it, and take your codes with you (the export in Settings). Email privacy@baobabqr.com. You can also complain to the Information Regulator of South Africa or, in the EU and the UK, to your data protection authority.
11. Cookies and storage
The only advertising cookies we use are Meta’s, on our website, as described below. When you sign in, on any of our pages, your browser keeps your sign-in session in its local storage. Our website uses Cloudflare Web Analytics, which uses no cookies.
Our website, baobabqr.com, uses the Meta Pixel to measure our ads. The pages someone sees when they scan a code stay free of cookies. The pixel sets Meta’s own cookies and tells Meta which of our pages you visit, and when you make an account, open a checkout or pay, with the amount and currency of a payment. We don’t send Meta your name or email address. If you’re in the EU, the EEA, the UK or Switzerland, we ask first, and the pixel loads only if you choose Allow; elsewhere it loads straight away. Your choice is kept in your browser’s local storage, and you can change it at any time with Ad measurement at the foot of every page. Meta uses what it receives under its own privacy policy.
12. Security
Our website, dashboard and codes use encrypted connections. Your information is reached only through our own service, which checks who is asking and shows each workspace only its own; browsers can’t read our database, except to look up where a code leads, which scanning it shows anyway. We use Turnstile and limits on how often anyone can ask for things, check every payment notification’s signature, keep a record of every change to a code, and protect our own accounts with two-factor sign-in.
13. Children
Baobab QR is for people aged 18 or over.
14. Changes to this policy
We tell you by email at least 30 days before a material change takes effect.