Drafting status
Not yet operative policy
The final minimum age, supported regions, guardian-verification method, consent duration, revocation process, and minor payout rules remain unresolved. The former local form and fake “consent verified” result have been removed.Guardian verification
Protected workflow not yet enabled
CoreComp will not collect guardian names, emails, identity evidence, or signatures through an unverified local form while the approved workflow is pending.Current age position
CoreComp is not currently designed for children under 13, and under-13 participation should remain disabled unless CoreComp intentionally builds a child-directed program with verifiable parental consent, data minimization, parent rights, retention controls, security safeguards, and professional review.
A simple “13+” label is not enough to determine every user’s eligibility. Rules for ages 13–17 can depend on country or state, account features, communications, event type, entry fees, prizes, publicity releases, payout providers, and game-publisher requirements.
Consent relationship
Four verified links—not one checkbox
Age and region checks
The product should request only the minimum age information needed to place a user in an eligibility band. It should not expose a minor’s birth date or guardian status publicly. Region should be determined consistently enough to apply the correct age and event rules without creating a public location trail.
If a user is not eligible for a feature, CoreComp should explain the restriction in age-appropriate language and avoid revealing sensitive account details to teammates, opponents, or public viewers.
When guardian involvement may be required
Counsel and provider rules must determine whether guardian notice, consent, co-signature, publicity release, payout authorization, or other approval is required for account use, communications, a particular competition, prize acceptance, or payment.
Consent must be specific to the approved purpose. A guardian’s approval for general account participation should not silently authorize cash entry fees, publicity use, international travel, data sharing, or a prize payout.
Protected consent workflow
- The minor account encounters a feature or event that has a verified guardian requirement.
- CoreComp creates a time-limited, single-purpose handoff without exposing the minor’s status publicly.
- An approved guardian-verification method provides the required notice and collects only necessary evidence.
- CoreComp receives a limited status, policy version, scope, timestamp, expiry, and provider reference—not unnecessary identity documents.
- The guardian can review, withdraw, or update consent through a protected channel where the approved policy requires it.
Minor data and communications
CoreComp should minimize minor profile fields, default sensitive visibility conservatively, restrict staff access, moderate communication channels, provide reporting and blocking controls, and avoid behavioral advertising or unnecessary profiling.
Guardian contact information and verification status must be private. CoreComp must not request government IDs or consent evidence through public Discord channels, ordinary support email, team applications, or public profile fields.
Events, organizers, and prizes
Event organizers must select from approved age and prize configurations; they must not invent their own guardian form or override a CoreComp restriction. Official rules should state the minimum age, region, guardian requirement, communication method, publicity treatment, prize eligibility, and payout limits.
If a selected provider cannot support a minor recipient or the recipient’s location, the event must not promise that payout. The rules must define a lawful alternative or make the participant ineligible before entry.
Guardian and user rights
The approved program must explain how a guardian can review the notice, confirm the scope, refuse or withdraw consent, request deletion where applicable, update contact information, and raise a concern. It must also explain the consequences of withdrawal for active events and future participation.