Skip to main content

PlayerPal documentation

One player identity across casinos, games and affiliates. Without personal data.

Guides for partners evaluating PlayerPal, references for engineers integrating it, and the principles that keep player data private.

ExampleOne player, as each partner holds them
HolderWhat they keep
Casino AOperatorpp_plr_opr_7f3k2q…
Game provider BPlayers at casino App_plr_prv_c91mxe…
Game provider BPlayers at casino Cpp_plr_prv_4hd8wz…
PlayerPalThe networkThe link between them. No email, name or phone number.
Illustrative values in the real alias formats. Every partner gets its own alias for the same player, so a game provider cannot join its players across casinos.
A signed fact batch
POST /v1/ingest
Authorization: PP-HMAC-SHA256 keyId=pp_kid_XXXX, signature=<base64url>
X-PP-Timestamp: <unix seconds>
X-PP-Nonce: <random 16–128 chars>
Content-Type: application/json

{
"schema": "playerpal.provider.player_game_daily.v1",
"schema_version": 1,
"batch_id": "<your unique batch id>",
"period_start": "2026-10-01",
"period_end": "2026-10-01",
"records": [ ... ]
}

Honest about what is built

Every page carries a status, so you always know what you can rely on today.

AvailableIn developmentPlannedSee capabilities
Internal build

Team handbook

Architecture, decisions, implementation status and deep dives. Not part of the public site.