AGCOM 96/25/CONS Compliant

API/SDK for Double Anonymity
Age Verification Made Simple

Intermediary between adult sites and KYC providers.Guarantee complete anonymity and AGCOM compliance.

Fully Compliant
GDPR Compliant
Integrated with Certified Partners
Double Anonymity Guaranteed
15min
Integration Time
100%
Anonymous
2
KYC Providers
99.9%
Uptime SLA

Age Verification Compliance

Modern regulations require age verification with double anonymity protection

Legal Requirement

AGCOM Resolution 96/25/CONS: Double anonymity is mandatory. Fines up to €250,000 + site blocking

Direct Integration = Privacy Violation

Integrating Yoti/Namirial directly violates double anonymity: your site would see user data

Complex Implementation

Building your own anonymity layer is complex, time-consuming, and error-prone

Double anonymity means:

The KYC provider doesn't know which site you visit, and your site doesn't know who the user is

How Veiled Works

The intermediary that guarantees double anonymity by design

1

User Visits Your Adult Site

Your site requests age verification via Veiled SDK → User is redirected to Veiled verification page

Simple SDK IntegrationOne Line of Code
2

User Chooses KYC Provider

On Veiled page, user selects verification method (Yoti or Namirial) → Provider doesn't know which site user wants to access

Yoti IntegrationNamirial IntegrationFirst Anonymity Layer
3

Provider Verifies Age

Yoti/Namirial verifies user identity and age → Returns to Veiled only "18+ verified" flag (no personal data)

Certified KYCNo Data Shared
4

Veiled Issues Anonymous Token

Veiled creates an anonymous JWT token with only "age_verified: true" → Token contains no personal information

Anonymous JWTZero PIISecond Anonymity Layer
5

Your Site Grants Access

User returns to your site with token → Your backend validates token with Veiled API → Access granted based only on age verification

CompliantAnonymousAGCOM Certified

Double Anonymity Guaranteed

1.KYC Provider → Veiled: Provider sees user identity but doesn't know which adult site they want to access

2.Veiled → Your Site: Your site receives verification confirmation but doesn't see user name, date of birth, or any personal data

Why Choose Veiled

The only API/SDK that guarantees double anonymity and AGCOM compliance

100% Compliant

  • AGCOM 96/25/CONS certified
  • Double anonymity guaranteed
  • GDPR compliant
  • Zero personal data stored

15min Integration

  • Simple JavaScript SDK
  • TypeScript support included
  • Developer-friendly documentation
  • Framework agnostic

Transparent Pricing

  • Pay only for verified traffic
  • Prepaid credit model
  • No subscription fees
  • See pricing in dashboard

Simple, Transparent Pricing

Pay only for verified traffic. No subscriptions. No hidden fees.

Prepaid Credits

Load credits and pay only for traffic you verify

No Subscriptions

No monthly fees. No commitments. Pure pay-as-you-go.

Full Transparency

See exact costs and usage in your dashboard

Detailed pricing available in dashboard after signup

Integration in 15 Minutes

Simple JavaScript SDK. Production-ready in minutes.

your-site.js
// 1. Install SDK
npm install @veiled/sdk

// 2. Initialize with your API key
import Veiled from '@veiled/sdk';

const veiled = new Veiled({
  apiKey: 'your_api_key_here',
  onSuccess: (token) => {
    // User verified: Grant access to adult content
    // Token contains ONLY age verification (no personal data)
    grantAccess(token);
  },
  onError: (error) => {
    // User not verified or error occurred
    showErrorMessage(error);
  }
});

// 3. Trigger age verification
veiled.verify();

// That's it! ✅ AGCOM compliant with double anonymity
JavaScript/TypeScript
Framework agnostic
15 min integration
Full documentation

Start Building with Veiled Today

Guarantee AGCOM compliance with double anonymity

15-minute integration
No credit card required for signup
AGCOM 96/25/CONS compliant from day one