Trust and operations
Contact and corrections
A privacy-safe reporting process for content, standards, accessibility, and software issues.
Reviewed
Email contact
Email contact@barcodeopskit.com for content, standards, accessibility, privacy, security, or software reports. BarcodeOpsKit is a static site and does not run a server-side contact form. Email delivery, receipt, review, and a response are not guaranteed. Follow the privacy-safe reporting guidance below before sending a message.
What to include
- Issue category: content, standards, accessibility, privacy, security, or software.
- The public page path and visible heading.
- The exact statement or step that appears wrong.
- Expected behavior and a concise reproduction using synthetic data.
- For standards corrections, the primary source title, version, section, and URL.
- Browser and assistive technology versions when relevant.
Do not include operational data
Never send a real GTIN, UPC, EAN, GLN, SSCC, GS1 element string, Digital Link, scan result, CSV row, uploaded filename, label, workspace backup, customer record, secret, token, or camera image. Replace values with a clearly labelled synthetic example. BarcodeOpsKit cannot determine registration or ownership from a submitted number.
How corrections are handled
A standards-dependent correction should identify the authoritative source before code or explanatory content changes. Calculation and parser fixes require a regression test. Content changes retain source and review metadata. Accessibility and privacy reports are assessed against the stated target and data boundary. The public changelog records user-visible corrections once evidence is available.