Compliance-safe scoping

To keep discussions precise and compliance-safe, we typically scope around:

• What is being protected? Authenticity, certification, lab claim, origin claim, traceability, or buyer engagement.
• What is the misuse risk? Copy / replay (screenshots), transfer (label harvesting), substitution, or fabricated history.
• Which verification model is required? Single-use (non-transferable claims / entitlements), or persistent identity with lifecycle control (multi-event traceability).
• Where does verification happen? Consumer scan, channel partner scan, warehouse scan, audit / inspection scan, etc.
• What evidence is required? Outcome states, reason codes, exception flags, retention expectations, export needs.
• What are the constraints? Packaging type, printing process, connectivity realities, device policy, integrations.

Share only what is needed

• We recommend sharing only what is necessary for scoping.
• If you attach files, ensure they do not include sensitive personal data unless required.
• For published policies, see Privacy Policy and Data Processing Addendum.