Privacy policy.

• Barcode decoding happens on the device. Images, camera frames and scan results never reach us.
• Your email address is the only identifier you give us. There are no passwords and no profiles.
• No analytics, no advertising, no cross-site tracking; this site serves its own scripts and fonts.
• We do not sell personal information, and we share it only with the providers that run the service.
• Payments run through Stripe; we never see card details.

It covers visitors to scanlatch.com and account holders who sign up for a trial or a subscription. It also explains what the SDK does inside your own app, because you embed it on your website and your end users never talk to us.

If you embed Scanlatch in your product, the sections on collection and browser storage tell you what touches your users’ browsers and what reaches our servers — which is very little.

• Your account: your email address and when it was created. Sign-in codes are stored only in hashed form and expire within minutes.
• Your session: when you are signed in, a single cookie identifies the session. It is secure, HTTP-only and same-site. When the site is served through our network provider, we may also record the IP address and browser user agent attached to a session.
• Your websites: the origins you register.
• Installations: when the SDK first activates on one of your websites, the browser generates a random installation identifier and we record it with your license and that website so billing can count installations. It is not a device fingerprint — it lives in the browser’s storage, says nothing about the person or the hardware, and clearing that storage discards it.
• Billing: a Stripe customer reference, your subscription state, and one usage record per installation per billing cycle. Invoices, receipts and payment details are handled by Stripe.
• License checks: the SDK sends your license key, the website origin, the installation identifier and a fresh one-time value to the license service. Every answer is signed, and the browser verifies the signature before trusting it.

• Scan results. Decoded barcodes, images and camera frames stay on the device.
• Camera access. The camera is used inside your app, between the end user’s browser and your site; we are not part of that.
• Tracking data. No analytics beacons, advertising tags, social pixels or cross-site identifiers run on this site.
• Payment card details. Those go to Stripe directly.

We do not sell personal information, and we do not share it with anyone beyond the providers listed below.

The public pages of this site set no cookies. When you sign in, we set one session cookie, and it disappears when you sign out or it expires.

The SDK, running on your website, stores what it needs in your end users’ browsers: the installation identity and signed license records in IndexedDB, and the last-chosen camera in localStorage. That data stays in the browser. Clearing it removes the installation identity; if the SDK activates again afterwards, it counts as a new installation.

• Stripe processes payments, subscriptions, invoicing and tax, and handles payment details under its own privacy policy.
• Cloudflare delivers the site over HTTPS, protects it from abuse, and enforces our United States-only access policy, which involves processing visitor IP addresses.
• An email delivery provider sends sign-in codes and account mail.
• Our own servers run the website, the account portal and the license service.

Stripe, Cloudflare and the email delivery provider process data on our instructions for those purposes. We do not otherwise share personal information with anyone.

This website accepts access only from the United States; requests from elsewhere are blocked at the network edge. If you travel, the site may be unreachable until you return.

• Sign-in codes: minutes.
• Account data: while your account is active.
• Installation and usage records: while they are needed to keep billing accurate, including for past cycles you may question.
• Billing and accounting records: as long as tax and accounting law require.

• See, correct or delete your account data: contact support from inside your account.
• Close your account: the same route. We will cancel outstanding billing and remove your account data.
• Clear the SDK’s browser storage at any time; that installation stops being recognized, and a later activation counts as a new one.
• Cancel your subscription from the billing portal in your account; scanning continues to the end of the paid cycle.

The service is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has given us an email address, contact support and we will remove it.

The site and the license service run over HTTPS, license answers are cryptographically signed and verified in the browser before use, and secrets are kept away from the public site. No system is perfect; if something goes wrong that affects your data, we will tell affected account holders.

We may update this policy as the service changes; the effective date at the top is always the current version. Material changes are announced by email or in the portal before they take effect.

Questions, requests and notices reach us through the support contact inside your account. The Terms of service govern use of the service.