Safety & Privacy
Privacy isn't a feature. It's the architecture.
Playprint was designed from day one for the most sensitive environments in gaming — children's products, family platforms, and markets with strict regulatory requirements.
Our commitments
What we promise
Clear, simple commitments that studios can share with players, parents, and regulators.
Gameplay data only in Playprints
The Playprint SDK captures only in-game decisions — moves, timing, strategies. No voice, chat, photos, or device fingerprints ever enter a Playprint.
Account data kept separate
Our account system collects parent emails and dates of birth for COPPA compliance. This data is never used to build Playprints and is stored separately from gameplay data.
No voice, chat, or messaging
There is no microphone access, no text chat, and no form of direct communication between players through Playprint.
No likeness or identity
A Playprint does not replicate a player's appearance, voice, personality, or identity. It captures playstyle only.
Opt-in sharing only
Playprints are private by default. Players (or parents) must explicitly choose to share with specific people.
Delete and reset anytime
Any player or parent can delete a Playprint and their account data at any time. Deletion is immediate and permanent.
Data practices
What we collect — and what we don't
Playprint SDK data
- Gameplay decisions
Actions taken in-game: moves, choices, card plays, resource allocation, timing.
- Game state context
The game situation when a decision was made (board state, turn number, available options).
- Session metadata
Anonymous session IDs and timestamps — never linked to real identities.
Account data (COPPA compliance)
- Parent email address
Collected only when a child under 13 registers, to obtain verifiable parental consent as required by COPPA.
- Date of birth
Used solely for age-gating — to determine whether parental consent is required. Not stored in Playprints.
Never collected — in any context
- ✗ Location or IP addresses
- ✗ Device identifiers or fingerprints
- ✗ Voice, audio, or video
- ✗ Chat messages or text input
- ✗ Photos, avatars, or likeness data
- ✗ Browsing history or app usage
- ✗ Purchase history or payment data
Kids & family
Built for children's products
Playprint is designed to meet the strictest standards for children's digital products.
No stranger interaction
Players only encounter Playprints from people they (or their parent) have explicitly approved. No public matchmaking, no random opponents, no discovery of unknown players.
No live connections
Playprint opponents are generated from pre-computed policies. There is no real-time connection to another person — ever. This eliminates grooming vectors entirely.
Parental controls
Parents can view, approve, and revoke Playprint sharing. They can delete any Playprint associated with their child. Controls are simple and accessible.
Data minimisation
We follow a strict data-minimisation principle. We collect the minimum gameplay data needed to build a useful playstyle profile — nothing more.
Compliance
Regulatory posture
Our architecture is designed to support compliance with major children's privacy and data protection regulations.
COPPA (US)
Playprint's architecture avoids collection of personal information as defined under COPPA. Our account system uses age-gated registration with verifiable parental consent for players under 13. Learn more →
GDPR / GDPR-K (EU/UK)
Our data minimisation approach aligns with GDPR principles. Gameplay behavioural data is not linked to identified individuals. Local-only deployment keeps all data on-device.
Age-Appropriate Design Code (UK ICO)
Playprint supports AADC principles including data minimisation, default privacy settings, and the absence of nudge techniques or attention-capture mechanics.
This page describes our architectural approach and design posture. It is not legal advice. Studios should consult qualified legal counsel for their specific compliance requirements.
Want to review our safety architecture?
We're happy to walk through our technical approach and answer questions about privacy, compliance, and deployment options.