Use Cases & Setup Guides

Use Cases & Setup Guides

Step-by-step configuration guides for the most common VeriSelf deployments. Copy the settings exactly for your industry.

Use Case A: Adult Content Site (18+)

Goal: Block all underage visitors from accessing the entire site with real AI verification (not just an honor-system checkbox).

Step-by-Step Setup

  1. Go to Gate tab → Set Trigger to “On page entry”.
  2. Set Gate Type to “Overlay”.
  3. Select Industry Preset: “Adult”.
  4. Set Minimum Age: 18.
  5. Enable Consent Mandatory (required for GDPR + 2257 compliance).
  6. Enable AI Alternative so users can verify with camera instead of just typing a birthday.
  7. Go to System tab → Set Re-Verify Interval to “30 days” (UK Online Safety Act recommendation).
  8. Set Cookie Duration to 30 days.
  9. In System → Compliance → Legislation Source, select “Auto-detect by IP”.

Result: Every visitor sees an 18+ gate before accessing any page. Camera verification provides actual proof of age.

Use Case B: Vape / CBD Store (Checkout Gate)

Goal: Verify age before a customer can complete checkout. Gate only the checkout page, not the whole site.

Step-by-Step Setup

  1. Go to Gate tab → Set Trigger to “On demand (shortcode)”.
  2. Create a checkout page and insert
    before the checkout form.
  3. In your theme or page builder, conditionally hide the checkout form until the user has the veriself_verified user meta.
  4. Set Minimum Age to 18.
  5. In System → GPS Settings, set GPS Mode to “Optional” to collect state-level location for compliance logging.

Result: Customers must verify age before seeing the checkout form. Verification result stored in admin log as evidence.

Use Case C: Dating Platform (Couple Mode)

Goal: Verify both people in a couple’s profile photo are real humans of appropriate age. Unique couple mode feature.

Step-by-Step Setup

  1. Upgrade to PRO — Couple mode is a PRO feature.
  2. Go to Setup tab and connect your self-hosted Ollama server.
  3. Go to Gate tab → Set Trigger to “On demand (shortcode)”.
  4. Create a profile verification page.
  5. Insert
    .
  6. In System → Integrations, enable UM Integration → Update Profile Photo.
  7. Enable Gender-Based Outline if your UM setup tracks gender.

Result: Both people must be visible. AI estimates each person’s age and gender. If either is underage, verification fails.

Use Case D: Alcohol Delivery (21+, GPS Required)

Goal: Verify age AND confirm the customer is in a state where delivery is legal. Strict fraud detection.

Step-by-Step Setup

  1. Go to Gate tab → Set Minimum Age to 21.
  2. In System → GPS Settings, set GPS Mode to “Mandatory”.
  3. Set Nominatim User-Agent to your business name.
  4. In System → Compliance, set Fraud Action to “Auto-block” with Max Fraud Score: 60.
  5. Enable VPN Detection.
  6. Set Legislation Source to “Auto-detect by IP”.

Result: Customer must share real GPS location. If IP and GPS mismatch (fraud score > 60), the order is blocked.

Use Case E: Membership Site (Bot Prevention)

Goal: Ensure new members are real humans, not bots or throwaway accounts. Add trust badges to verified profiles.

Step-by-Step Setup

  1. Go to Gate tab → Set Trigger to “On demand (shortcode)”.
  2. On your registration page, insert
    after the registration form.
  3. Set Minimum Age to 13 (or your platform’s TOS age).
  4. Enable Show Remember Me so verified users stay verified.
  5. In System → Integrations, enable UM Integration → Show Verified Badge.
  6. Set Re-Verify Interval to “Never” (once verified, always verified).

Result: Every new member must pass a live camera check. Bots cannot complete this. Verified members get a visible trust badge.

Use Case F: Re-Verification for Compliance (UK Online Safety Act)

Goal: Re-verify users periodically to comply with regulations requiring ongoing age assurance. Complete audit trail.

Step-by-Step Setup

  1. Go to System tab → Set Re-Verify Interval to “30 days”.
  2. Set Show Verified Message to ON.
  3. In System → Compliance, set Fraud Action to “Log only”.
  4. In System → Maintenance → Log Limit, set to 5000+ to retain audit history.

Result: Every 30 days, previously verified users must re-verify. Admin log provides complete audit trail with timestamps, IPs, and GPS.

Need help with a custom setup? Contact support at support@veriself.eu or visit our support portal.