SDK Privacy And Consent

Target reader: developers implementing player consent in the SDK UI.

Screenshot upload, recent logs, and contact information are opt-in. Screenshot and recent-log checkboxes start unchecked.

Minimal example

{
  "screenshot_upload": false,
  "recent_logs_upload": false,
  "contact_upload": false,
  "recent_logs_dropped": false,
  "contact_dropped": false
}

Use screenshot_upload, recent_logs_upload, and contact_upload as the only consent fields. The removed Alpha fields include_screenshot, include_recent_logs, and include_contact make the entire payload invalid.

Project feature gates and consent per submission

The project settings screenshot, recent_logs, and contact only make those capabilities available. They do not grant consent and do not set the corresponding consent fields to true. breadcrumbs and offline_queue are project capabilities and are not additional player-consent fields.

Each newly opened feedback panel starts with screenshot upload, recent-log upload, and privacy confirmation unchecked. Contact is included only when the feature is available and the player explicitly enters contact for that submission. A previous panel selection is not reused. Every accepted report stores the consent snapshot for that report, so project settings and consent evidence remain separate.

Server behavior

The server applies project feature gates first, then the player's consent for this submission. If the player has not confirmed the privacy notice, the API rejects the report. If contact information or inline recent_logs are sent without consent, the server stores the report, drops those fields, and records contact_dropped or recent_logs_dropped in the consent snapshot. Attachment uploads for screenshots or recent logs are rejected when the project feature is disabled or the matching saved consent flag is false.

Common mistakes

• Do not upload a screenshot when the checkbox is unchecked.
• Do not infer contact information from a game account.
• Do not send removed include_* consent fields; the API rejects them.
• Do not log player contact, project keys, JWTs, or signed URLs.
• Do not use an enabled project feature as evidence of consent.

Next step

Read the full Privacy guide.