Terms of Service

Commercial and operational terms for Age Verify

Effective date: March 13, 2026. These terms govern platform usage, billing behavior, and operational responsibilities for merchant customers.

1. Agreement and eligibility


These Terms govern your use of the Age Verify platform, APIs, SDK, and related services. By using the service, you represent you have authority to bind your organization.

2. Service scope


Age Verify provides age-assurance workflows and related APIs for age-gated access decisions. Unless explicitly stated otherwise, the service is not a document verification, named-person identity verification, or general KYC product. Age Verify provides age verification workflows, verification APIs, SDK tooling, integrator portal authentication, onboarding, resource delivery workflows, and merchant billing infrastructure. Age Verify does not provide legal advice and does not guarantee legal compliance outcomes.

3. Account and key security


You are responsible for account access controls, API key storage, credential rotation, password protection, and all actions taken using your credentials. Secret keys must remain server-side, and you must protect reset tokens and authentication endpoints against unauthorized use.

4. Fees, usage, and billing


Fees are usage-based and billed on successful verification events according to the published pricing schedule. Fees are non-refundable by default, net of taxes, and charged through your configured merchant payment method.

5. Billing status and service gating


Verification processing may be restricted when billing status is not active or when no default payment method is available. You are responsible for maintaining valid billing configuration and resolving payment failures promptly.

6. Acceptable use


You may not misuse the service, attempt unauthorized access, interfere with platform integrity, or use the service for unlawful, discriminatory, or abusive activity.

7. Website forms and communications


If you submit or collect data through Age Verify-hosted lead, demo, onboarding, or resource request forms, you agree that the submitted data may be used for onboarding, requested asset delivery, support follow-up, and account operations in accordance with the Privacy Policy.

8. Compliance responsibilities


Customer is responsible for determining whether age assurance is sufficient for its use case and whether any workflow requires additional identity verification, KYC, or other legally mandated controls. You are responsible for determining legal requirements in your jurisdictions and implementing required notices, consent, and policy controls in your product, including age-gate disclosures and any obligations tied to your deployment context.

9. Data processing and privacy


Data handling is described in the Privacy Policy and any applicable data processing addendum. Clients may opt in to reusable verification across participating properties, and any such use remains subject to applicable law, contractual settings, and client controls. You remain responsible for lawful data collection and downstream use in your own systems.

10. Intellectual property


Age Verify retains all rights in the platform, SDK, APIs, and documentation. Subject to these Terms, you receive a limited, non-exclusive, non-transferable license to use the service for internal business purposes.

11. Availability and changes


Features may be modified, improved, or deprecated over time. Unless otherwise agreed in writing, the service is provided on an as-is and as-available basis.

12. Suspension, termination, and liability


We may suspend or terminate access for non-payment, security risk, legal requirement, or material breach. To the maximum extent permitted by law, liability for indirect or consequential damages is excluded, and aggregate liability is limited to fees paid in the prior twelve months.

13. Updates and contact


We may update these Terms with a new effective date. Continued use after updates constitutes acceptance. Legal and compliance inquiries should be sent through your account support channel.

How to apply these terms operationally

These terms are structured to reduce ambiguity between legal language and platform operations. Teams should review them with product, engineering, and finance owners before launch so obligations are translated into concrete controls.

Fee and billing clauses are especially important for rollout planning. Teams should know when verification traffic can be restricted by billing state and how recovery workflows are communicated to support and customer success.

If your organization requires additional contractual controls, use these terms as the baseline and map changes explicitly to internal owners. Clear ownership of contractual exceptions reduces implementation drift over time.

Contract operations notes

  • Align contract terms with internal runbooks before launch so obligations are operationalized, not only documented.
  • Revisit billing and suspension clauses during expansion to new geographies or higher-risk product surfaces.
  • Track approved contractual exceptions in a central record used by legal, finance, and engineering leads.