QR Lite Help Center

Privacy Policy

How QR Lite processes account, content, visit, payment and browser storage information.

Version: 2026-11-17 — image replacement privacy revision. Effective when this version is published in the Help Center.

This Policy explains how we process information when you use the QR Lite website, customer workspace or Help Center, or scan a QR Lite dynamic code. The Google sign-in sections apply only when you choose to use that feature. You may use email sign-in when no Google option is shown.

1. Who this Policy applies to

This Policy covers code creators, workspace members and people who visit QR Lite pages by scanning codes. Once a code redirects to another website, that website's operator explains its own processing. Third-party content in a code is not an endorsement or guarantee by QR Lite.

“We” means the QR Lite service operator identified at the end of this Policy.

2. Information we process and why

2.1 Accounts and sign-in

Information Purpose
Email, account status, registration time and role Create accounts, sign in, determine permissions and handle support requests
Password hash Verify passwords; we do not store plaintext passwords
Email verification code hash, expiry, attempt count and sending records Verify email, reset passwords and prevent excessive sending; we do not store plaintext codes that can be used directly for verification
Sending limit records Record cooldowns and counts against an email hash to prevent bypassing limits by switching between registration, password reset and other entry points
Session token hash Maintain sign-in and support session revocation on sign-out or password changes

The registration page determines whether a verification code is required. Registration without a code does not mean that the email address has been verified. Unverified email addresses cannot be used for email-based authorization in other workspaces and do not receive membership, ticket and similar business notifications. Sensitive actions such as password reset still require verification.

2.2 Google sign-in, registration and linking

We load the relevant Google components and start verification only when you choose Google sign-in or account linking. Google provides identity information under its authorization screen. The server verifies the identity credential's unique account identifier, email and verification status, validity and request information. We do not store the complete identity credential or ask you to give QR Lite your Google password.

We store the Google account's unique identifier, linked email and linking time, along with security audit records for registration, sign-in, linking and unlinking. Linking uses the unique Google identifier, rather than relying only on an email match. Accounts with the same email are not automatically merged. Existing users must first sign in by their existing method and then choose to link Google. New users with a non-Gmail address that is not managed by a Google Workspace domain must also verify current access to that mailbox as prompted.

We do not request access to Gmail messages, Drive files, contacts or offline access, or use Google identity information for advertising. Google's processing of its components' requests, cookies and other information is subject to the Google Privacy Policy.

Unlinking removes the Google link held by QR Lite and revokes existing QR Lite sign-in sessions. It does not delete your account, codes or historical security audit records. It does not delete your Google account or revoke the app connection on Google's side; you can manage third-party connections separately in your Google account.

2.3 Content you save and publish

To provide dynamic codes, we store code names, destination URLs, text or menu content, styles, short addresses, expiry dates, groups, publication states and versions, as well as workspace names, members, roles and plan entitlements.

Published code content is visible to people who obtain the code or link. Do not put passwords, verification codes or private personal information in public codes. Before uploading information, images or logos for someone else, make sure you have the necessary permission.

Static code content, styling and ordinary exports on the website are processed locally in the browser. Generating a static code does not by itself save it as a dynamic code on the server. Operations requiring server processing have a different data path. For example, print color conversion sends an image to the server for processing and returns the result; it is not entirely offline.

Image replacement and decoding: QR detection, cropping and compositing for ordinary images take place in your browser. Those operations do not upload ordinary images or the content entered for a new code to the server. If a member selects a CMYK source image or new-code image, that image is sent to the server for conversion to sRGB and the result is returned to the browser for further processing; the image in the conversion request is not saved as dynamic-code content. Only use images you have permission to process, and consider whether they contain personal information.

Checking and recording image-replacement allowances requires a server connection. For usage subject to a limit, the server records the applicable account identifier or, when no valid account can be identified, an identifier hashed from the IP address and a server-side secret, together with the allowance period, count and update time. We use these records to manage allowances and prevent abuse; these allowance requests do not need the image or QR code content. A hashed identifier is not completely anonymous, and network requests, server logs or proxy logs may still involve an IP address. There is currently no fixed automatic deletion period for allowance records. To ask about access, correction or deletion, use the contact channels in this Policy.

