Acceptable Use

How Identity Entry may be used.

Effective October 17, 2026

1. Purpose of this policy

Identity Entry handles sensitive information about real people. This policy sets out how the service may and may not be used. It is part of the Terms of Service and applies to every account, team member and API key.

2. Permitted uses

  • Confirming the identity of customers, tenants, members, guests, contractors or staff who have agreed to verify who they are.
  • Meeting identity, age or fraud prevention requirements that apply to your business.
  • Reviewing results before making a decision, and recording that decision with its reasons.
  • Testing the service with clearly made-up details and sample images.

3. Prohibited uses

You may not use Identity Entry to:

  • Check a person who has not agreed to the check, or without giving the notices the law requires.
  • Identify, track, locate or monitor a person, or build a profile of them, outside a check they agreed to.
  • Stalk, harass, threaten or intimidate anyone.
  • Discriminate unlawfully on the basis of race, color, religion, sex, national origin, disability, age or any other protected characteristic.
  • Make decisions about employment, housing, credit or insurance without following the laws that apply to those decisions.
  • Check children under 13.
  • Submit images or documents you know are forged, stolen or belong to someone else.
  • Resell, relabel or give others access to the service without our written agreement.
  • Build a database of faces or identity documents, or use results to train models.
  • Probe, scan or test the security of the service without permission, except as described on the Security page.
  • Interfere with the service, overload it, or get around its limits or protections.
  • Copy, decompile or reverse engineer the service, except where the law allows.
  • Break any law or regulation.

4. Keeping links and keys private

Capture links are meant for one person. Send each link only to the person it is for. Keep API keys on your own servers and never place them in browser code, public repositories or messages. Revoke any key you think has been exposed.

5. Respecting the people you check

The people you check are trusting your business with sensitive information. Tell them why the check is needed, use results only for that reason, and give them a way to ask questions or raise a concern about a result.

6. Your team

You are responsible for making sure everyone on your team and every system using your API keys follows this policy.

7. Reporting misuse

If you believe Identity Entry is being misused, including to check you without your agreement, use the contact page. We review every report.

8. Enforcement

If we reasonably believe this policy has been broken, we may investigate, ask you to stop, remove access for specific team members or keys, suspend the account, or end the agreement. Where it is practical and lawful, we will tell you first and give you a chance to fix the problem. Where the law requires, we may report unlawful use to the authorities.

9. Questions

If you are unsure whether a use is acceptable, ask before you start through the contact page.