Age verification

4rho is a real-money prediction-market platform regulated under the US federal floor (UIGEA, age 18 minimum) plus state-specific floors (NV and NJ are 21+, others are 18+). UK users are gated by the UK Gambling Commission's licensing conditions. We collect your date of birth at signup so we can confirm you're old enough to use the product in your jurisdiction.

What we collect

A single field: your date of birth (YYYY-MM-DD). We store it calendar-only (no time-of-day, no timezone). We do not store your full identity document at this stage — counsel may add a KYC document scan in a future update for higher-risk product tiers, and we'll surface that explicitly if so.

When we collect it

• At signup: the sign-in dialog includes a DOB date input plus a checkbox confirming you're at least 18.
• For existing users (accounts created before we required DOB at signup): a banner appears on the home page asking you to confirm your DOB. You have 7 days from the banner appearing to submit it before order placement / deposit / withdraw paths are gated until you do.

What if I was rejected at signup?

If you submitted a DOB that puts you under the floor for your jurisdiction (18 federally; 21 in NV / NJ), the signup dialog returns an AGE_RESTRICTION error. The most common reasons:

1. Typo in the date input — wrong year, day/month transposed, etc. We don't accept a one-shot self-correction here because that would let a sub-floor user game the gate by retrying. Instead, open a support ticket and our team can verify your real DOB against a government ID.
2. You're genuinely under the floor for your jurisdiction — federal law (and our terms) require us to refuse account creation in this case. If you reach the floor in the future, you're welcome to come back and sign up then.
3. Wrong jurisdiction detection — if our geo lookup placed you in a 21+ state but you're actually in an 18+ state, support can correct the jurisdiction record.

For (1) and (3), follow these steps:

1. Open a support ticket with the subject "Age verification — DOB correction request".
2. Attach a clear photo of a government-issued ID showing your DOB. Acceptable IDs: driver's license, passport, state ID card.
3. What we'll do with your ID: a support representative reviews the DOB on the document, applies the correction via an internal admin tool, and deletes the photo from the ticket within 7 days. We do not retain ID images outside that review window.
4. Once the correction is applied, you'll receive a ticket reply. Sign in normally — the gate is now satisfied.

The internal correction tool requires an elevated role (risk) and generates a tamper-evident audit-log row attributing the action to the specific support representative. This is the same compliance posture that applies to ban / suspend actions on the platform.

Once verified

We store three fields on your account:

• date_of_birth (the calendar date)
• age_verified_at (the timestamp of the most recent verification)
• age_verified_method (which mechanism ran — self_attestation for the signup form, admin_manual for support-corrected, future values for document-scan KYC providers)

Your DOB is never echoed back through the user-facing API. Only admin surfaces — gated by the view_audit_logs permission — can read the value, and even then only via the dedicated user-detail endpoint. The verification timestamp + method are visible to you under your account settings so you can confirm what's on file.

Right to erasure (GDPR Art 17 / CCPA §1798.105)

When you delete your account, the DOB column is scrubbed to NULL. We retain age_verified_at and age_verified_method as audit metadata — the regulator-defensible record that "this account was once age-verified, and by what mechanism" — even after the raw DOB itself is gone.

Related articles

• My account was suspended or banned
• Sign-in history
• Account deletion

Need more help?

Open a support ticket and a real human will respond.