Skip to content
RightQR
Help & FAQCreate QR code
Clarity for every connection

Privacy Policy

Understand what RightQR collects, how QR scan reporting works, and the choices you have over your information.

Effective November 16, 2026Last updated November 16, 2026[email protected]

On this page

1. About this policy2. Information we handle3. Dynamic QR scan reporting4. How and why we use information5. Who can receive information6. Cookies and browser storage7. Retention and deletion8. Security and international processing9. Your choices and privacy rights10. Children’s information11. Updates and contact

The essentials

You can create a static QR without an account. Account features store your workspace and saved QR content on our servers. Dynamic links record limited scan information.

RightQR does not sell personal information or share it for cross-context behavioral advertising. Contact [email protected] with questions or requests.

1. About this policy

This policy explains how RightQR (“we,” “us,” or “our”) handles personal information when you visit our website, create QR codes, use an account or shared workspace, contact support, or open a RightQR dynamic link. RightQR is responsible for the account and service information described here.

A QR code may lead to another organization’s website. The destination’s own privacy notice applies after you leave RightQR. Workspace owners are responsible for their own use of content and scan reports and any notices they must provide.

2. Information we handle

  • Account details: your name, email address, chosen character avatar or optional profile photo, password hash, confirmation status, and authentication and recovery information. Passwords are hashed, not stored as readable account passwords.
  • Workspace information: workspace and folder names, saved QR content, designs and logos, destination history, team email addresses, roles, invitations, activity records, and saved preferences.
  • QR content: website links, contact details, text, email or SMS content, and Wi-Fi credentials you enter. PDF and menu codes point to a URL you provide; they do not upload the linked document to RightQR.
  • Billing: when paid plans are enabled, customer and subscription identifiers, plan status, and invoice information. Stripe handles payment entry; RightQR does not receive your full card number or security code through its checkout.
  • Communications: the email address, message, attachments, and details you send in a support, privacy, or abuse report.
  • Technical information: requests expose information such as IP addresses, browser headers, requested URLs, and request times to our hosting infrastructure. Operational or security logs may contain this information. Scan records use the more limited format below.

Anonymous static QR generation happens in your browser. Content is not saved to a server workspace unless you choose to save it through an account. Temporary drafts may remain in this tab’s storage. Your visit can still produce network and hosting logs.

3. Dynamic QR scan reporting

A static code contains its content directly. RightQR does not receive a scan event when someone reads that code. A dynamic code contains a hosted RightQR link: opening it makes a request to RightQR before redirecting to its destination.

Dynamic scan records contain the QR identifier, event time, a broad device category, an approximate country when available, and a keyed visitor hash. That hash uses the QR identifier, UTC date, requesting IP address, and browser user-agent information. Raw IP addresses and user agents are not saved in the scan-event database. They may still be processed by the server or appear in separate infrastructure logs.

Known bots are excluded. Estimated unique scans are visitors to one code on one UTC day, not a count of people. The same person may count again on another day or code; shared networks and browser changes affect the estimate. For new dynamic scans, Cloudflare IP geolocation can supply an approximate country. VPNs, mobile networks and shared connections can affect this estimate. Older scans and requests without trusted country data are reported as unknown. We do not save precise coordinates, city or street addresses in scan records.

Authorized workspace users can view reports available to their plan, and eligible users can export reports. Visitor hashes are pseudonymous information, not a promise of complete anonymity.

4. How and why we use information

We use information to create and secure accounts, provide saved workspaces and editable links, process authorized payments, deliver confirmation and recovery emails, send team invitations, answer requests, investigate abuse, and maintain the service. Scan reporting helps workspace users understand visits to their links.

Where data protection law requires a legal basis, we rely on performance of our agreement for account and service features; legitimate interests for proportionate security, reliability, abuse prevention, and service reporting, subject to applicable rights; legal obligations for required records and lawful requests; and consent where required for optional storage or communications. Ask us about the basis for a particular use.

