Privacy, in plain English.

Information we use

Your email address lets you sign in and receive account messages. Your profile, saved codes, destinations and customization settings let you return to your work. Sign-in cookies keep your session active.

A scan of a dynamic code records the code, time, result, broad device category and referring website when available. The scan record does not store the full browser identification string or the referrer’s page path. This demo does not collect a scanner’s country or precise location for scan analytics.

Visits and generator activity help us understand which pages bring people to K2QR. These records include the page, time, campaign labels and referring website, rather than your code’s contents. A campaign cookie connects an earlier visit to checkout. Confirmed purchases provide purchase amounts and access status.

Support uses your account email, ticket subject, messages and attachments to handle your request. Operators can add private notes. Those notes are not part of your conversation or account export.

What a code makes public

Anyone with your code can scan it. Its destination or encoded content may be visible to them. Only share information you intend that audience to see. Changing a dynamic destination does not remove copies people already downloaded.

Files and logos uploaded to your account are private unless you explicitly share a file through a public code. A logo included in a downloaded code becomes part of that image. Support attachments marked customer-visible can be read by the ticket’s customer; private attachments stay with authorized operators.

Services that help us run K2QR

Stripe handles checkout and payment information. K2QR keeps payment references, amounts and access records, rather than collecting your card number in its own forms. SMTP2GO sends sign-in and service emails, including Support replies, using your email address and the message content.

Account records and uploaded files are stored on the local demo server. Vultr supplies artificial intelligence for operator-requested public-content drafts. Those drafts use product facts and editorial instructions; customer code contents, Support messages and personal information are excluded from those prompts.

A website reached through a code handles your visit under its own privacy practices. K2QR does not control that website.

Keeping and requesting your data

Sign in and contact Support to request an export of your own account data. We verify the account before providing it. Your export excludes other customers’ information, private operator notes and storage credentials.

Account deletion and deactivation are not available in this local demo. You can record a request through Support, but that request does not erase records, cancel purchases, change printed codes or reset your free allowance. Account, purchase, Support and scan records currently remain stored; no automatic deletion period applies to those records.

The cleanup task removes eligible anonymous website-activity records older than 90 days. It excludes purchases and signed-in customer records. Deleted file contents become eligible for cleanup after a 30-day restore window; a record of the deletion remains. These tasks do not delete your account or its printed-code identities.

Cannot sign in? The Support page includes sign-in help and the local demo help route.