Effective date: 21st July 2026
Service provider: Verares Labs Inc.

3. Acceptable Use and Verification Disclaimer

3.1 Short-form notice for the public verification page

Verification notice

What “Verified” means. Res Labs accepted this NFC Tag’s cryptographic response, found the Tag in its registry, linked it to the displayed Supplier batch record, and found recorded source and integrity evidence for the displayed third-party Lab COA.
What it does not mean. Res Labs did not open, sample, test, analyze, manufacture, bottle, store, or ship this vial. Res Labs does not verify the vial’s contents, identity, purity, potency, concentration, sterility, safety, legality, or fitness for any use. A genuine Tag can still be put on the wrong vial, moved, misapplied, stolen, or associated with inaccurate Supplier or Lab information.
The Lab document controls. The COA was produced by the named third-party Lab, not by Res Labs. Open the official COA on the Lab’s own domain and review the actual tests, methods, dates, limitations, and results. A test of a batch sample is not proof about every vial.
Research use only. Materials shown here are represented for legitimate laboratory research only—not for human or veterinary consumption, administration, diagnosis, treatment, compounding, food, cosmetic, or household use. Do not use this page to make a medical, dosing, or safety decision.
Warnings matter. Do not rely on a page showing a recall, revocation, clone warning, unknown Tag, contract mismatch, unavailable status, broken Lab source, or a vial that does not match the displayed batch information. Contact the Supplier and Lab independently.
Tap logging. To authenticate the Tag and detect replay or cloning, Res Labs logs the Tag identifier, tap counter, timestamp, IP address, country-level location and optional approximate city, and browser or device information as described in the Privacy Policy.

Use of this page is subject to the Terms of Service, Privacy Policy, and the long-form disclaimer below.

3.2 Purpose and scope of the long-form disclaimer

This Acceptable Use and Verification Disclaimer governs every public verification page, verification result, badge, certificate-style display, API response, NFC Tag, Batch Record, COA link, integrity record, archive link, blockchain proof, and related statement made available through Res Labs. It supplements and forms part of the Terms of Service. Capitalized terms have the meanings given in the Terms.

The purpose of a Verification Record is to help a viewer evaluate provenance evidence. It is not to replace independent laboratory testing, chain-of-custody controls, regulatory review, product inspection, professional judgment, or the viewer’s obligation to comply with law.

3.3 Limited scope of Res Labs verification

When a page displays VERIFIED, the status is limited to the evidence then available to the Services. Depending on the record and product version, Res Labs may have performed some or all of the following:

checked that the NFC response was in the expected format;
authenticated a cryptographic message associated with the registered Tag;
checked a Tag counter or other replay-resistance signal;
confirmed that the Tag identifier appeared in the Res Labs registry;
resolved the Tag to the displayed Supplier Batch Record;
confirmed that the submitted COA URL matched an approved Lab domain at the time of submission;
retrieved or received a COA file and calculated a cryptographic hash;
recorded an IPFS content identifier or other archive reference;
anchored a hash or related record to a blockchain; and
checked the record’s current off-chain status for recall, revocation, or another warning.

These checks support the statement: this Tag passed the platform’s authentication check and points to this recorded batch and this recorded third-party Lab COA. They do not support the statement: Res Labs proved what is chemically inside this vial.

3.4 No chemical, physical, safety, or legal verification

Res Labs does not take possession of Research Materials, witness their production, select test samples, seal sample shipments, supervise a Lab, inspect Supplier facilities, or maintain physical custody from testing through delivery. Res Labs does not perform identity, purity, potency, concentration, sequence, sterility, endotoxin, bioburden, heavy-metal, solvent, stability, fill-volume, contamination, authenticity, or any other chemical or physical test.

Accordingly, a Verification Record does not establish or guarantee:

that the vial contains the named substance or any substance at all;
that the vial contents match the COA, label, batch photo, Supplier description, or another vial;
that the tested sample came from the displayed batch or was representative of it;
that every vial in a batch is homogeneous or unchanged after testing;
that the vial was filled, labeled, sealed, transported, stored, or handled correctly;
that a Tag remained continuously attached to the same vial;
that a product is sterile, safe, effective, stable, lawful, non-toxic, uncontaminated, or fit for any purpose;
that an untested attribute meets any limit or specification;
that a product meets pharmaceutical, food, cosmetic, medical-device, clinical, compounding, or manufacturing standards; or
that the Supplier, Lab, or Buyer complied with law.

A visually matching vial or batch photo is only a comparison aid. Common packaging can be copied or reused. A visual match does not prove contents, custody, or authenticity.