Scheduled digest and product update emails are not currently sent, even when a preference is saved. We do not use QR content to build advertising profiles or make decisions with legal or similarly significant effects about you solely through automated processing.

5. Who can receive information

Information may be shared as needed with providers for hosting, databases, email delivery, payment processing, and service operations. Stripe receives the information needed for checkout, billing, and fraud prevention when used; see Stripe’s Privacy Policy.

Workspace owners and authorized teammates can access workspace content and reports according to their role. Invitations disclose invitation details to the address supplied. Public QR content is available to anyone who can scan or obtain the code.

We may disclose information when legally required, to protect rights and safety, or in connection with a business transfer, subject to applicable protections. We do not sell personal information, rent customer lists, or share information for cross-context behavioral advertising.

6. Cookies and browser storage

RightQR uses cookies for sign-in and request security, tab storage for drafts and workspace selection, and local storage for appearance choices. Fonts and QR-generation scripts are served locally. The current website does not load third-party advertising or website analytics tags.

Our Cookie Policy lists browser storage entries. Use Cookie settings to manage appearance memory or clear drafts in this tab. A browser preference does not delete server records or disable dynamic-link scan reporting.

7. Retention and deletion

Business scan events are eligible for deletion after 1,096 days; other plans retain the 366-day cleanup policy. Business reports cover up to 36 months, Pro up to 12 months, and Free seven days. Downgrading from Business makes older records eligible for cleanup under the new plan, so export needed reports before changing plans. Previously deleted history cannot be restored. Automated cleanup runs approximately every six hours; deletion follows that schedule and can be delayed by an operational failure. The Free plan’s seven-day reporting window limits access, rather than deleting records after seven days.

Account, workspace, destination history, and related records are kept while needed to operate the service and handle security, disputes, or legal requirements. Financial records may need to remain after a subscription ends. Backups and logs may retain copies until their applicable retention cycles complete; deletion does not mean immediate removal from every backup.

Archiving a code changes its workspace status. It does not delete it or stop its dynamic redirect. For account or workspace deletion, contact support. We will explain what can be removed, what must be retained, and the effect on shared workspaces and printed dynamic codes.

8. Security and international processing

Measures include hashed passwords, access controls, email confirmation, protected sign-in sessions, and request validation. No online service is completely secure. Protect your account credentials and review workspace membership.

QR codes are readable content, not encrypted containers. Anyone with an image or printout may extract embedded details, including Wi-Fi passwords. Do not encode secrets or information you are not authorized to distribute.

Providers may process information outside your country. Where law requires safeguards for an international transfer, those protections must apply. Contact us for processing locations or safeguards relevant to your request.

9. Your choices and privacy rights

Edit profile and workspace details through available controls, manage team access if you are an owner, change browser preferences, or sign out. For access, correction, deletion, portability, restriction, objection, or withdrawal of consent where applicable, email [email protected]. Rights and exceptions depend on your location.

Describe the request and the account or QR link concerned. Do not send passwords or full payment details. Proportionate verification may be needed before information is released or deleted; an authorized agent may need to show authority. We respond within applicable legal time limits and explain any extension or refusal. A scan hash alone may not reliably identify a visitor’s records.

There is no sale or behavioral advertising sharing to opt out of. See Do not sell or share for browser controls and Global Privacy Control information. We do not penalize people for exercising applicable rights. Where available, you can appeal by replying to support or complain to your local data protection authority.

10. Children’s information

RightQR is not directed to children under 13. A higher local minimum age for providing personal information without parental authorization also applies where required. Do not create an account if you do not meet those requirements. If you believe a child has provided information contrary to these requirements, contact support so we can investigate and take appropriate action.

11. Updates and contact

We may revise this policy as features or practices change. We will update the date and provide additional notice where required for material changes. A future feature requiring consent will not obtain it merely through a policy update.

Let’s make it clear.

Email [email protected] for questions or privacy requests. Include “Privacy request” in the subject to help route your message.

Privacy Policy · Cookie Policy · Terms and Conditions · Contact RightQR