Privacy

Local tool and file inputs

Barcode values, GS1 data, CSV or TSV rows, images, camera frames, label contents, and workspace records are processed by site code in the browser. They are not intentionally placed in URLs, analytics events, console logs, error payloads, or server requests. Files are parsed locally. Camera access begins only after an explicit action, and media tracks are stopped when scanning ends or the tool closes. Scanned URLs are shown as inert text and are never opened automatically.

Raw CSV and scanner output are not saved automatically. A project or template reaches IndexedDB only after the user chooses Save locally. The workspace page can list, export, import, and delete those records. Browser storage remains tied to the browser profile and origin; clearing site data removes it. Exported files remain wherever the user saves them.

Operational providers and identifiers

Hosting and security providers can receive ordinary request information such as the requested page, time, IP address, user agent, referrer, and security signals. Public, indexable pages load the approved Google AdSense account-verification script during the review period. No visible manual ad units are configured. Google may process browser, device, cookie, consent, page, and advertising identifiers under its own terms and policies. Noindex pages, including the local workspace, omit that script.

BarcodeOpsKit does not pass a tool field, decoded value, CSV row, label value, or workspace record as an AdSense parameter. Interactive workbenches and results retain exclusion hooks for future placement audits. That implementation boundary does not erase the separate network and storage activity of the browser, host, consent system, or Google.

Cookies, consent, and advertising review

BarcodeOpsKit itself does not require an account cookie to use its tools. Hosting protections or the AdSense review integration may use cookies or similar storage. Where applicable law or provider policy requires consent, the deployment owner must configure an appropriate consent mechanism before serving personalized advertising. This static codebase does not treat the presence of a review tag as consent and does not claim AdSense approval.

Retention and user choices

• Do not use the tools with confidential data on a device you do not control.
• Use synthetic values for demonstrations and support reports.
• Delete workspace records from the workspace or clear the site's browser storage.
• Revoke camera permission through browser or operating-system settings.
• Use browser privacy controls for cookies and third-party storage.

Operational log and advertising retention is controlled by the relevant provider and deployment configuration, not by local tool storage. Report a suspected boundary failure through the privacy-safe correction process without attaching raw operational data.