Files selected for file codes are uploaded to private Cloudflare R2 storage for processing, review, preview and download. We store the filename, type, size, digest, version, review status and necessary access-quota records. People who obtain a published code or link may view or download the file according to the publisher's settings. A private bucket does not make a published file visible only to its owner. Previews and downloads use short-lived, restricted access. Previously issued direct read links may remain usable briefly, and copies already received on a device cannot be recalled. Drafts, historical versions and files in Trash may continue to use storage. Storage is released only after object cleanup following permanent deletion succeeds. The security-check process is described below.

To prevent prohibited content, malicious links and harmful files, dynamic content is subject to applicable automated security checks by default when submitted for publication or changed. Published content may also be checked retrospectively or periodically. Tencent Cloud Infinite in the Guangzhou region receives text, menu text, images, PDF/Office files or public webpage URLs being checked for content risks and applicable virus scanning. Google Web Risk receives public URLs being checked for known threats such as malware and phishing. Web Risk and Google sign-in are separate processes; security checks do not require authorization to sign in with Google.

Files and menu images remain primarily in private Cloudflare R2 storage. Tencent Cloud may read the specific file being checked through a signed URL valid for approximately 30 minutes; this does not grant access to the entire bucket. R2 reading is the current method. If COS staging is enabled separately, copies needed for a check enter cleanup after the task finishes, and failed cleanup remains recorded for retry. Tencent Cloud may process content in Guangzhou, mainland China; Google and other providers may process information across regions. Account passwords, sign-in credentials and payment information are not sent as moderation content. Please do not include unnecessary sensitive personal information in content submitted for publication.

Content may publish automatically after the applicable checks pass; uncertain findings may go to authorized administrators for review. Risk findings, detection errors, incomplete coverage and budget pauses are not treated as a pass. We retain submitted version snapshots, file digests, task identifiers, findings and necessary operational records for publication control, appeals and troubleshooting. Completed, expired review history that has been superseded or detached from its original content becomes eligible for cleanup after 90 days by default. Current publication evidence, risk blocks, unresolved disputes and unfinished tasks may be retained longer; not all records are deleted on day 90.

Short-lived URLs and our cleanup rules do not mean that providers immediately delete their processing copies, logs or task results. Provider-side processing and retention are governed by their service terms and privacy information. Contact us using the details in this policy for questions or deletion requests.

2.4 Visits to dynamic codes

Dynamic code statistics include visit counts, time periods, browser, operating system, referrer and approximate country or region. They help code creators understand usage and investigate problems. A visit count is not a count of unique people, and an inferred country or region is not a precise location.

Raw IP details for a dynamic code are limited to the most recent 7 days and at most 1,000 records per code. Cleanup tasks delete expired records. Workspace owners and administrators may view their workspace codes' IP details; ordinary viewers cannot. Server, reverse proxy or CDN operational logs may separately contain request information, with a lifecycle different from the product's IP detail retention period.

2.5 Website analytics

The website uses its own analytics rather than third-party advertising analytics scripts. Records include a random visitor identifier, visit path, time, referring domain, device type and browser type. A request with a valid signed-in session may also be associated with the QR Lite user ID to understand visits and registrations.

These analytics do not store URL query parameters or fragments, and the analytics event table does not store raw IP addresses. The server temporarily uses IP addresses for request rate limiting. This does not mean the processing is completely anonymous, or that servers or CDNs do not process IP addresses.

2.6 Tickets and notifications

We store the ticket titles, descriptions and messages you submit, together with status and handling records, to resolve issues. A ticket is not a public message visible to everyone in the same workspace.

We send verification codes, security messages, ticket updates and membership notifications according to account and feature status. Membership emails are mainly sent to workspace owners with verified email addresses. Receiving mail services may delay, reject or place messages in spam. Check the workspace record to determine whether an action has taken effect, rather than relying on email alone.

2.7 Orders and subscriptions

If you choose to purchase online, you are taken to Waffo Pancake checkout. That provider directly processes the name, email, billing address, tax and payment information entered there for payment, tax, subscription and refund handling. Its processing is also subject to the terms and privacy information shown at checkout.

QR Lite sends Waffo Pancake the selected product, quote currency, QR Lite order reference, checkout language and return address. We receive and verify order, payment, customer and subscription identifiers, amounts, currencies, statuses, service periods and refund or dispute results to activate entitlements, reconcile transactions, handle refunds and provide support. QR Lite does not store full card numbers, card security codes or customer information from raw payment callbacks. For signed messages, only the event type and reference identifiers needed for reconciliation are persisted.

