Legal

Privacy policy

What personal data QRwise processes, why, for how long, and how to exercise your rights under the EU General Data Protection Regulation (GDPR).

1. Who is responsible

The controller of the personal data described here is Gerard Flores Gallardo (Clariva), NIF 41677148K, Carrer de Santa Madrona 23, 08001 Barcelona, Spain. Contact for any privacy question: info@clariva.tech.

2. Two roles: your account, and the people who click your links

For your account (email, name, workspace, billing 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, enforce plan limits and keep the service secure. If you publish QRwise links, you are responsible for informing your own visitors where the law requires it.

3. What we collect

Account holders

People who click or scan a QRwise link

For each click or scan we store one record with:

We do not build profiles of visitors, link clicks across different links or accounts, or use fingerprinting.

Static QR codes made without an account

The QR maker on the home page works entirely in your browser: the address you type is not sent to us and we store nothing about it. If you choose "Make it editable", the address is kept in your browser's local storage (qrw_pending_editable) for up to a day so the dashboard can offer it after you sign up; it never leaves your device until you create the link. Static codes never expire and do not depend on QRwise.

Guest links created before 20 November 2026 stored the destination and a one-way SHA-256 hash derived from the IP address, used only for rate limiting. The hash is deleted when such a link moves to an account, or with the link.

Our own website analytics

We do not use Google Analytics, advertising cookies or any third-party analytics on useqrwise.com. Statistics about our own website come from our own cookie-free server records.

4. Why we process it, and on what legal basis

PurposeLegal basis (GDPR art. 6)
Creating and running your account, redirecting your links, showing analyticsPerformance of a contract (6.1.b)
Sign-in emails, invitations and essential service messagesPerformance of a contract (6.1.b)
Click records processed on your behalfYour instructions as controller (art. 28)
Rate limits for guest codes, abuse and phishing prevention, security logsLegitimate interest in keeping the service safe (6.1.f)
Accounting and tax records of purchasesLegal obligation (6.1.c)

We do not send marketing emails without your consent and we do not sell personal data.

5. Who processes data for us

ProviderRoleLocation
Hetzner Online GmbHHosting of the application and databaseGermany (EU)
Brevo (Sendinblue SAS)Delivery of transactional emails (sign-in links, invitations)France (EU)
AppSumoSale of lifetime-deal codes; AppSumo is the seller and processes payment data under its own privacy policyUnited States

Hosting and email stay in the European Union. When you buy on AppSumo you deal with AppSumo directly; we only receive the code you redeem, not your payment details. We sign data processing agreements with our processors as required by article 28 GDPR.

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. In that case the visitor briefly sees a QRwise page that loads those scripts before redirecting, and the link owner is the controller of that processing. QRwise does not load any third-party script on links without pixels.

6. How long we keep it

7. Your rights

You can ask for access, rectification, erasure, restriction, portability or object to processing by writing to info@clariva.tech. You can export your links and their clicks to CSV from the dashboard at any time. If you are a visitor of a link, contact the link owner first; we will forward requests we receive to them. You may also complain to the Spanish Data Protection Agency (aepd.es) or your local supervisory authority.

8. Security

Traffic is encrypted with TLS. Passwords and API keys are stored as hashes, and access to production systems is limited to the people who run QRwise.

9. 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 20 November 2026