Legal · Authvio

Terms of Service

The rules for Authvio accounts, verification, developer services, connected applications, and supported global or regional use.

Last updated: July 18, 2026 · A brand of Bolrach Technologies Limited

On this page

1. Agreement to these terms

These Terms govern Authvio accounts, sign-in, identity verification, developer-console, API, webhook, organization, and related services. Authvio is a brand of Bolrach Technologies Limited, which is the entity providing the service.

By creating an account or using the service, you agree to these Terms and the policies linked from them. If you act for a company or another legal entity, you confirm that you may bind it to these Terms.

2. Countries and service availability

Authvio is designed for supported global and country-specific use. Features may differ by country, verification level, provider availability, data-region readiness, developer approval, and law. Selecting Global coverage does not promise that every verification method is available in every country. A country or capability may stay disabled until the required storage, licensing, provider, or review path is ready.

3. Eligibility

You must be at least 18 and legally able to enter these Terms to create a self-service account. You must not register for another person or use the service where law prohibits it. We may refuse, restrict, or close access when eligibility, sanctions, legal, safety, or service-availability rules require it.

4. Account information and credentials

Provide accurate information and keep it current. The required profile photo must show you and must not be a logo, illustration, celebrity, or another person. A profile photo is account data only and does not create a verified-identity claim.

  • Protect passwords, passkeys, recovery methods, API keys, client secrets, and webhook secrets.
  • Do not share a personal account or let another person complete verification for you.
  • Review active sessions and connected apps and report access you do not recognize.
  • Use the Security support topic to report a suspected account compromise.

5. Identity verification

A requested check may involve an email or phone confirmation, government document, selfie, active liveness challenge, document-to-face comparison, configured issuer match, attended review, or a combination shown in the flow. Submit only genuine material that belongs to you and follow the capture instructions.

A result describes the check actually completed. id_and_face does not mean an issuing authority confirmed the identity. issuer_match is available only when an approved issuer connector is configured for the request. Authvio may return pending, failed, expired, unavailable, or needs-review instead of a successful result.

Verification lowers risk but cannot guarantee a person's future conduct, legal status, creditworthiness, or suitability for a transaction. A relying party remains responsible for its own legal and risk decisions.

6. Developer and business responsibilities

  • Do not use developer menus, APIs, keys, Live resources, or higher verification levels until the relevant approval is active.
  • Request only the scopes, claims, countries, and checks your service needs and has a lawful basis to use.
  • Give users accurate notice, honor consent and data rights, and protect any fields or results Authvio returns.
  • Verify webhook signatures, use idempotency controls, keep Test and Live data separate, and secure secrets outside client code.
  • Do not present a Test result as a real-person verification or use synthetic test data in Live decisions.

7. Allowances, paid features, and taxes

The developer console may include a monthly API allowance. Calls above that allowance and paid verification levels require a written rate card or separate order before they become available. The console does not collect a payment card or silently enroll an account in paid service. A written order may add volumes, pricing, service levels, taxes, and commercial terms that take priority for that order.

8. Acceptable use

You must follow the Acceptable Use Policy. Do not impersonate someone, submit forged evidence, bypass controls, probe another tenant, scrape protected data, abuse verification, mislead people about a result, or use Authvio to support unlawful discrimination, fraud, surveillance, or harm.

9. Privacy and data processing

The Privacy Policy explains Authvio's own data practices. A developer that receives user fields or results is responsible for its use of that data. Where Authvio processes customer-controlled data as a processor, the Data Processing Agreement applies.

10. Ownership and permitted use

Bolrach Technologies Limited and its licensors own the service, software, documentation, trademarks, and supplied content. You retain rights in content you submit. We grant a limited, revocable, non-transferable right to use the service and published integration materials for their intended purpose. Do not copy branding, badges, non-public code, or protected interfaces, or imply an endorsement that Authvio has not given.

11. Availability and disclaimers

The service is provided on an "as available" basis. We work to keep it reliable, but no identity system is error-free or continuously available. Maintenance, provider outages, legal restrictions, regional-storage failure, or misuse may interrupt a capability. To the extent law allows, we disclaim implied warranties not stated in these Terms or a signed order.

12. Liability

To the maximum extent permitted by law, Bolrach Technologies Limited is not liable for indirect, special, incidental, punitive, or consequential loss arising from the service. Nothing in these Terms excludes liability that applicable law does not allow us to exclude, including liability for our fraud or gross negligence. A signed commercial order may state a different liability cap for that order.

13. Suspension, closure, and erasure

You may close your account through Account Privacy. We may suspend a person, application, key, organization, capability, or account to prevent harm, comply with law, investigate misuse, address unpaid written terms, or enforce these Terms. Where practical and lawful, we will give notice and a way to ask for review.

Closure does not erase records that must remain for fraud prevention, audit integrity, legal duties, billing, dispute handling, or the protection of legal claims. The Privacy Policy describes erasure behavior.

14. Changes

We may update these Terms. The page date will change, and material changes affecting existing users will receive notice where required. If law requires new consent, continued use alone will not replace that consent.

15. Governing law and disputes

These Terms are governed by the laws of the Federal Republic of Nigeria, without applying conflict-of-law rules. Start a dispute through the Legal support topic so the parties can try to resolve it. Unless applicable consumer law requires another forum or a signed order states another process, Nigerian courts have exclusive jurisdiction.

16. Contact

Use the Legal support topic for questions or notices about these Terms. Use the Security topic for suspected compromise and the Privacy topic for data-rights requests.

Questions about this document?

Authvio is a brand of Bolrach Technologies Limited. Send a legal or privacy request through the encrypted support form.