Authorized finance or platform administration personnel handle orders and transactions according to their responsibilities. There is currently no self-service option to clear billing records. Necessary transaction and audit records may need to be retained by law after account deletion or a personal information deletion request. Cancelling a subscription does not mean payment records are deleted.

3. Cookies and browser storage

Cookies set by QR Lite have a maximum lifetime of seven days. Signing in again or selecting a language again sets the relevant cookie anew. Third-party sign-in providers may set cookies that they manage; their lifetimes are subject to those providers' notices and your browser settings.

Name or purpose What it does Lifetime
qr_session Maintains QR Lite sign-in; HttpOnly cookie Up to 7 days; invalidated on sign-out from that session or session revocation
qr_google_browser Associates a one-time Google verification with the initiating browser; HttpOnly cookie 10 minutes
qr_apple_browser Associates a one-time Apple verification with the initiating browser; HttpOnly cookie 10 minutes
qr_vid Random visitor identifier for our website analytics; HttpOnly cookie Up to 7 days; after expiry or clearing, a later visit from the same device may receive a new identifier
qrlite_language and authentication language selection Remember a manually selected interface language across applicable website and customer workspace domains. The first-party cookie is sent with requests to applicable domains; local storage is a fallback if the cookie is unavailable. The website and customer workspace support Simplified Chinese, English, Japanese and Indonesian; authentication screens also support Traditional Chinese. Cookie: up to 7 days; local storage: until cleared or overwritten
Dismissed announcement marker Avoids repeatedly showing the same announcement within a browser tab session Current tab session

On a first visit, we read the browser's preferred language. Without a manual selection, Simplified Chinese, Japanese and Indonesian use their corresponding languages, and unsupported languages fall back to English. Manual selection takes priority; explicit English, Japanese and Indonesian URLs and specific Chinese-version links remain accessible. URL redirect notices on short-link domains use the visitor's browser language and do not read the website's language preference cookie. After sign-in, the language selected in the customer workspace or support portal is also saved to the account for system notifications and support email. The administrator interface remains in Chinese. Customer content and untranslated operator content are not automatically translated.

You can clear or restrict cookies and local storage in your browser. Disabling sign-in cookies may prevent you from remaining signed in. Clearing a browser identifier does not automatically delete existing analytics records on the server. Google sign-in components may use Google's own technologies and cookies, so the website should not be described as never using any third-party cookies.

4. Providers and people who may access information

Recipient Circumstances and information involved
Tencent Cloud Hosts the application and database in Singapore and processes information necessary to operate the service; also provides content moderation and applicable virus detection in Guangzhou for the content described in this policy
Resend Sends email and processes recipient addresses, email content and information needed for delivery
Google Provides authentication components and identity information when you choose Google sign-in or linking; Web Risk separately receives public URLs for threat detection
Waffo Pancake Processes checkout information, payments, taxes, subscriptions and refunds for online purchases and provides results needed to reconcile orders and entitlements; code content and uploaded files are not submitted as payment information
Cloudflare Stores file-code files in private R2 storage; provides network forwarding and security for domains using its proxy and processes related file or request information. Not all domains use the same network path.
Authorized platform administration and maintenance personnel Handle support, permissions, faults, misuse or archive restoration according to their responsibilities; relevant operational actions are audited

Platform administrators may view accounts, workspaces, code names, short addresses, destination URLs, statuses and archive information in the administration interface. Interface permissions do not mean the underlying database or authorized maintenance personnel can never access information.

We do not sell personal information or give the information above to third parties for advertising profiles. Disclosures required by law or involving a business transfer will be handled under applicable requirements, including necessary notice.

5. Storage locations and retention

The main application and database are located in Singapore. File storage, email, Google sign-in, online payments and network proxies that are actually enabled, together with the cloud security checks described above may process information in other countries or regions. We cannot promise that all information is processed only in Singapore.

Membership expiry, hiding a code from the customer workspace and moving it to Trash do not mean permanent deletion. Expired codes are currently retained in an administrator archive rather than automatically physically deleted. Administrators may still view the original short address, destination URL and necessary records, and restore them under the applicable rules. Personal information deletion requests must be submitted and assessed separately. Archiving is not blanket authorization to keep all personal information forever.

