1. Who is responsible
The controller of the personal data described here as ours is Gerard Flores Gallardo (Clariva), NIF 41677148K, Carrer de Santa Madrona 23, 08001 Barcelona, Spain. Clariva is the trade name of Gerard Flores Gallardo, a sole trader (empresario individual) based in Spain. Contact for any privacy question: support@qrlanza.com. We have not appointed a data protection officer, as the law does not require one for our activity.
2. Two roles: your account, and the people who click your links
For your account (email, name, workspaces, redeemed codes) we are the controller. For the clicks and scans on links you create, you are the controller and we act as your processor: we record the click data on your behalf and only use it to show you analytics, send it to your webhook if you set one, enforce plan limits and keep the service secure. The data processing agreement sets out these terms. If you publish QRlanza links, you are responsible for informing your own visitors where the law requires it.
3. What we collect
Account holders and team members
- Email address and, if you give it, your name.
- A password hash (scrypt) if you set a password; we never store the password itself.
- Sign-in links sent by email: a hash of the link, the email address it was sent to, and when it was requested and used. Each link works once and expires after 20 minutes.
- Passkeys, if you add one: only the public key, its name and when it was created and last used; the private key never leaves your device.
- Session records (a hash of the session token and its expiry date).
- If you choose to continue with Google, Apple or Microsoft: the name and email address that provider shares with us, whether it verified that address, and the provider's ID for your account, so we can recognise you next time. Apple may give us a private relay address instead of your real one. We receive no password, contacts or other data from your account there.
- Workspace content: links, destinations, QR designs, tags, folders, link-in-bio pages, custom domains, API keys (stored hashed), webhook addresses and team invitations (the invited person's email address).
- Subscription details: plan, billing period, status and renewal dates, and the Stripe customer reference. Full card numbers stay with Stripe.
- Promotional codes you redeem and the date of each redemption.
- Messages you send us by email.
People who click or scan a QRlanza link
For each click or scan we store one record with:
- Date and time, and the link it belongs to.
- Country and city. Our server looks up the IP address in a local IP geolocation database (DB-IP IP to City Lite) at the moment of the click; nothing is sent to an outside service. The IP address is not stored in the click record or sent to the link owner, and it is not hashed or kept in any other form.
- Device type (mobile, tablet, desktop or bot), operating system and browser family, derived from the user agent. The full user-agent string is not stored.
- The referring website's host name only (for example,
instagram.com), not the full referring address. - The browser's preferred language, whether the visit came from a QR scan, a plain link or the API, and which redirect variant was served.
We set no cookie and store nothing on the visitor's device when they follow a link, except the short-lived cookie for password-protected links described in the cookie policy. We do not build profiles of visitors, link clicks across different links or accounts, or use fingerprinting. Above a plan's monthly quota we only count the click, without storing these details.
AI apps connected through the MCP server
If you connect Claude, ChatGPT or another AI app to QRlanza (see the MCP guide), the app signs in with OAuth and acts on one of your workspaces like an API key. For each connection we store:
- The app's registration: the name it gives itself, its redirect addresses and, if it uses one, a hash of its client secret.
- The permission you granted: which account and workspace, the scope (
mcp), when you granted it and when the app last used it. - Authorization codes and tokens, stored only as SHA-256 hashes with their expiry and use dates. A code works once and expires after 5 minutes; an access token lasts 1 hour; a refresh token lasts 30 days and is replaced each time it is used, so the app stays connected while it is used at least once every 30 days.
- A daily count of operations per account, to apply your plan's daily limit. We do not keep a log of the prompts, conversations or tool calls themselves; what the app creates or changes is stored like any other link in your workspace.
What you type in the AI app is processed by that app's provider under its own privacy policy; we only receive the tool calls it sends us. To disconnect an app, use Revoke in Settings → Connected apps: the permission and all its codes and tokens are deleted at once. Expired codes and tokens are deleted the next time the app renews its tokens, an app registration never used to connect is deleted after 7 days, and everything is deleted with the workspace or the account.
Static QR codes made without an account
The QR maker on the home page works in your browser: while you only make a static code, the address you type is not sent to us and we store nothing about it. If you choose "Make it editable", we store the destination (and every later change), a hash of the secret edit key (never the key itself) and a SHA-256 hash derived from your IP address, used only for rate limiting. The IP hash and the log of changes are deleted after 2 days; the link stays, as links never die. The edit key lives in the qrw_edit cookie and in the private edit link we show you once.
Guest links created before 20 November 2026 stored the destination and a SHA-256 hash derived from the creator's IP address, used only for rate limiting. Such a hash is pseudonymous personal data. It is deleted when the link moves to an account, when the link expires, or with the link.
Our own website
We do not use Google Analytics, advertising cookies or any third-party analytics or tracking on qrlanza.com. The only third-party script is Google's sign-in script, described below, and only on the sign-in and sign-up pages. Like any web server, ours processes your IP address to deliver pages. Server technical logs (including IP addresses of connections to the server), used only for security and troubleshooting, and backups are kept for at most 30 days; we do not keep a log of website visits.
4. Why we process it, and on what legal basis
| Purpose | Legal basis (GDPR art. 6) |
|---|---|
| Creating and running your account, redirecting your links, showing analytics | Performance of a contract (6.1.b) |
| Sign-in emails, invitations, closure exports and essential service messages (including notice of changes or a shutdown) | Performance of a contract (6.1.b) |
| Click records processed on your behalf | Processed as your processor, on your instructions (art. 28); you choose the legal basis |
| Rate limits, abuse and phishing prevention, handling abuse reports, security logs | Legitimate interest in keeping the service and its visitors safe (6.1.f); legal obligation where the Digital Services Act applies (6.1.c) |
| Answering your messages | Legitimate interest in replying to you (6.1.f), or contract if you are a customer |
| Keeping records needed to defend or bring legal claims | Legitimate interest (6.1.f) |
You can object at any time to processing based on legitimate interest. We do not send marketing emails without your consent, we do not use automated decision-making that has legal or similar effects on you, and we do not sell personal data.
5. Who processes data for us
The full, current list of providers that may process personal data, with what they do and where, is on the subprocessors page. In short:
| Provider | Role | Location |
|---|---|---|
| Hetzner Online GmbH | Hosting of the application, database and backups | Germany (EU) |
| Sendinblue SAS (Brevo) | Delivery of transactional emails: sign-in links, team invitations and the export sent when an account is closed | France (EU) |
| Stripe Payments Europe, Ltd. | Payment of monthly and yearly subscriptions (card, Apple Pay, Google Pay), invoices and the billing portal; we never see or store full card numbers | Ireland (EU) |
| IONOS SE | Our mailbox, where emails sent to support@qrlanza.com are delivered | EU |
| Porkbun LLC | Domain registrar and forwarding of emails sent to @qrlanza.com addresses, such as support@qrlanza.com | United States |
We sign data processing agreements with these providers as required by article 28 GDPR. Where a provider is outside the European Economic Area, the transfer relies on an adequacy decision (such as the EU-US Data Privacy Framework, where the provider is certified) or the European Commission's standard contractual clauses.
We may also disclose data to authorities or courts when the law requires it.
Signing in with Google, Apple or Microsoft
These providers are not our processors: each is an independent controller of the account you hold with it, under its own privacy policy. They are only involved if you choose their button (or, for Google, the One Tap prompt). We only receive the data listed below.
| Provider | Used for | Data we receive |
|---|---|---|
| Google Ireland Limited | Continue with Google and Google One Tap | Name, email address, whether Google verified it, and your Google account ID |
| Apple Distribution International Ltd. | Continue with Apple | Name (only the first time), email address or Apple's private relay address, and your Apple ID identifier |
| Microsoft Ireland Operations Limited | Continue with Microsoft | Name, email address, whether the address is verified, and your Microsoft account ID |
Only on the sign-in and sign-up pages (never on the home page or any other page, nor when someone opens a QRlanza link), when you are not signed in and Google sign-in is enabled, your browser loads Google's sign-in script from accounts.google.com to offer the One Tap prompt. Google then receives your IP address and browser details and may read its own cookies to show the accounts you are signed in to; we receive nothing unless you pick an account.
Tracking pixels and webhooks chosen by link owners
A link owner can add tracking pixels (Meta, Google Analytics 4, LinkedIn or TikTok) to a link, or send click data to their own webhook. When a link owner adds retargeting pixels (Meta, Google, LinkedIn, TikTok), we ask visitors for consent before loading them and store their choice for 6 months in a first-party cookie (qwc_…); Global Privacy Control and Do Not Track are treated as a refusal. The link owner is the controller of the data those pixels collect. Only if the visitor accepts, a short QRlanza page loads those scripts in the visitor's browser before redirecting, so the browser connects directly to those providers, which receive the IP address and may set cookies. QRlanza does not load any third-party script on links without pixels. Webhooks receive the click details listed above, never the IP address.
6. How long we keep it
- Account data: while your account exists. When you close your account, your links keep redirecting for 90 days (see the Live Links Pledge) and we email you a full export; then the account, its workspaces, links and click records are deleted automatically.
- Click records: while the link exists. Deleting a link deletes its clicks. Your plan limits how much history the dashboard shows, not how long we keep it.
- Sessions: 30 days, or until you sign out. Expired sessions are deleted.
- Sign-in link records: 30 days after they were requested.
- Connected AI apps: the permission until you revoke it; tokens until they expire, as described in section 3.
- Redeemed promotional codes: when an account is deleted, the code stays in our list of issued codes, unlinked from you, so it cannot be redeemed again.
- Abuse reports and the decisions we take on them: up to 3 years, to handle appeals and repeat abuse.
- Emails you send us: as long as needed to deal with them, and up to 3 years after.
- Server technical logs (including IP addresses of connections to the server) and backups: at most 30 days, so deleted data disappears from our backups within 30 days. We do not keep a log of website visits.
7. Your rights
You can ask for access, rectification, erasure, restriction or portability, or object to processing, by writing to support@qrlanza.com. We answer within one month. We may ask you to confirm the request from your account's email address. You can export your links and their clicks to CSV from the dashboard at any time. If you are a visitor of a link, the link owner decides about that data: contact them first. We will forward requests we receive to them and help them answer. You may also complain to the Spanish Data Protection Agency (aepd.es) or the supervisory authority where you live or work.
Residents of California and other US states
We do not sell personal information or share it for cross-context behavioural advertising, and we do not use or disclose sensitive personal information. The categories we collect are those in section 3, for the purposes in section 4. Whatever state you live in, you can use the rights in this section, including to know, delete and correct your data, and we will not treat you differently for doing so.
8. Security
Traffic is encrypted with TLS. Passwords, session tokens, API keys and OAuth codes and tokens are stored as hashes. Our server is in the EU, behind a firewall, with key-only administrative access, and access to production systems is limited to the people who run QRlanza. Webhook calls are signed so you can check they come from us. If a personal data breach affects you, we will tell you and the authority as the law requires.
9. Children
QRlanza is not meant for children. Accounts require being at least 16, or the age of digital consent in your country.
10. Changes
We will update this page when our processing changes and tell account holders by email about material changes. Cookies are described in the cookie policy.
Last updated 21 November 2026