Draft for review. Legal review is required before this document is published as the effective privacy policy, including review of processing grounds, recipients and retention.
1. Scope and operator
This policy describes how the operator of Smart QR Codes handles information through the public website, account dashboard, QR codes, short links, mini-sites, API and MCP connections, billing and support.
The operator is Ozumni LLC.
Contact hi@smartqrcodes.io about personal data or this policy. A person who publishes a QR code, link or mini-site chooses its content and may have separate responsibilities for the information they collect from visitors.
2. Account and access information
- Your email address and the name, phone number or profile image you provide.
- A password hash for password-based accounts, or identifiers and profile information received when you choose an external sign-in provider such as Google.
- Session and verification records, notification preferences, workspace membership, roles and relevant account activity.
- API key identifiers, permissions and usage records, including MCP usage when you connect a client.
Protect account credentials and only authorise clients you trust. A connected API or MCP client can request information and perform actions within the permissions you grant.
3. Content, forms, support and billing
- QR payloads, destination addresses, mini-site text, images, uploaded files and settings you save or publish.
- Information visitors submit through mini-site forms and enabled interactive features, together with technical submission details.
- Support messages and attachments, including contact information, the topic, message and information needed to investigate a request.
- Billing identifiers, invoice amounts, currency, payment status and subscription periods. When checkout is enabled, Stripe processes card details; the service does not store card numbers or card security codes.
Do not publish other people’s personal information without an appropriate basis. Content embedded in a static QR code can be read by anyone with the image; content on a public link or mini-site can be accessed by its visitors.
4. Scan events and technical records
When someone follows a dynamic QR code or short link, the service can record the event time, IP address, user-agent, referring page, language and campaign parameters in the address. It can derive an approximate country or city, device type, browser and operating system from technical information. An inferred location is not the same as precise device location.
The service also processes technical information for mini-site views and submissions, access control, diagnostics and relevant administrative or integration activity. Event records containing IP addresses or other identifiers are not anonymous by default.
Workspace reports depend on the events received and the available plan. A scan or click count is not proof that a particular person read a page or completed a purchase.
5. How information is used
- Create accounts, authenticate users, recover access and enforce permissions.
- Store and publish your content, resolve dynamic destinations and provide the functions you request.
- Produce scan and click reports and apply plan and API usage limits.
- Manage subscriptions, send service notifications, answer support requests and investigate payment issues.
- Detect misuse, protect the service, diagnose faults and maintain relevant audit records.
- Consider data requests and meet obligations that apply to the operator.
The grounds that apply to processing depend on its purpose and the applicable rules. This draft does not treat use of the service as blanket consent to every use of information.
6. Cookies and local browser data
The website and account interface use a language preference cookie and browser storage for settings and selected functions. Examples include the theme, saved QR designs, scanner history, drafts and account session tokens. Browser storage is specific to the website origin and device.
The current account client stores access and refresh tokens in localStorage, rather than HttpOnly cookies. Token validity and the time a value remains in browser storage are different: an expired token can remain stored until it is replaced or removed.
The Cookie Policy explains the items, their purposes and available controls. Clearing browser data does not by itself delete server records or cancel a subscription.
7. Public website analytics
If enabled through the service configuration, the public website and account use Google Analytics 4 with Google Consent Mode v2. The Google Analytics script is not loaded when the analytics identifier is absent.
Analytics and advertising consent signals are denied by default. Allowing platform analytics grants analytics storage only; advertising signals remain denied. Declining prevents client-side Google Analytics events. Server-side events used for redirects, security and workspace scan reports are separate from this preference.
A mini-site publisher can include external content and third-party pixels. Publisher tracking scripts load only after the visitor agrees in that mini-site’s separate notice, and the choice is isolated by mini-site. Those services can then receive visitor information under their own terms.
8. Recipients and processing locations
- Google Cloud provides the service infrastructure, and Google Workspace handles service email and support correspondence.
- Stripe receives information needed to provide checkout, billing management and payment processing when those functions are used.
- An external sign-in provider, such as Google, processes the sign-in you choose. Its own privacy information also applies to that service.
- Authorised workspace members can access information within their roles. An API or MCP client you connect receives the information its permissions allow it to request.
- Visitors receive the content you publish. A webhook configured by a mini-site publisher can receive submitted form or newsletter data. Publisher-selected analytics, embedded services and external destinations can receive visitor or technical information according to their functions and policies.
Information may also be disclosed where required by applicable rules or needed to address a security incident or a legal claim. Access should be limited to what the relevant purpose requires.
Hosting and external providers may process information outside your country. This draft does not promise storage in your country or identify a particular cross-border transfer mechanism as already in place. Contact hi@smartqrcodes.io for information about the arrangements relevant to your use.
9. Retention and deletion
The time for which analytics can be viewed depends on the plan described on the Pricing page. A reporting limit is not a promise that the underlying event is physically deleted on that date. Deletion of raw events depends on a separate retention setting; without it, the current cleanup process does not delete them by age. Daily aggregates do not currently have an automatic expiry.
Current automated cleanup removes expired refresh, verification, sign-in state and temporary QR records according to their expiry, read notifications older than 90 days and webhook delivery records older than 30 days. The documented infrastructure backup rotation is 14 days. These periods do not determine how long the underlying account, content or aggregated analytics data is retained.
Account information, content, billing records, correspondence, logs and backups can have different retention needs. This draft does not set a single deletion deadline for them. Requests must take account of records needed for ongoing service, security, disputes or applicable obligations.
Contact hi@smartqrcodes.io to request deletion or ask about a category of records. Any information that must be retained and any limits on deletion should be explained when the request is assessed. Clearing local browser data only removes the data stored on that browser origin.
10. Security measures
The service uses password hashing, limited-life access tokens, refresh-token rotation, permission and workspace checks, input validation, request limits and hashed API keys. These controls reduce risk but do not guarantee that every incident can be prevented.
Use a secure device, keep credentials private and sign out on shared devices. If you suspect exposure of account data or a key, contact hi@smartqrcodes.io and revoke or change the affected credentials where available.
11. Requests and complaints
Write to hi@smartqrcodes.io to request access to information about you, correction, deletion or an export, to object to or ask for a restriction of processing, or to withdraw consent where processing relies on it. Describe the data and action concerned and, where possible, use your account email address.
To protect your information, the operator may ask for proportionate verification and clarification. The response will depend on the request and the rules that apply; this draft does not promise that every record can be deleted or exported automatically. Withdrawing consent does not itself reverse processing already carried out.
You can also raise a concern with the competent data protection authority in your place of residence, where applicable. You do not have to give up that option to contact support.
12. Updates and contact
The current revision is available on this Privacy Policy page. The policy needs to be reviewed when data uses, storage, providers or analytics change. The revision date helps you identify the text you are reading.
For privacy requests and questions, contact the operator of Smart QR Codes at hi@smartqrcodes.io.