Age Verification Policy

1. Adults only

pleasedtobe is restricted to users who are at least 18 years old. Creating an account does not by itself provide access to active community features. Users must satisfy pleasedtobe's age-verification requirements before entering the community.

2. Current development status

The current pre-launch development build uses a simulated verification provider for testing. Production age verification is not yet configured, and the production service should not be represented as having a live identity-verification provider until that integration is completed.

Before public launch, pleasedtobe must select a production provider and update this policy with provider-specific information about the verification flow and any identity, document, biometric, or other data the provider processes.

3. Information currently stored by pleasedtobe

• Age-verification provider name.
• Provider reference ID.
• Verification status.
• Verified threshold, currently represented as 18+.
• Verification creation and completion timestamps when applicable.
• User-level verification status, age-verified flag, and age-verified timestamp.

4. Verification outcomes

pleasedtobe does not manually approve age-verification failures or ambiguous results. If a production provider performs additional review, that review occurs within the provider's own process. pleasedtobe waits for the provider's final pass/fail result rather than allowing administrators or moderators to override age eligibility.

• PENDING: pleasedtobe is waiting for the third-party verification provider to return a final result.
• PASSED: the provider returned a successful 18+ verification result and the account may proceed to eligible community access.
• FAILED: the provider did not return a successful 18+ verification result and the account is not admitted to active community features.

5. No circumvention

• Do not use false identity information or another person's identity to pass verification.
• Do not lend, sell, transfer, or share an age-verified account with a minor or an unverified person.
• Do not manipulate verification requests, provider callbacks, or technical controls.
• Do not create replacement accounts to bypass a failed verification or restriction.

6. Re-verification and provider changes

pleasedtobe may require re-verification when reasonably necessary for safety, fraud prevention, provider migration, account recovery, suspected circumvention, or legal compliance.

A future change in verification provider may require additional disclosure and a revised policy version.

7. Privacy

Age-verification information is handled subject to the Privacy Policy. pleasedtobe should collect and retain only the verification information necessary for the production verification design, safety operations, and applicable legal obligations.

Because the production provider has not yet been selected, no promise is made in this draft about whether the provider will process identification documents, facial images, biometrics, or similar data. Those details must be disclosed accurately before launch.

8. Underage accounts and reports

Accounts reasonably believed to belong to a person under 18 may be restricted and required to complete or repeat verification through the designated third-party process. pleasedtobe moderators do not manually certify a user's age. Users should report suspected underage users or underage sexual content through the UNDERAGE CONTENT OR USER category.

Such reports receive critical-priority triage in the current reporting system, but priority alone does not determine the final result.