Adult Verified | Xgroovy

| Step | Action | What the user sees | Data handling | |------|--------|--------------------|---------------| | 1 | on the protected page. | A modal window appears prompting the user to verify age. | No data transmitted yet. | | 2 | Selection of verification method (e.g., government ID upload, credit‑card check, or a trusted third‑party account). | Options displayed: “Upload ID,” “Use Credit Card,” “Login with Google/Apple.” | The user chooses one method. | | 3 | Data capture (if ID upload) or token exchange (if credit‑card). | The user follows on‑screen instructions (e.g., photographing a driver’s license). | xGroovy’s secure servers encrypt the data in‑transit (TLS 1.3). | | 4 | Automated validation using AI‑driven document verification and anti‑fraud checks. | A progress indicator (“Verifying…”) is shown. | The raw ID image is not stored after validation; only a verification token is retained. | | 5 | Result returned to the website via a signed JWT (JSON Web Token). | If successful, the modal closes and the user gains access. If failed, the user is asked to retry or provide an alternative method. | The JWT contains a timestamp, the user’s age status (verified/unverified), and a cryptographic signature; no PII is exposed to the publisher. | | 6 | Session continuation – the website uses the token to allow or block access. | The user continues browsing uninterrupted. | The token expires after a configurable period (commonly 24 h). |

Verification helps ensure that the content being shared is genuinely produced or owned by the account holder, fostering a transparent environment and protecting intellectual property. Why Platform Verification Matters xgroovy adult verified