Games · Platforms and publishers
Gate games by age — with verification you can defend
Rated titles, in-app purchases, and multiplayer need trustworthy age assurance — not just a birth date at signup or a PIN anyone can guess. When regulators, families, or auditors ask, you need proof of what was checked and why.


What game teams face
Onboarding must stay frictionless enough to convert players — yet strict enough to protect minors and honor content ratings. Balancing both with fragmented tools is where most platforms lose control.
- Self-declared age at signup anyone can change without consequence.
- Kids profiles without real verification behind parental controls.
- Different rules on console, PC, and mobile — inconsistent outcomes.
- Unlocking 16+ or 18+ content without a consistent age gate.
- In-app purchases without re-verification when policy requires it.
- Household account sharing that bypasses supervision settings.
- Testing a new verification flow without affecting real players becomes a side project.
How Qonclor helps
You gain infrastructure focused on identity and age decisions — with outputs your product, trust & safety, and compliance teams can use and explain.
One flow across surfaces
Document, selfie, and official data on the same path — fewer vendors, less integration debt, fewer failure points on console, PC, and mobile.
Clear outcome: allow, block, or review
Structured decisions with confidence and risk — without interpreting raw third-party payloads in production.
History when someone asks
Every check leaves a trail. Legal and leadership can look it up without patching spreadsheets.
Data handled with care
We minimize what we process and store — less exposure for players and for you under LGPD.
Test before going live
Tune policies and flows in a safe environment before they affect real players.
Operations dashboard
Volume, exceptions, and trends visible to product, compliance, and operations.
How it works in practice
- 1
Define when to verify — signup, store purchase, mature content unlock, multiplayer access, or revalidation.
- 2
The player or guardian submits document, selfie, or data; Qonclor checks behind the scenes.
- 3
You receive the result: allow, block, or route to manual review.
- 4
Your platform applies the rule; Qonclor keeps the record.
- 5
Your team monitors in the dashboard — no scramble when a request lands.

Frequently asked questions
Does Qonclor replace content ratings or in-game moderation?
No. We specialize in identity and age verification decisions. Editorial ratings, community guidelines, and moderation stay with you — we take the weight of reliable age assurance off your plate.
How is this different from iGaming?
Our iGaming use case covers licensed betting operators — player KYC, deposits, and fraud. Games covers video game platforms and publishers: store gates, kids profiles, in-app purchases, and multiplayer access.
How does this relate to Lei Felca?
Lei Felca sets expectations for protecting minors in digital environments, including trustworthy age checks where self-declaration is not enough. See our ECA Digital page for context — we support your verification layer; your counsel validates your full compliance program.
Does it work for users in Brazil?
Yes. The flow is built for the Brazilian market, including CPF validation and biometric confirmation, at the pace game platforms need.
Do you store identity evidence forever?
Not necessarily. You define retention; sensitive evidence can be discarded after verification while keeping a record of the decision.
Ready to strengthen age controls on your game platform?
Tell us how you operate today — surfaces, volume, and what keeps your team up at night. We will put together a focused demo, no strings attached.
This page describes product capabilities. For legal and regulatory decisions, consult your advisors.