3.5 Third-party COAs and Lab information

The named Lab creates and controls its COA. The Supplier is responsible for ensuring that the COA is genuine, complete, accurately associated with the batch, and submitted with the correct result. Res Labs does not adopt the Lab’s methods, conclusions, statements, or liability.

Test panels differ. A result shown as “Pass” means only the pass or similar status supplied for that record. It does not mean every possible test was performed. A COA reporting purity alone provides no result for identity, sterility, endotoxins, heavy metals, residual solvents, concentration, fill quantity, or any other omitted attribute. A statement that a Lab is “accredited” may be limited to particular facilities, methods, matrices, or scopes and may change over time.

The live document on the Lab’s independently verified domain should be reviewed first. A Res Labs archive, IPFS copy, recorded hash, or blockchain anchor can help show that a particular file or record existed in a particular form. It cannot prove that the Lab’s scientific work was accurate, that a Supplier submitted a representative sample, or that the vial in hand contains the tested material.

If a live Lab document and an archive, summary, hash, or other record differ, stop relying on the verification page and contact the Lab and Supplier. Res Labs may preserve prior versions for audit purposes and mark a current version as corrected, replaced, voided, or recalled.

3.6 NFC, cryptographic, replay, and tamper-evidence limitations

A supported NFC Tag is designed to produce authentication data that is materially harder to copy than a static QR code. A valid response is evidence that the cryptographic system accepted participation by the registered Tag or accepted data associated with it. It is not evidence that the Tag has remained on the same physical vial or that every system component is uncompromised.

The following remain possible:

a genuine Tag may be stolen, diverted, sold, or applied to an unauthorized vial;
a Supplier or other person may attach the wrong Tag to a vial;
a Tag may be moved, overlaid, transplanted, or presented separately from a vial;
tamper-evident material may fail to reveal every removal, opening, refill, substitution, or repackaging event;
a valid URL may be copied or shared, subject to counter and server controls;
phones and readers may misread, cache, fail to increment, or present incomplete data;
keys, accounts, domains, software, cloud systems, DNS, certificates, or manufacturing processes may be compromised;
implementation defects, outages, clock errors, race conditions, configuration mistakes, or third-party failures may produce a false positive, false negative, stale result, or unavailable result; and
cryptographic algorithms and hardware may become weaker or obsolete.

No person may describe the Services as “physically impossible to clone,” “impossible to fake,” “tamper-proof,” “guaranteed authentic,” or “permanent.” Accurate descriptions may state that supported Tags use dynamic cryptographic responses and counters designed to resist copying and replay, and that COA hashes or records may be anchored to provide tamper-evidence.

3.7 Meaning of common verification states

VERIFIED. The Tag and record passed the limited checks described above. It is not a verdict about chemical contents, safety, legality, chain of custody, or fitness.
CLONE_WARNING or unusual activity. The Services detected a counter, replay, geography, frequency, or other pattern that may be inconsistent with expected use. The signal may have an innocent explanation or may indicate copying, sharing, misuse, or compromise. Do not rely on the tap until the Supplier and Lab resolve it.
RECALL. The current record indicates that the batch or COA has been recalled, voided, or withdrawn. Do not rely on the prior verified state. Follow the Supplier’s recall instructions and contact the Lab.
REVOKED. Res Labs or an authorized participant disabled the Tag or record. A historical COA or blockchain anchor may remain visible, but it does not restore the Tag’s active status.
UNKNOWN. The Services could not resolve the Tag to a recognized active record. This may indicate an unissued, malformed, mistyped, damaged, counterfeit, unsupported, or not-yet-imported Tag. No product conclusion should be drawn from the page.
CONTRACT_MISMATCH. The off-chain record and expected blockchain or contract evidence did not match or could not be reconciled. Do not treat the record as verified.
INACTIVE, PENDING, or UNAVAILABLE. The Tag or record is not currently in a state that supports a verified result. Retap later only if instructed, and confirm with the Supplier and Lab.

A warning is not a laboratory result, law-enforcement finding, or final forensic conclusion. Res Labs may intentionally hide product details on a warning page to reduce leakage and misuse.

3.8 Permitted use

Subject to the Terms, you may:

tap a Tag attached to a vial in your lawful possession;
review the current Verification Record and official Lab COA;
compare the vial with displayed batch details and photos;
independently calculate and compare a document hash or blockchain anchor;
report a suspected mismatch, broken link, damaged Tag, counterfeit, recall issue, or security problem;
use accurate, unaltered verification links or approved badges to identify a current active record; and
use authorized APIs within documented limits for lawful provenance, inventory, or anti-counterfeit purposes.

