Data inventory
Agree events, identifiers, IP addresses, and any other potential personal data.
Security you can review
Establish the basis for technical and legal review before transferring player events and identifiers.
Event sourcesAccess rulesAnalytics
Access scope and the data to be transferred are agreed before integration.
Documentation and certification
| Topic | What is known | What to verify |
|---|---|---|
| ISO 27001 | Working toward certification | Entity, scope, issuer, validity |
| GDPR | Data Protection Policy | Party roles and processes |
| DPA | Document published | Applicability and execution |
Data and infrastructure
Storage
Confirm regions, retention, backups, and deletion.
Access
Confirm roles, tenant isolation, support access, and auditing.
Transfer
Review encryption, keys, and the subprocessor list.
Review package
Request the DPA, subprocessor details, data-flow description, and evidence of claimed controls. Security-questionnaire answers should be agreed with the responsible team.
Report a vulnerability
Email info@playerly.io with the subject ‘Security’. We’ll agree a channel for technical details. Start with a brief description without secrets or player data.
Explore your goals with Playerly
Explore the right scenario for your games or traffic sources: player analytics, attribution, and collaboration between providers and affiliates.
Book a demo