Privacy policy
Version 1.1 · in effect since November 16, 2026
This policy says which personal data Qrino handles, what for, on what legal basis and for how long. Static QR codes, the ones on the free plan, are made in your browser: their content never reaches us.
1. Who handles your data
The controller is Dedorama Portais de Conteúdo na Internet Ltda., CNPJ 69.983.580/0001-80, Rua Pais Leme, 215, conj. 1713, Pinheiros, São Paulo/SP, CEP 05424-150, Brazil.
Data subject channel, for any request or question about your data: privacidade@qrino.app. As a small processing agent, Dedorama does not appoint a data protection officer (ANPD Resolution CD/ANPD No. 2/2022); this channel plays that role.
2. What we keep, what for and for how long
Rows marked Pro apply only to Pro: dynamic QR codes, accounts and subscriptions. The legal bases are those of Art. 7 of Brazil's General Data Protection Law (LGPD).
| Data | What for | Legal basis (LGPD) | How long |
|---|---|---|---|
| Static QR codes and the editor draft: the content (link, Pix key, Wi-Fi password, contact and more) and the design | Making the QR code in your browser | Not applicable: none of it reaches us | Only in this browser tab, until you close it |
| Access record: IP, date and time of each access to the site, the dashboard and dynamic QR short links and, in the dashboard, the account that signed in (the IP and the account, encrypted) | Complying with Brazil's Internet Civil Framework (Law 12,965/2014, Art. 15); in the dashboard, knowing which account acted, to answer a court order or an abuse case | Legal obligation (Art. 7, II); the account in the dashboard, legitimate interest (Art. 7, IX) | We keep, for 6 months and confidentially, the access record the law requires (IP, date and time) and, in the dashboard, the account that signed in. It is not part of the metrics and is only handed over under a court order. When an authority asks for a hold (Internet Civil Framework, Art. 15, § 2), what it asks for stays for the period requested. |
| Site counters: downloads by QR type (e.g. Wi-Fi), clicks on the I want this button of coming-soon types and on the site's invitations and links, with where the link is and the day, and how many times the editor warned that the frame's call to action doesn't match the QR type and how many times the fix was accepted, by type — never the content or the design, without cookies and without storing who it was | Knowing which QR types and which pages are used | Legitimate interest (Art. 7, IX) | Daily counts, which identify no one |
| Free-tier counters: visits (one per browser tab, only on public pages, outside the dashboard and the sign-in page) and QR codes generated by type, with the day and the tab's source (the utm_source of the link that opened the first page, in lowercase and only with letters, digits, dot, hyphen and underscore; with no utm, “direto”, direct) — never the QR code's content or design, the page address or the site you came from, without cookies and without storing who it was | Knowing how many visits the site gets, which QR types are generated and which promotions bring visits | Legitimate interest (Art. 7, IX) | Daily counts, which identify no one |
| Anti-abuse code: computed from the IP with a secret and changed every day; it is not the IP | Limiting repeated counter submissions, reports and notice requests | Legitimate interest (Art. 7, IX) | Up to 2 days |
| Visits (Vercel Web Analytics): the page address without its parameters, the site you came from (if it is another one), approximate country, region and city, operating system, browser and device type — outside the dashboard and the sign-in page, without cookies. What you type in the editor is never sent with the visit | Counting visits to the site's pages | Legitimate interest (Art. 7, IX) | At Vercel, which shows only totals; it counts visitors with a code that lasts one day |
| Pro founders list: the email, the language, the text and version of the consent you accepted, the date and time and the page where you joined and, for the consent to the international transfer (the form's separate box), the text version and the date and time | Sending the Pro opening notice, the founder offer and Qrino news until it opens | Consent (Art. 7, I); the international transfer, specific and highlighted consent (Art. 33, VIII) | Until Pro opens, when the list is deleted; without the email confirmation, 7 days. To leave earlier, one click on the link in any of our emails deletes yours right away |
| Currency: the approximate country, which our hosting derives from the IP on each visitPro | Showing the price and charging in your country's currency (Brazilian reais in Brazil, US dollars elsewhere) | Legitimate interest (Art. 7, IX) | The country is not kept: only the currency, in a cookie (Cookies section) |
| Account: email, creation and access dates and open sessions (device, browser and IP, kept by the sign-in service, Supabase Auth)Pro | Signing in to the dashboard and keeping you signed in | Performance of a contract (Art. 7, V) | Until you delete the account; the session, until you sign out or go 30 days without using it |
| Sign-in history: the IP, date and time of each sign-in, sign-out and session renewal, kept by Supabase AuthPro | Protecting the account and knowing where it was accessed from | Legitimate interest (Art. 7, IX) | 6 months; deleted when the account is deleted (if the cleanup fails at that moment, by the next day) |
| Dynamic QR codes: each code's name, destination and design (colors, shapes, frame and its texts) and the logo, if you upload one: your browser shrinks it into a PNG of up to 256 px, and the server strips its metadata (text, date, camera data) before storing it. Only you can see the design and the logoPro | Making the QR code work and showing the design in your dashboard | Performance of a contract (Art. 7, V) | Deleting a QR code takes it offline and deletes the design and the logo at once; the record (name, destination and short link) stays, so the short link is never reused. A QR code with a security warning or blocked can't be deleted (Terms, item 7). When the account is deleted, the name, design and logo leave; the short link stays, with no link to you, so it is never reused, and so do the destination and status while the QR code stays online (if you choose to keep it) or under a warning or block in force |
| Dynamic QR scans: date and time, approximate country, device type and operating system, and a code that changes every day, only to count unique visitorsPro | Showing the QR code's owner how many people scanned it, by day, country and device | Legitimate interest (Art. 7, IX) | 12 months with Pro; 30 days when the account has no subscription; deleted when the account is deleted (if the cleanup fails at that moment, by the next day), and a QR code with no owner records no scans |
| Safety check: the full destination address, checked against Google Web Risk on creation, on edit, when reported and about once a day. Rejected destination: only the domain, the threat type, the account and the datePro | Protecting people who scan from scams and malware and noticing repeated attempts | Legitimate interest (Art. 7, IX) | Rejected destination: 90 days |
| QR reports: the reported QR code, a copy of its destination, the reason and the optional text, without the reporter's emailPro | Analyzing the report and protecting people who scan | Legitimate interest (Art. 7, IX) | The text, 90 days after the case is closed; the case, 12 months after it is closed (30 days after, if the QR code is deleted). For confirmed scams or prohibited content, a copy of the text stays in the moderation record |
| Moderation: every step (security warning, review, block, suspension, appeal and answer), with the date, who decided (the system or the email of the person on our team), the note of who decided, a copy of the case (the QR code's name and link, the destination at the time, threat types, the report reason and, for confirmed scams or prohibited content, the report text), the text of appeals and the answer, and whether the email to the owner went outPro | Deciding each case, answering appeals and proving what was decided | Regular exercise of rights (Art. 7, VI) | 5 years, even if the QR code or the account is deleted; on account deletion, the record loses its link to the account; what is still in force — an active warning, a confirmation that still counts against the account and a suspension — is kept while it is in force |
| Account deletion record: the date, how it was done (through the admin or outside it), the choice (keep or switch off the QR codes), who on the team carried it out (outside the admin, the system that deleted it) and the counts, without your email or the account idPro | Proving that the deletion request was fulfilled | Legal obligation (Art. 7, II) and regular exercise of rights (Art. 7, VI) | 5 years after the deletion |
| Subscription and payments: the plan, the currency, the status, the dates (start, renewal, cancellation, late payment and refund) and the Stripe codes of the subscription, payments, disputes and refunds, plus the currency × card country counts (only the codes, with nothing about who paid). The card stays only with StripePro | Charging, renewing, canceling, refunding, answering disputes and checking whether the currency matches the card | Performance of a contract (Art. 7, V); for payment records, legal obligation (Art. 7, II) and regular exercise of rights (Art. 7, VI) | The subscription, while the account exists; on deletion, the ended subscription stays with no link to the account, as a payment record, 5 years after it ends. Payment, dispute and refund records, 5 years after they are recorded, also at Stripe |
| CPF or CNPJ for the invoice: the optional field at checkout in reais, checked and kept only at Stripe, as the customer's tax ID; never in our database or logsPro | Issuing the invoice (NFS-e) in the right name | Legal obligation (Art. 7, II) and performance of a contract (Art. 7, V) | At Stripe, while the customer exists and for the period required by tax law |
| Cancellation reason: the optional answer, from a fixed list with no free text, with the day and how long you had been subscribed (1st month, 2 to 3 months, or 4 months or more)Pro | Understanding why people cancel | Legitimate interest (Art. 7, IX) | With the subscription; deleted with the account |
| Subscription counters: checkouts started (once per account per day, with a code derived from the account that changes every day), new subscriptions, cancellations and refunds, per day, without linking the count to the accountPro | Knowing how many people subscribe and cancel | Legitimate interest (Art. 7, IX) | Daily counts; the code, up to 2 days |
| Emails: the sign-in code, subscription and moderation notices (with the QR code's name and short link) and answers to appealsPro | Telling you what happens to your account and QR codes | Performance of a contract (Art. 7, V) | At the email provider, for its period; the replies you send reach contato@dedorama.com |
3. For people who scan a Qrino QR code
Static QR codes: they don't go through us. The phone reads the content straight from the pattern; nothing reaches our servers, and we don't know a scan happened.
Dynamic QR codes: the phone opens the Qrino short link, which leads to the destination chosen by whoever created the code. On the way, we record the scan: date and time, approximate country, device type and operating system, and a code computed with a secret, which changes every day, only to count unique visitors. The browser and the language are not kept, and the redirect sets no cookie.
We keep, for 6 months and confidentially, the access record the law requires (IP, date and time) and, in the dashboard, the account that signed in. It is not part of the metrics and is only handed over under a court order.
Whoever created the QR code sees the scans by day, country and device and can download them, without the code. If the destination is flagged as dangerous, you see a warning in its place. The destination site belongs to whoever created the QR code and has its own privacy policy.
5. Who we share with
We don't sell data. Only these suppliers handle data on our behalf, each for what the table says. Vercel's functions and Supabase's database are in São Paulo, Brazil.
| Supplier | What for | Country | International transfer |
|---|---|---|---|
| Vercel | Hosting of the site and its functions, and visit metrics (Web Analytics) | USA | Vercel's data processing agreement (DPA) |
| Supabase | Database and sign-in | Singapore | Supabase's data processing agreement (DPA) |
| Resend | Sending the emails | USA | Resend's data processing agreement (DPA) |
| Google (Workspace) | Dedorama's email: messages sent to Qrino addresses, such as privacidade@qrino.app, and the contato@dedorama.com mailbox, which receives replies to our emails and support requests | USA | ANPD standard contractual clauses, in Google's data processing addendum |
| StripePro | Payments, refunds and receipts | USA | ANPD standard contractual clauses, in Stripe's data transfers addendum |
| Google (Web Risk)Pro | Safety check of destinations: receives the full destination address | USA | ANPD standard contractual clauses, in Google's data processing addendum |
Founders list: your email goes through Vercel (USA) and is stored at Supabase (Singapore; the database is in São Paulo) and Resend (USA), which sends the notices. This international transfer relies on the specific and highlighted consent you give in the form's separate box (LGPD, Art. 33, VIII), apart from the list's box. To withdraw it, leave the list: one click on the link in any of our emails deletes yours right away.
The site that receives a dynamic QR code visit is the destination site, straight from the phone of whoever scans; it is not our supplier.
6. Your rights
Under the LGPD (Art. 18), you can request: confirmation that we handle your data and access to it; correction; anonymization, blocking or deletion of what is unnecessary or excessive; portability; deletion of what we handle based on your consent; information on who we share with; withdrawal of consent; and objection to processing based on legitimate interest.
Ask at privacidade@qrino.app. We answer within 15 days; confirmation that we handle your data, in a simplified form, goes out as soon as we check the request is yours. To protect the account, we may ask for the request to come from its email.
In the Pro dashboard, you can download your destinations and your analytics as CSV at any time.
A destination's security warning is automatic (Google Web Risk). To ask for a review by a person, appeal from the dashboard (Terms, item 7).
If you think we didn't answer properly, you can complain to Brazil's National Data Protection Authority (ANPD).
7. Account deletion
Ask at privacidade@qrino.app and choose whether your dynamic QR codes keep redirecting or are switched off (Terms, item 10). Leaving our database: the account, the sessions, the name, design and logo of the QR codes, the cancellation reason and the rejected destinations; and, right after, the sign-in history and the QR code scans (if the cleanup fails at that moment, by the next day).
What stays, with no link to the account, for the periods in the table: the ended subscription and payment records, the moderation record and the deletion record. The access record stays as it is until it reaches 6 months, or until the end of a hold requested by an authority: in dashboard accesses, with the account id, encrypted. From each QR code, the short link stays, so it is never reused, and so does the destination while the QR code stays online (if you choose to keep it) or under a warning or block in force. At Stripe, the customer stays (the email, the account id, the payment methods and, if you gave it, the CPF or CNPJ for the invoice), for the tax period.
8. Security and incidents
Only the people who run the service access the data, and only what they need; connections are encrypted (HTTPS).
If a security incident may bring you relevant risk or harm, we notify you and the ANPD within the period set by regulation.
9. Changes to this policy
Each version has a number and an effective date and is kept, with its own address, in the list of versions on this page. A relevant change is announced on the site and, to account holders, by email, before it takes effect.