3.9 Prohibited use and prohibited reliance

You may not use or rely on a Verification Record to:

decide whether to ingest, inject, inhale, implant, apply, compound, prescribe, dispense, administer, or otherwise use a Research Material in or on a person or animal;
determine a dose, reconstitution method, route, treatment plan, clinical decision, diagnosis, or medical response;
claim that Res Labs, ObjectOS, a Lab, or a blockchain verified the chemical contents of a vial;
claim that a product is safe, effective, sterile, pharmaceutical grade, human grade, approved, lawful, or suitable for consumption;
imply that every vial was individually tested;
omit a recall, warning, limitation, failed result, test omission, or material COA qualification;
associate a record with another product, vial, Supplier, batch, Lab, or document;
crop, edit, recolor, relabel, forge, simulate, or display a status or badge in a manner that obscures its source, date, current state, limitations, or link;
continue using a screenshot, cached result, or marketing claim after revocation, correction, or recall;
scrape or combine tap data to identify, profile, contact, or advertise to a Buyer;
test, probe, replay, extract, reverse engineer, or defeat a Tag or security control without prior written authorization; or
facilitate any unlawful transaction, substance, claim, shipment, or end use.

3.10 Research-use-only rule

The Services are limited to materials represented for legitimate laboratory research and analytical use. They may not be used to support human or veterinary administration, self-experimentation, clinical care, compounding, bodybuilding, weight loss, cosmetic treatment, diagnosis, therapy, prevention, or consumer wellness use.

Labels and disclaimers do not override actual conduct. A Supplier or other person violates this rule if surrounding facts show an intended prohibited use, including through product selection, targeting, testimonials, dosing or reconstitution instructions, administration supplies, customer communications, search terms, social media, or repeated sales patterns.

The Services are not an emergency service. If exposure, poisoning, injury, or an adverse event may have occurred, contact local emergency services or the appropriate poison-control authority. Do not wait for Res Labs to investigate a Tag or record.

3.11 Reporting, warnings, and recalls

Report a suspected counterfeit, mismatch, broken COA source, misleading claim, security issue, or recall concern through the available reporting function or at info@reslabs.ai. Provide the verification URL or tap identifier, Tag identifier if visible, Supplier and batch information, approximate tap time, a description, and supporting images or documents where lawful.

A report is an allegation, not proof. Res Labs may share it with the relevant Supplier, Lab, service providers, insurers, advisers, or authorities as described in the Privacy Policy. Res Labs may preserve evidence, restrict access, hide details, flag a record, suspend an account, revoke Tags, or take no action while investigating.

A Supplier remains responsible for directly notifying its customers, regulators, carriers, distributors, and other affected persons of a product correction, withdrawal, or recall. A Res Labs warning page is supplemental and is not a substitute for a legally adequate recall program.

3.12 Tap data and privacy

A public verification page does not require a buyer account or email. It does require server-side processing of technical data. Each attempted tap may create an append-only event containing the Tag or sticker identifier, tap counter, timestamp, IP address, country-level geolocation, optional approximate city or region, user agent, result, and anomaly indicators.

Res Labs uses this data to authenticate the request, reject replay, detect possible cloning or abuse, secure the Services, investigate incidents, preserve audit evidence, and produce limited operational analytics. This data is not fully anonymous because IP addresses, precise timing, or combinations of technical details may relate to a person. The Privacy Policy explains legal bases, recipients, retention, international transfers, and rights.

Do not tap a Tag if you do not want the verification request and necessary technical data transmitted to Res Labs. A person may instead review a COA directly with the Supplier or Lab, but Res Labs cannot authenticate a Tag without receiving the tap request.

3.13 Enforcement and changes

Res Labs may block traffic, rate-limit access, suspend accounts, disable APIs, revoke Tags or records, remove badges, contact a Lab, preserve evidence, or report suspected unlawful conduct. Enforcement may occur without advance notice where necessary for security, legal compliance, fraud prevention, a recall, or protection of third parties.

Res Labs may update supported Tag technologies, verification methods, statuses, risk thresholds, Lab-domain rules, archive providers, blockchain systems, or this disclaimer. No earlier marketing statement, interface label, sales conversation, or technical description expands the limited meaning of verification stated here.

3.14 Warranty and liability reminder

Verification pages and Verification Records are provided on an “as is” and “as available” basis. The warranty disclaimers, limitation of liability, dispute provisions, and other protections in the Terms of Service apply to this disclaimer and every use of a verification page. Where this disclaimer conflicts with promotional copy, the Terms and this disclaimer control.