Welcome to
Docs
Build for every age,
everywhere.
Integrate once. k-ID resolves the right age gate, consent flow, and feature permissions for each user's jurisdiction — automatically.
Choose your path
Start with CDK. Age assurance, parental consent, and permissions all run on the same integration.
CDK
The full compliance engine — embedded flows or custom workflows on the k-ID API.
Adaptive Access
Age assurance inside CDK: k-ID decides when a user must prove their age, at entry or at a feature, and keeps the result on the session.
Compliance Studio
Configure products, markets, permissions, and thresholds — no code.
Legal disclaimer
The information contained within this documentation is not intended to be a substitute for legal counsel and does not constitute legal advice. Please consult with your legal counsel for any questions regarding your compliance strategy.
One platform, five parts
k-ID enables games and applications to be compliant world-wide by providing jurisdiction-specific data from a comprehensive database of regulations to drive product behavior in 200+ markets. There are five main components in k-ID:
An always-up-to-date compliance database containing privacy & safety laws across 240+ jurisdictions (195+ countries, 22,000+ sources)
Enterprise-grade compliance framework that automatically manages regulatory logic and determines feature accessibility based on age, jurisdiction, and parental consent
AgeKit+Privacy-preserving age verification on its own, for a single, standalone age check. In CDK, Adaptive Access runs age assurance for you
Family ConnectWhere parents can grant consent and manage permissions for kids and teens
Compliance StudioWhere you configure and customize your product's compliance settings, permissions, and policies
Integrate with AI coding agents
k-ID publishes official Agent Skills, small instruction packs for supported AI coding tools. Read Integrate with AI coding agents for installation paths and verification checklists.
How the Compliance Development Kit works
The k-ID Compliance Development Kit (CDK) is an enterprise-grade compliance framework that automatically manages regulatory logic and compliance settings. It intelligently determines which features and content are accessible to users based on their age, jurisdiction, and parental consent status.
CDK provides two integration options:
Widgets - Pre-built widgets that handle the complete compliance flow in iframes, including age gate, Verifiable Parental Consent (VPC), data notices, and permission management.
Custom UX workflows - Build completely custom compliance experiences with the k-ID API while still leveraging CDK's compliance logic.
CDK maintains all compliance logic and settings to determine:
- Which features and content are allowed to users
- Which users need parental consent
- Which users must prove their age, and when
- What permissions can be granted based on age, jurisdiction, and consent
- What data notices must be displayed
All compliance policies are configured through the Compliance Studio, where you define and manage your product's regulatory requirements.
For more information, see CDK.
Age assurance with Adaptive Access
Adaptive Access is how CDK runs age assurance. Instead of asking every user for proof up front, k-ID decides when proof is needed: at the age gate with product-level age assurance, when a user reaches a protected feature with feature-level age assurance, or not at all. When a user passes, the result is saved on their session, and later decisions reuse it.
You turn it on and adjust it per market in Compliance Studio. To get started, follow Age assurance at entry or Age assurance at features.
If you only need a single age check with no session, AgeKit+ is also available on its own. See Adaptive Access or AgeKit+ on its own.
Configuration and customization
k-ID is highly customizable for the needs of the product in the markets it serves. Customization of policies, permissions, trusted adult disclosures, and white-labeled parent experiences is done in the k-ID Compliance Studio.
Tip
Before you begin, make sure you have created a product in the Compliance Studio and generated your API key. This is required for all k-ID integrations.