Terms of Service
Terms of Service — ZeroTrust
Version: 2026-11-02 · Effective: November 2, 2026 · Supersedes: Version 2026-10-01
This document is versioned by its effective date. Every superseded version remains available at
zerotrust.entrinsia.com/legal/terms/<version>permanently. Changes are listed in the Revision History at the end.
These Terms of Service ("Terms") are a binding agreement between Entrinsia Inc. ("Entrinsia," "we," "us," or "our") and the person or entity accessing or using ZeroTrust (the "Customer," "you," or "your"). They govern your access to and use of ZeroTrust, including our website, APIs, verification workflows, server endpoints, Documentation, merchant plugins, and administrative interfaces (collectively, the "Service").
By creating an account, subscribing via AWS Marketplace, installing or deploying our integration plugins, calling our APIs, or otherwise accessing or using the Service, you agree to these Terms. If you are agreeing on behalf of a company, partnership, or other legal entity, you represent and warrant that you have authority to bind that entity, and "you" and "your" refer to that entity. If you do not have such authority or do not agree, do not use the Service.
Our collection and handling of personal data is described in our Privacy Policy. Our obligations to you as a processor of End User personal data are set out in our Data Processing Addendum ("DPA"), which is incorporated into these Terms by reference and forms an integral part of them.
1. Definitions
- "End User" means an individual whose identity, age, or credential is submitted for verification through the Service in connection with your websites, applications, storefronts, or business workflows.
- "Verification Session" means one attempt by an End User to complete identity, document, or age verification through the Service, as defined in Section 6 and billed under Section 4.
- "Verification Result" means the outcome data the Service returns or makes accessible to you following a Verification Session, for example a pass or fail flag, an age-over-threshold assertion, matched attributes, or an audit reference key.
- "Your Data" means data you submit to the Service in configuring or operating your account, such as domain registrations, configuration settings, administrative settings, and billing information. End User personal data is addressed separately in Section 9, the Privacy Policy, and the DPA.
- "Merchant Plugin" means the ZeroTrust integration plugin we distribute for a commerce platform, including the WooCommerce plugin, as described in Section 12.5.
2. The Service
ZeroTrust verifies a government-issued ID and confirms, through a live selfie, that the person submitting the ID is the person depicted on it and is physically present. Based on your configuration, ZeroTrust returns a Verification Result to you, which may be as simple as a pass or fail flag, or may include specific data fields extracted from the ID.
2.1 What ZeroTrust Is
A tool for real-time document authentication, selfie-based liveness detection, facial match comparison, and age validation, supporting United States state driver's licences and state-issued non-driver identification cards, as described in our Documentation. Where enabled for your account, ZeroTrust may also accept a mobile driver's licence or other digital identity credential presented from a device wallet, subject to these same Terms.
2.2 What ZeroTrust Is Not
- Not full "Know Your Customer" (KYC) or AML compliance. The Service is not configured to satisfy statutory Anti-Money Laundering or Customer Identification Program requirements under the Bank Secrecy Act, or similar obligations in banking, money transmission, or cryptocurrency. In particular, and as described in Sections 9.5 and 9.6, we do not retain plaintext street addresses, complete dates of birth, or full unhashed government ID numbers. If your business requires traditional KYC recordkeeping, the Service will not satisfy your regulatory requirements on its own. Contact us before relying on it for that purpose.
- Not legal advice, and not a compliance guarantee. Using the Service does not, by itself, ensure compliance with any law applicable to your business, including age-restricted commerce statutes such as California AB 1263, privacy laws, or industry-specific regulations. See Section 8.
- Not infallible. Automated biometric and document verification operates on probabilistic models and is subject to false positives, false negatives, image distortion, and evolving spoofing methods. See Section 11.
3. Eligibility and Accounts
3.1 Business Use Only
The Service is intended for use by businesses and other organisations verifying their own End Users, not for personal, non-commercial use.
3.2 Account Registration and Credential Safeguards
To use the Service, you must register an account, register every storefront domain from which you will call the Service, and provide accurate account and billing information. You must maintain strict confidentiality of your account credentials, API keys, and webhook signing secrets. You are responsible and liable for all activity and billing incurred under your credentials, whether or not authorised by you.
3.3 Notify Us of Unauthorized Use
You will notify us promptly at support@entrinsia.com if you become aware of any unauthorised access to or use of your account or credentials.
4. Fees and Payment
4.1 Pricing
The Service is billed on a per-Verification-Session basis at the rate published at zerotrust.entrinsia.com/#pricing at the time of your subscription, currently $0.60 per billable Verification Session, unless you have a separate signed agreement or an AWS Marketplace subscription specifying different pricing. Pricing for usage exceeding 10,000 Verification Sessions per month is available by contacting us.
4.2 Billing Method
You may pay either (a) directly, with Entrinsia invoicing you or charging a payment method on file, generally monthly in arrears for the prior month's usage, or (b) through AWS Marketplace, in which case billing is also subject to your AWS Marketplace agreement. Where AWS Marketplace's billing terms conflict with these Terms, AWS Marketplace's terms govern billing mechanics, while these Terms continue to govern your use of the Service itself.
4.3 What You're Billed For
You are billed for each billable Verification Session initiated through your account, as defined in Section 6, regardless of whether the result is a pass, a fail, or an abandonment after capture has begun.
4.4 Free Verifications
New accounts receive a set number of free Verification Sessions, currently 50, as described at the time of sign-up. Free Verification Sessions are tracked and deducted automatically before billable invoicing, and are subject to these Terms in all other respects.
4.5 No Refunds
Fees for billable Verification Sessions are non-refundable, except as required by law, as provided in Sections 5.4, 6.6, and 16, or as we otherwise agree in writing.
4.6 Taxes
Fees are exclusive of applicable taxes. You are responsible for any sales, use, VAT, or similar transaction taxes associated with your use of the Service, other than taxes on Entrinsia's net income.
4.7 Late Payment
Amounts not paid when due, for direct billing arrangements, may accrue interest at the lesser of 1.5% per month or the maximum rate permitted by law, and we may suspend the Service for non-payment after notice.
5. Term, Cancellation, and Suspension
5.1 Term
These Terms commence on your initial access to or registration for the Service and remain in effect for as long as you maintain an account or otherwise use the Service.
5.2 Cancellation
You may cancel your account at any time through your account settings, your AWS Marketplace subscription, or by contacting us. Cancellation takes effect at the end of the then-current billing period. There are no cancellation penalties, but fees already incurred remain payable.
5.3 Suspension
We may suspend or restrict your access to the Service or your API keys, with notice where reasonably practicable, if (a) you fail to pay amounts due, (b) we reasonably believe your use violates Section 7, compromises system stability, or indicates malicious circumvention, (c) we detect a severe security vulnerability or fraud affecting your integrated domains, (d) we are required to act to comply with law or a judicial, regulatory, or governmental request, or (e) continued provision of the Service to you would expose us to liability we reasonably consider unacceptable.
5.4 Termination
Either party may terminate these Terms for the other party's uncured material breach, by giving written notice identifying the breach and allowing thirty (30) days to cure; termination takes effect at the end of that period if the breach remains uncured. Either party may terminate immediately if the other becomes insolvent or ceases operating in the ordinary course. We may also terminate for convenience on thirty (30) days' notice, in which case we will refund any prepaid, unused fees for future service.
5.5 Effect of Termination
Upon termination, your right to access the Service ends and any amounts owed to us become immediately due.
Within thirty (30) days after termination, Entrinsia will delete Your Data and any End User verification data associated with your account, except for (a) compliance records that remain within their retention period under the Privacy Policy, which we retain so that you or we can evidence that verifications occurred, and (b) records we are required by law to retain. On written request made before termination takes effect, we will provide you with an export of the compliance records associated with your account in a machine-readable format.
Sections that by their nature should survive termination, including Sections 1, 4, 8, 9, 10.3, 11, 12, 13, 14, 15, 16, 17, 19, and 20, will survive.
6. Verification Sessions
6.1 Definition
A Verification Session is a single attempt by one End User to complete verification through your account. It begins when the verification flow is opened and ends when it returns a pass or fail result, is abandoned, or expires.
6.2 When a Session Becomes Billable
A Verification Session becomes billable at the moment an image, video stream, or credential payload is first submitted to our servers or processing endpoints. An End User who opens the verification flow and leaves without submitting anything does not create a billable Verification Session.
6.3 One Session
The following count as a single billable Verification Session:
- Repeated attempts by the same End User against the same order, cart, or transaction reference within sixty (60) minutes of the first submission, where each repeat follows a failed capture rather than a completed outcome. A failed capture means no definitive verdict was reached — for example an unreadable or distorted image, a liveness check that could not be assessed, or a network interruption.
- A verification begun on one device and completed on another through our QR code or device handoff, against the same reference.
6.4 Separate Sessions
The following count as separate billable Verification Sessions:
- An attempt against a different order, cart, or transaction reference;
- A further attempt by the same End User more than sixty (60) minutes after the first submission for that reference; or
- A further attempt made after a completed outcome — that is, after the Service has returned a definitive pass or fail verdict — where your configuration permits the End User to try again.
For the avoidance of doubt, the distinction between Sections 6.3 and 6.4 is whether a definitive verdict was returned, not whether the End User succeeded. Retrying after an unreadable image inside the window is one session; retrying after a returned "fail" verdict is a new one.
6.5 Billed Regardless of Outcome
You are billed for each billable Verification Session whether it results in a pass, a fail, or an abandonment after capture has begun. A failed session has performed the Service's function by identifying a non-matching or fraudulent attempt.
6.6 Changes to This Section
We may change this Section on thirty (30) days' notice. If a change would increase the number of Verification Sessions billed for the same volume of End User activity, you may terminate without penalty before it takes effect, and the refund provision in Section 5.4 applies.
7. Acceptable Use
You will not, and will not permit or authorise any third party to:
- Use the Service for any unlawful purpose, or to facilitate fraud, discrimination, or harassment;
- Use the Service to verify an individual without that individual's knowledge where such knowledge is legally required, or inconsistently with the notice and consent obligations in Section 8;
- Reverse engineer, decompile, trace, or extract the underlying models, algorithms, neural networks, or biometric processing techniques used by the Service, subject to Section 12.5;
- Interfere with, bypass, or probe rate limiters, server authentication, or session validation barriers, other than through a good-faith, coordinated disclosure process;
- Submit synthetic, deepfake, or spoofed images or credentials to benchmark or systematically test Service accuracy without our prior express written approval;
- Introduce malware, or interfere with or disrupt the integrity or performance of the Service;
- Scrape, mirror, or republish Service components or Documentation, subject to Section 12.5;
- Use the Service to build a directly competing product or service, or to benchmark the Service publicly without our prior written consent;
- Exceed reasonable rate limits or attempt to bypass usage-based billing; or
- Call the Service from unregistered or deceptive domains, or misrepresent your identity, your business, or the domains you are authorised to call from.
We may investigate and take appropriate action, including suspension under Section 5.3, for suspected violations of this Section.
8. Your Compliance Responsibilities
This section is important, and we want to be direct about it.
8.1 You Are Responsible for Your Own Compliance
You are solely responsible for determining whether, and how, your use of the Service satisfies any law, regulation, or industry requirement applicable to your business, including age-verification statutes such as California AB 1263 or similar laws in other states, general privacy laws such as the CCPA and the GDPR, and biometric privacy laws such as BIPA. Entrinsia is not a law firm, does not provide legal advice, and nothing in the Service, our Documentation, our marketing materials, or any communication from us should be construed as legal advice or a guarantee of compliance. You should consult your own legal counsel regarding your specific obligations.
8.2 Order Fulfillment and Server-Side Verification
Pre-fulfillment obligation. Before releasing, fulfilling, or shipping any order subject to age-verification or identity laws, including California AB 1263, you must confirm that a passing Verification Result covering that order exists on Entrinsia's server systems. Our records are the authoritative source for that confirmation. You may make it through the Merchant Plugin's administrative screens or through our authenticated APIs, as described in Section 10.
A record covers an order if the Service associates it with that order's reference, or with the cart or transaction reference from which that order was created. Where the Service holds a passing Verification Result that it has not associated with the order — for example where recording the association did not complete — you must resolve the discrepancy through the administrative screens or with our support before fulfilling the order. You must not infer coverage from the fact that a verification occurred at around the same time.
No reliance on client-side indicators. You must not treat storefront interface elements, DOM state, browser redirects, front-end JavaScript callbacks, or local browser storage as evidence that a verification occurred or passed.
Circumvention and tampering. You acknowledge that browser-executed interfaces and client scripts run on End User-controlled devices and can be bypassed, modified, spoofed, or blocked. Implementing server-side enforcement in your own systems — including honouring the order holds the Merchant Plugin applies, and not releasing a held order until the Service shows it verified — is your responsibility.
Absence of record. Any order for which no passing Verification Result exists on our server systems is unverified for the purposes of these Terms, regardless of what your storefront interface permitted or displayed, and regardless of any indication an End User may have seen.
8.3 Notice and Consent to End Users
ZeroTrust displays a biometric notice to every End User before it requests camera access, and requires the End User to accept that notice before any image or video is captured. The notice is described in Section 9.3 of our Privacy Policy. It covers the biometric processing that ZeroTrust itself performs. We retain a record of each acceptance, including the version of the notice shown and the time of acceptance, and will make that record available to you on request for verifications run under your account.
That notice does not, and is not intended to, satisfy every notice or consent obligation that applies to you. You remain responsible for providing End Users with any notice, and obtaining any consent or written release, that applicable law requires of you. This includes any disclosure specific to your industry or jurisdiction, any disclosure required by the age-verification statute you are relying on, and any written release required of you as the party collecting biometric identifiers under a state biometric privacy statute.
If you are uncertain whether the notice built into ZeroTrust is sufficient for your circumstances, you should assume that it is not, and obtain your own.
8.4 Use of Verification Results
You are responsible for how you use, store, and act on Verification Results after we return them to you, including any further retention obligations that apply once data is in your possession. Our own retention practices are described in the Privacy Policy and do not extend to data you separately store.
8.5 Age Thresholds and Document Types
You are responsible for configuring the correct age threshold and accepted document types for your use case, and for confirming that configuration meets your legal requirements.
9. Data Protection
9.1 Roles
With respect to End User verification data, Entrinsia acts as a processor (and "service provider" under the CCPA/CPRA) and you act as the controller (and "business"). We process that data only on your documented instructions, which for these purposes comprise these Terms, the DPA, and the configuration you set for your account. Entrinsia will not "sell" or "share" End User personal information, and will not retain, use, or disclose it outside the business relationship governed by these Terms.
9.2 Biometric Processing Commitments
Entrinsia does not sell, lease, or trade biometric identifiers. Biometric templates generated during liveness checking and facial comparison are processed ephemerally in volatile memory and deleted immediately after comparison. What is retained is the outcome and the audit metadata described in Section 9.5.
9.3 Processing Addendum and Privacy Policy
Our obligations as a processor are set out in the DPA at zerotrust.entrinsia.com/legal/dpa, which is incorporated into these Terms by reference. Where the DPA and these Terms conflict in respect of the processing of personal data, the DPA controls.
Our collection, use, retention, and deletion of data is described in our Privacy Policy. We will not make a change that materially reduces the protections applying to End User data already collected under your account without giving you prior notice, and where such a change would materially reduce those protections going forward we will give you at least thirty (30) days' notice before it takes effect.
9.4 Breach Notification
We will notify you in writing without undue delay, and in any event within seventy-two (72) hours of confirming, any unauthorised access to or acquisition of, or other security breach compromising, End User personal data processed for you. We will provide reasonable cooperation and the incident details you reasonably require in order to meet your own notification obligations.
9.5 Verification Metadata and Audit Records
To maintain audit integrity, prevent and detect fraud, defend against transaction repudiation, and allow you to evidence compliance with statutory requirements such as California AB 1263, the Service retains specific verification records. These purposes are business purposes for which a service provider may retain and use personal information, and we do not use these records for any other purpose. You authorise Entrinsia to store:
- Timestamps of session initiation, biometric consent, capture completion, and final result;
- The verification outcome — pass, fail, abandoned, or a specific fraud flag;
- The End User's extracted name and the age-over-threshold determination;
- Your transaction references, including order, cart, and store references, and our internal session reference;
- Client device network and security telemetry, including the desktop IP address, the mobile handoff IP address, and browser user-agent headers;
- Non-reversible cryptographic HMAC hashes derived from document and address fields, including a document number hash, a name key, and an address key, generated using isolated server-side keys that are not exposed to you or to End Users; and
- The version and timestamp of the biometric notice and disclosure the End User acknowledged.
9.6 Transient Address Processing
Where your integration requires consistency between the address on a government ID and the address on a merchant order, the Service may temporarily hold ID address components server-side, in an isolated and encrypted transient state, for the purpose of populating and validating checkout fields. You acknowledge and agree that:
- Such data is processed strictly in-flight to permit that population and validation;
- It is wiped on generation of the final verification outcome or on session termination; and
- Entrinsia does not persist plaintext street addresses, complete dates of birth, or raw ID numbers in its long-term audit records.
10. Service Delivery and Availability
10.1 Interface Availability
Reporting, verification status, and audit records are delivered through the Merchant Plugin's administrative screens and through our authenticated REST APIs. Supplementary web management portals, reporting exports, and features labelled "Beta" or "Coming Soon" are provided as available and do not form an operational warranty.
Verification outcomes are delivered via API responses, synchronous plugin hooks, or authenticated server-to-server webhooks where configured and supported. You are responsible for properly handling timeouts, retries, and asynchronous delivery states in your own architecture.
10.2 Target Availability and Fallback
We target 99.9% monthly uptime for the Service's API and verification flow, excluding scheduled maintenance, for which we will provide advance notice where practicable, and events outside our reasonable control (see Section 18). We will notify affected Customers of significant disruptions by email or through the Service. This target is an operational goal, not a binding service-level guarantee, unless you have a separate signed agreement that includes a specific SLA with associated remedies.
You are responsible for configuring appropriate fallback behaviour in your own systems for periods when the Service is unavailable — for example queuing verifications, routing to manual review, or holding orders — consistent with your obligations under Section 8. Nothing in this Section relieves you of the pre-fulfillment obligation in Section 8.2: an outage is not a basis for releasing an unverified order.
10.3 Security and Compliance Documentation
Upon reasonable written request, no more than once per calendar year, Entrinsia will provide an executive summary of then-available third-party security audit reports, such as a SOC 2 report if and when obtained, or other compliance documentation reasonably requested to support your own compliance review. This Section applies to Customers with a current subscription, and to prospective Customers evaluating the Service under a mutual non-disclosure agreement. Any such materials are Confidential Information under Section 13 and may be shared only with your personnel and advisors who need them for that purpose. This Section does not obligate Entrinsia to obtain any particular certification or audit.
11. Disclaimers
THE SERVICE, INCLUDING ALL INTEGRATIONS AND VERIFICATION RESULTS, IS PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT.
Without limiting the foregoing, we do not warrant that:
- The Service will be uninterrupted, timely, error-free, or secure;
- Any Verification Result will be accurate in every instance. Identity verification and liveness detection technology, including ours, can produce false positives and false negatives, and a pass result is not a guarantee that a submitted document or selfie is genuine;
- The Service will detect every instance of fraud, document forgery, deepfake, or spoofing; or
- The Service satisfies the specific legal or regulatory requirements applicable to your business, including California AB 1263 or other age-verification statutes. You bear exclusive responsibility for your compliance posture (see Section 8).
12. Intellectual Property
12.1 Our IP
The Service, including its underlying software, models, Documentation, and branding, is owned by Entrinsia or our licensors and protected by intellectual property laws. Subject to your compliance with these Terms, we grant you a limited, non-exclusive, non-transferable, revocable licence to access and use the Service during the term of these Terms, solely for your internal business purposes.
12.2 Your IP and Your Instructions
You retain all rights to Your Data and to your own website, application, and branding. You grant us a limited licence to use Your Data solely as necessary to provide the Service to you. You instruct us to process End User personal data as necessary to perform verifications for you and to meet our obligations under these Terms and the DPA, and you represent that you have authority to give that instruction.
12.3 Feedback
If you provide feedback or suggestions about the Service, we may use them without restriction or obligation to you.
12.4 No Model Training
Entrinsia will not use Your Data, End User ID images, video selfies, biometric data, or any data extracted from an ID to train or improve any machine learning model, whether our own or a third party's. Our agreements with the cloud processing providers described in Section 16 impose the same restriction on them, including a prohibition on using verification payloads to train public or foundational models. We may use aggregated, de-identified operational metrics, such as error rates, processing latency, and step completion rates, to improve the Service.
12.5 Merchant Plugins, Licensing, and Updates
Open-source licence. The WooCommerce Merchant Plugin is distributed under the GNU General Public License, version 2 or later ("GPLv2"). Where GPLv2 applies, its terms govern your rights in that plugin's source code and prevail over any conflicting restriction in these Terms. In particular, the restrictions in Section 7 on reverse engineering, decompiling, and republishing do not apply to the Merchant Plugin to the extent GPLv2 grants those rights. They continue to apply in full to the hosted Service, our APIs, our models, and our Documentation, none of which are licensed under GPLv2.
Updates. We may make updates to the Merchant Plugin available through an Entrinsia-operated update service, and your WordPress or commerce platform may offer or install them. You consent to that delivery mechanism. Where we identify a release as necessary to correct a defect affecting security or the integrity of compliance records, we may deliver it as a mandatory update that installs without further action by you. We will not use this mechanism to disable your checkout or to withhold the Service from an out-of-date installation.
Your responsibility for your environment. You remain responsible for your own hosting environment, for backups, and for testing updates against any customisations you have made. If you have modified a Merchant Plugin, Section 14.2 does not apply to the modified version.
13. Confidentiality
Each party may have access to the other's non-public business, technical, or financial information ("Confidential Information"). Each party agrees to use the other's Confidential Information only to perform its obligations under these Terms, and to protect it using at least the same degree of care it uses for its own confidential information of similar importance, but no less than reasonable care. This Section does not apply to information that is or becomes public through no fault of the receiving party, was already known to the receiving party without restriction, or is independently developed. Either party may disclose Confidential Information as required by law, provided it gives the other party reasonable notice where legally permitted.
14. Indemnification
14.1 Your Indemnification of Entrinsia
You will defend, indemnify, and hold harmless Entrinsia and its parent, affiliates, officers, directors, employees, and agents from and against any third-party claims, regulatory actions, fines, penalties, damages, liabilities, costs, and expenses, including reasonable attorneys' fees, arising out of or related to:
- Your actual or alleged non-compliance with any law applicable to your use of the Service, including consumer protection, age-verification, or privacy laws;
- Your failure to provide required notice or obtain legally sufficient consent or written release from End Users;
- Your release, fulfillment, or shipment of any order subject to verification for which no passing Verification Result was confirmed on our systems, including any bypass or circumvention scenario described in Section 8.2;
- Your use of Verification Results, including decisions, order denials, or cancellations made or not made based on a Verification Result;
- Your Data or your instructions to us; or
- Your violation of these Terms or of Section 7.
14.2 Our Indemnification of You
We will defend, indemnify, and hold you harmless from third-party claims that the Service, as provided by us and used in accordance with these Terms, infringes a third party's United States patent, copyright, or trademark rights, and will pay damages finally awarded by a court of competent jurisdiction, subject to Section 15. This obligation does not apply to claims arising from (a) modification of the Service or a Merchant Plugin by anyone other than Entrinsia, (b) combination of the Service with products or applications not provided by us, (c) your use of the Service in violation of these Terms, or (d) your continued use of an infringing version after we have made an updated non-infringing release available.
14.3 Process
The indemnified party will promptly notify the indemnifying party of any claim, give the indemnifying party control of the defence and settlement — except that any settlement requiring the indemnified party to admit fault or take affirmative action must be approved by the indemnified party — and provide reasonable cooperation at the indemnifying party's expense. A delay in notice relieves the indemnifying party only to the extent it is prejudiced by the delay.
15. Limitation of Liability
15.1 Exclusion of Certain Damages
TO THE FULLEST EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST REVENUE, LOSS OF DATA, LOSS OF GOODWILL, OR BUSINESS INTERRUPTION, ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICE, REGARDLESS OF THE THEORY OF LIABILITY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Without limiting the foregoing, Entrinsia is not liable for statutory fines, civil penalties, or regulatory enforcement actions assessed against you, for merchant account terminations, for the costs of any recall, credit monitoring, or breach notification you undertake, or for damages arising from your failure to satisfy your responsibilities under Section 8.
15.2 Liability Cap
TO THE FULLEST EXTENT PERMITTED BY LAW, EACH PARTY'S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS WILL NOT EXCEED THE GREATER OF (A) THE FEES YOU PAID TO ENTRINSIA IN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM, OR (B) ONE THOUSAND DOLLARS ($1,000).
15.3 Exceptions
The limitation in Section 15.2 does not apply to: (a) your indemnification obligations under Section 14.1; (b) your payment obligations under Section 4; (c) either party's breach of Section 13; or (d) either party's gross negligence, willful misconduct, or fraud.
Entrinsia's indemnification obligations under Section 14.2 are not subject to Section 15.2, but are subject to a separate aggregate cap equal to the greater of (i) three (3) times the fees you paid to Entrinsia in the twelve (12) months preceding the first claim under Section 14.2, or (ii) fifty thousand dollars ($50,000).
15.4 Basis of the Bargain
The parties acknowledge that the fees charged for the Service reflect the allocation of risk in this Section 15, and that this allocation is an essential basis of the parties' agreement.
16. Third-Party Services and Subprocessors
The Service relies on third-party infrastructure and AI processing providers, currently Amazon Web Services, Inc., to perform document authentication, liveness detection, and facial comparison, under contract terms consistent with those described in our Privacy Policy and the DPA. We are not responsible for the availability or performance of third-party services outside our control, except to the extent caused by our failure to properly configure or maintain our use of them.
We maintain a current list of the subprocessors that process End User personal data at zerotrust.entrinsia.com/legal/subprocessors. We will give you at least thirty (30) days' notice before adding or replacing a subprocessor that processes End User personal data. If within that period you object on reasonable data protection grounds, and we cannot make available a commercially reasonable alternative, you may terminate the affected portion of the Service without penalty and receive a refund of any prepaid, unused fees. We impose on each subprocessor obligations no less protective than those in the DPA, and we remain responsible to you for each subprocessor's performance.
17. Export Control
The Service may be subject to US export control and economic sanctions laws. You represent that you are not located in, or a national or resident of, any country subject to a US embargo, and are not on any US government restricted-party list. You will not use the Service in violation of applicable export control or sanctions laws.
18. Force Majeure
Neither party is liable for any failure or delay in performance, other than payment obligations, resulting from causes beyond its reasonable control, including natural disasters, war, terrorism, labour disputes, internet or utility failures, acts of government, or failures of third-party infrastructure providers such as AWS.
19. General Provisions
19.1 Governing Law and Venue
These Terms are governed by the laws of the State of Delaware, without regard to conflict of laws principles. For any dispute not subject to arbitration under Section 20, the parties consent to the exclusive jurisdiction and venue of the state and federal courts located in Santa Clara County, California, and waive any objection to venue there.
19.2 Modifications to These Terms
We may update these Terms from time to time. For material changes, we will provide notice through the Service, by email, or by publishing a new version with a new effective date, at least thirty (30) days before it takes effect. Continued use of the Service after changes take effect constitutes acceptance. If you do not agree to updated Terms, your remedy is to stop using the Service and cancel your account; where a change materially and adversely affects you, you may terminate without penalty before it takes effect and receive a refund of any prepaid, unused fees. A change to Section 6 is additionally subject to Section 6.6.
19.3 Modifications to the Service
We may modify, update, or discontinue features of the Service from time to time. We will provide reasonable advance notice of any change that materially reduces core functionality you rely on, where practicable. Updates to Merchant Plugins are addressed in Section 12.5.
19.4 Assignment
You may not assign these Terms without our prior written consent, except to a successor in a merger, acquisition, or sale of substantially all assets, provided the successor is not a direct competitor of Entrinsia. We may assign these Terms without restriction. Any attempted assignment in violation of this Section is void.
19.5 Notices
We may provide notice to you via the email address associated with your account or through the Service. You may provide notice to us at legal@entrinsia.com or support@entrinsia.com, or in writing to the address in Section 21. Notice is effective on receipt, or on the business day after sending if sent by email to a current address.
19.6 Severability
If any provision of these Terms is held unenforceable, the remaining provisions remain in full force and effect, and the unenforceable provision will be modified to the minimum extent necessary to make it enforceable.
19.7 No Waiver
Failure to enforce any provision of these Terms is not a waiver of the right to enforce it later.
19.8 Entire Agreement and Order of Precedence
These Terms, together with the Privacy Policy, the DPA, your registration details, and any Documentation incorporated by reference, constitute the entire agreement between you and Entrinsia regarding the Service, and supersede any prior agreements on the same subject matter. A separately signed written agreement between you and Entrinsia, such as a negotiated subscription agreement or enterprise order form that expressly references these Terms, will control to the extent of a direct conflict.
19.9 Relationship of the Parties
The parties are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency, or employment relationship.
20. Dispute Resolution and Arbitration
20.1 Agreement to Arbitrate
Except for claims that may be brought in small claims court, and except as provided in Section 20.3, you and Entrinsia agree that any dispute, claim, or controversy arising out of or relating to these Terms or the Service, including its interpretation, scope, or breach, will be resolved exclusively through final and binding arbitration rather than in court, on an individual basis.
20.2 Class Action Waiver
YOU AND ENTRINSIA AGREE THAT EACH MAY BRING CLAIMS AGAINST THE OTHER ONLY IN AN INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS, CONSOLIDATED, OR REPRESENTATIVE PROCEEDING.
20.3 Exceptions
Either party may bring an individual action in court, or seek emergency injunctive or provisional equitable relief in any court of competent jurisdiction in Santa Clara County, California, to prevent irreparable harm or to address actual or threatened infringement, misappropriation, or violation of a party's intellectual property or confidentiality rights.
20.4 Procedure
Unless a separately signed order form or enterprise agreement designates a different administrator, arbitration will be administered by JAMS under its Comprehensive Arbitration Rules and Procedures then in effect. The arbitration will be seated in Santa Clara County, California, conducted in English, and governed by the substantive law specified in Section 19.1.
20.5 End Users Are Not Parties
End Users are not parties to these Terms. Nothing in this Section 20 limits any right of an End User, and no End User is required by these Terms to arbitrate any claim. As between you and Entrinsia, claims brought by an End User arising from your notice or consent practices, or from your use of a Verification Result, are allocated by Sections 14 and 15.
21. Contact Information
If you have questions about these Terms, contact us at:
Email: legal@entrinsia.com / support@entrinsia.com
Mail: Entrinsia Inc. 559 S El Monte Ave Los Altos, CA 94022
These Terms apply specifically to ZeroTrust. Other Entrinsia products, such as MementoBook, are governed by their own terms of service. If you have a separately signed subscription agreement with Entrinsia for ZeroTrust that conflicts with these Terms, that agreement controls.
Revision History
Every published version of this document remains available at zerotrust.entrinsia.com/legal/terms/<version>.
| Version | Effective | Summary of changes |
|---|---|---|
| 2026-10-01 | October 1, 2026 | Initial publication. |
| 2026-11-02 | November 2, 2026 | Added the pre-fulfillment server verification requirement and client-side bypass disclaimers (Section 8.2), including how a verification record is matched to an order and what to do when it is not. Enumerated the audit metadata retained and restated it as service-provider business purposes (Section 9.5). Authorised transient address processing for checkout (Section 9.6). Added plugin licensing and update terms, including the GPLv2 carve-out from the acceptable-use restrictions and consent to mandatory compliance updates (Section 12.5). Resolved an ambiguity in session billing between failed captures and completed outcomes (Sections 6.3-6.4). Referenced pricing to the published pricing page rather than fixing it in these Terms (Section 4.1). Added breach notification commitments (Section 9.4). |