Documentation

1. Overview

This Documentation provides a plain-language reference to how the Legitly™ brand-protection and product-authentication platform works for brands, distributors, creators, and the customers who verify their products. It is intended as an informational guide and forms part of, and is subject to, our Terms of Service, Privacy Policy, and Anti-Counterfeit Agreement. Where this Documentation and any of those agreements conflict, the agreements control.

Legitly combines tamper-evident holographic labels, unique verification codes, single-scan technology, a brand dashboard, white-label verification, and an optional API to help brands prove authenticity and help consumers confirm it.

2. How Product Authentication Works

Each genuine item is paired with a Holographic Label that carries a unique Authentication Code, typically presented as a scannable QR code together with a protected or scratch-off element. When a customer scans or enters the code, the platform checks it against the Legitly database and returns a verification result.

• Unique codes: no two genuine items share the same Authentication Code.
• Tamper-evidence: labels are designed to show evidence of removal or transfer.
• Single-scan technology: a code is designed to register as “used” after its first valid scan and cannot legitimately be re-scanned or reused, which helps brands detect duplication.

3. The Verification Lifecycle

The typical lifecycle of an Authentication Code is:

1. Issue — the brand generates codes and labels through the dashboard.
2. Apply — the brand affixes a label to each genuine product.
3. Scan — a customer scans or enters the code to verify the item.
4. Result — the platform returns a verification result and records the scan event for analytics and fraud prevention.

4. Brand Dashboard and Catalog

Verified brands manage authentication from a secure dashboard, where they can register a product catalog, generate Authentication Codes, order Holographic Labels, view scan analytics and reporting, and produce certificates of authenticity. You are responsible for the accuracy of the catalog you register and for applying labels only to genuine products you have the lawful right to authenticate.

5. White-Label Verification and Subdomains

Qualified brands may operate a white-label verification experience under their own subdomain (for example, brand.legitly.com), so that their customers cross-check the brand’s labels against the Legitly database within the brand’s own branded environment.

Subdomain prefixes are assigned on a first-come, first-served basis. If a requested name is unavailable, a modified subdomain may be issued (for example, brandX.legitly.com or Xbrand.legitly.com). Eligibility, fees, and conditions for white-label and subdomain provisioning are described on the API Access page.

6. API Access and Integration

Legitly offers an API and a configurable pop-up verification modal that brands can integrate into their own websites so customers can verify products without leaving the brand’s site. API access is granted to verified brands on a case-by-case basis and is subject to eligibility, hosting, and one-time setup requirements, and must be integrated by a member of the Legitly team. Full details, conditions, and fees are set out on the API Access page.

7. Support and Technical Assistance

Brands and customers can reach us through the “Chat Now” button on our homepage or our live support page at /support-now. Verified brands that meet the eligibility requirements receive specialized technical assistance, including help configuring their system. See the Support page for channels and scope.

8. Acceptable Use and Compliance

Use of the platform, the codes, the labels, and the API is governed by our Terms of Service and Anti-Counterfeit Agreement, which prohibit, among other things, copying or re-encoding Authentication Codes, tampering with labels, circumventing single-scan functionality, reverse engineering, and creating imitation verification pages. Your handling of personal information collected through verification is also subject to our Privacy Policy.

9. Updates to This Documentation

We may update this Documentation as the platform evolves. We will post the updated version with a new effective date. Features described here may change, and certain features depend on your plan and eligibility.