When permanent deletion is available, confirmation by an authorized operator deletes the code's link, content and versions, style, visit details and group associations from code management and scanning services. It releases the original short address and revokes related in-app file access credentials. Related storage objects are cleaned up through the administration process. Previously issued short-lived storage links and copies already saved by visitors may not immediately expire or disappear. Security review records, which may contain content submitted at the time, reports and operational audit records remain under the existing rules. Historical backups follow their rotation cycle and are not rewritten immediately by this operation.

6. Managing your information

  • Where your permissions and membership status allow, you can change your codes, workspace and account security settings.
  • Pausing a code or moving it to Trash stops its normal public access, but does not automatically delete archives, history or backups.
  • You can unlink Google according to the account security page. If Google is your only sign-in method, first verify your email and set a QR Lite password.
  • When permanent deletion is available, workspace owners or administrators who meet the permission and workspace-status requirements may permanently delete dynamic codes from Trash. This does not close the account or delete all personal information. To correct account details, request access or an export, delete other personal information or close an account, use the contact channels below. There is currently no self-service account closure or complete data export.
  • We may need to verify your identity to avoid disclosure to someone else or deletion of the wrong person's information. If legal retention or dispute-handling needs prevent immediate deletion, we should explain the scope and reason.

Stopping use does not automatically delete stored information. Requests concerning other workspace members, visitors or public content must also take those people's rights into account.

7. Security and minors

We use HTTPS, password hashing, revocable sessions, server-side permissions and operational audits, but do not guarantee absolute security or uninterrupted service. Do not share passwords or verification codes, and sign out after using a public device.

The service is mainly for individuals, businesses and teams with QR code management needs; it is not directed at children. Minors' use should meet applicable age requirements and be guided by a guardian. Contact us if you believe minors' information has been processed without appropriate authorization so that we can investigate.

8. Changes and contact

Policy updates identify the version and effective information. Material changes to information processing should be prominently notified. Where separate consent is required, a statement that continued use means acceptance will not replace it.

Apple sign-in and account linking

Once Apple sign-in is enabled, you may choose Apple to verify your identity. We receive and verify an Apple account identifier and email information. If you choose Hide My Email, this may be an Apple private relay address. This feature does not request access to your iCloud files, photos or contacts, and we do not obtain your Apple password.

We use Apple's official web component for the button and authorization popup. Selecting the Apple sign-in option prepares the component inside the terms confirmation dialog and may contact Apple's official CDN. Selecting the official button in that dialog confirms the listed terms and continues authorization. The first network request is not guaranteed to wait until that official button is selected. Apple's authorization pages and services are also subject to Apple's own policies.

To complete sign-in, linking and later revocation, we temporarily process one-time authorization codes and identity tokens. We retain an authenticated-encrypted refresh token, not a plaintext token exposed to the browser. Developer signing keys are not sent to the browser. An authorization challenge expires after five minutes. Its HttpOnly browser-binding cookie expires after ten minutes. The server retains hashes of the relevant verification values and necessary purpose and origin information.

We retain account associations, authorization status and necessary security audit records. Verified server notifications from Apple may change forwarding or authorization status. Hashed notification deduplication receipts are retained for fourteen days. An unused authorization for which we hold a revocable credential may remain in an encrypted retry queue until revocation completes; that queue is not automatically discarded after fourteen days.

You can unlink Apple in Account security after confirming your current password. We revoke access with Apple before removing the association and ending sessions. If Apple is temporarily unavailable, we retain the association and credentials needed to retry. A verified revocation or Apple account deletion notification disables the authorization, clears invalidated tokens and ends QR Lite sessions. A minimal inactive association may remain to recognize a later authorization and avoid creating a duplicate account.

If private relay forwarding is disabled, we block further account mail to that address and retain a necessary hashed blocking record. Signing in again does not guarantee forwarding is enabled. Unlinking Apple, revoking its authorization or deleting an Apple Account does not itself delete a QR Lite account, membership, orders or QR codes. Requests to close a QR Lite account or exercise data rights continue to be handled through support under the full policy. After verification, relevant authorizations are revoked before business data is handled under applicable retention requirements.