> For the complete documentation index, see [llms.txt](https://docs.optivalux.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optivalux.com/trust/claims-and-limitations.md). # Claims & Limitations Optivalux is infrastructure that provides verifiable evidence. It does not make impossible guarantees. This page sets out the language Optivalux uses, the language it does not use, and the limitations that apply. ## What we say * **verified** * **registered** * **certificate active** * **authenticity evidence** * **product identity** * **provenance** * **ownership history** * **registered authenticator** * **authenticator verified** * **evidence checked** * **matches the registered identity** A precise result reads like: *"Authenticator verified · matches the registered identity · certificate active · checked 14:02."* ## What we do not say Optivalux does not describe itself or any product using these phrases, or equivalents: * ~~guaranteed genuine~~ * ~~100% authentic~~ * ~~unclonable~~ * ~~counterfeit-proof~~ * ~~fake-proof~~ * ~~tamper-proof~~ * ~~guaranteed value~~ * ~~fully trustless~~ * ~~blockchain-secured~~ * ~~legally proves ownership everywhere~~ ## Precise authenticity language A successful verification means: **the product's registered authenticator produced fresh, valid evidence that matches the registered identity, at the stated time.** It does not mean: * that the object is certainly the original product (see *transplant* below); * that the authenticator was physically next to the phone (see *relay* below); * that the person holding it owns it. ## Limitations of authentication * **Tag transplant.** A real authenticator removed from an original product and attached to another item would still verify. Mitigation is physical (embedding, tamper-evident or destructive-on-removal inlays) and varies by category. For some categories this risk is significant. * **Relay.** Evidence shows recent access to the authenticator, not co-location. Monitoring of unusual patterns reduces, but does not remove, this risk. * **QR codes and links** only locate a record. They are never evidence of possession. * **Factory-level misuse.** A compromised registration station could register real authenticators to non-original items within the brand's batch limits. * **Users who do not verify.** Protection depends on people tapping the authenticator. A buyer who relies on a QR code or a seller's word gets no protection from Optivalux. ## Off-chain dependencies Core certificate state, ownership and recorded provenance are kept on blockchain infrastructure. Other parts are operated services, and Optivalux depends on them: * **Symmetric verification** relies on the Optivalux verification service, which is a trust anchor for that model. * **First ownership** relies on the brand's claim authorization. * **Owner accounts and applications** are a trust surface: owner sovereignty assumes the owner controls their own account credentials. * **Indexes and databases** are projections of the record and can briefly lag behind it. * **Product details**, images and service information are held off the core record. * **Deployment and software approval** rely partly on verifiable process (published, audited builds) rather than on the record alone. See [Trust Model](/trust/trust-model.md). ## Privacy * No personal data is written to the core record, and public verification does not show the owner's identity or account. * Account identifiers on a public network can, in principle, be linked across products. How owner account identifiers are protected, and how this relates to data-protection law, is an **open design and legal-review item** to be resolved before a pilot with real consumers. Optivalux does not claim that public account identifiers are, by themselves, compliant with data-protection law. ## Legal and regulatory limitations * **Ownership in Optivalux is not legal title.** It is the recorded holder of a product's certificate within Optivalux. It does not determine legal ownership under the law of any jurisdiction and does not override court orders, inheritance law, insolvency or other legal processes. * **Optivalux is not a trademark registry** and does not replace trademark registration or enforcement. * **Digital Product Passport** readiness is a direction, not a compliance claim. Regulatory fit is assessed per category and market. * **No regulatory approvals** are claimed. ## No guaranteed value Optivalux does not set, guarantee or predict the value of any product. Verifiable evidence and history may help buyers and sellers, but market value depends on many factors outside Optivalux. ## No absolute anti-counterfeit claim Optivalux makes counterfeiting and misrepresentation **harder to hide** by giving each original product verifiable evidence and a visible history. It does not make counterfeiting impossible and does not claim to. ## Current maturity The capabilities described in these docs are implemented in the Production V2 protocol but are **not yet live** on a public network or in connected applications. See [Current Stage](/getting-started/current-stage.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.optivalux.com/trust/claims-and-limitations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.