Parents &
younger players.

A card game first. No commercial tricks.

Pile Raid is designed to be understandable, competitive and safe for a mixed audience. It must not use age to increase spending pressure, target advertising, expose hidden social risk or weaken fair play.

Ask only what is needed.

The release design uses a neutral age screen with four ranges: 9–12, 13–15, 16–17 and 18+. Players under 9 are not eligible to create or use a Pile Raid account. The screen should not ask for a precise date of birth merely to select the correct safety branch.

• Age-band choice must not be preselected or framed to push a player toward an adult answer.
• Where local law requires parent or guardian permission, account or feature activation waits for that adult action.
• Changing an age band to a less-protected state requires an appropriate adult or support review; it is not a one-tap bypass.
• If age is missing, malformed or uncertain, the service uses the protected child/unknown treatment.

Use less data, for clear reasons.

For younger players, Pile Raid should collect only what is needed for the account, game, safety, progression and a verified request. It does not need a child’s school, contacts, precise location, microphone, camera or advertising profile to play the card game.

• Public identity uses a username, approved avatar and optional country code—not a required real name.
• Email, private hand and hidden deck state are not public to other players.
• Age band is used for protection, not personalised marketing.
• Parents and eligible players may request access, correction or deletion, subject to identity checks and legal limits.

Read the complete younger-player privacy section.

Social features require stronger boundaries.

Private rooms, friends, invitations, usernames and emotes can create user-to-user contact. For child or unknown-age players, the release policy requires an adult-action or protected social mode where law or platform policy requires it.

• No free-form public chat is promised by the current product contract.
• Unsafe usernames, harassment, sexual content, grooming, threats, scams and attempts to move children to private external contact are prohibited.
• Block and report controls must be reachable from relevant player surfaces.
• A block must affect invitations, search and matchmaking where appropriate—not just hide a message.

See the Community Guidelines for the full conduct standard.

Adult action before money; no personalised child ads.

The current app source does not enable advertising or real-money checkout. If monetisation is activated later:

• child and unknown-age users must not receive personalised or interest-based advertising;
• any ad SDK and placement must be appropriate for the declared audience and verified before the first request;
• purchases for younger players require the relevant adult or platform control;
• prices come from Apple or Google, not hardcoded text;
• paid products stay cosmetic and may not influence cards, score, matchmaking or rating; and
• subscriptions require transparent recurring terms, restore and management controls.

Review these controls together.

1. Choose the truthful age band.
   Explain why the safer branch exists.
2. Use a non-identifying username.
   Avoid real full name, school, address or contact information.
3. Review social invitations.
   Only accept people the player recognises and trusts.
4. Keep verification and room links private.
   Support will never ask for a password.
5. Use block, report and account controls.
   Open Settings → Privacy & Safety.

Ask for help without sharing a password.

For a privacy request, child-safety concern, account issue or deletion request, use the in-app Privacy & Safety route or the active public support ticket. Sensitive requests may require identity or guardian verification.

This guide documents the intended mixed-audience posture. It does not claim child-privacy legal approval until controls and disclosures have separate legal, store, device and live evidence.