# What is PlayerPal

PlayerPal is one player identity and loyalty layer for the online gaming network. A Player keeps a single PlayerPal Account and earns Points across every casino and game they connect. Operators, game providers and affiliates get loyalty and analytics about their own players. PlayerPal does this without holding a player's email address, name or telephone number.

  <Card title="One private identity" eyebrow="Players">
    A single PlayerPal Account that follows the player across every casino and game they connect.
  
  <Card title="An alias per partner" eyebrow="Partners">
    Each partner gets its own random identifier for a player, so nobody can join players across partners.
  
  <Card title="No personal details" eyebrow="Privacy">
    PlayerPal never holds a player's email address, name or telephone number.
  

## The problem

Loyalty in online gaming is locked inside each casino. A player who plays the same studio's games at three casinos has three unrelated loyalty balances, and none of them follow the player. Each partner sees a slice of the picture and has no fair way to compare itself with the rest of the market.

The obvious fix, a shared player database, does not work. Operators will not hand their players' personal data to a third party, and a central dependency in the game path would turn any outage into a casino outage.

PlayerPal is designed around both constraints: a portable Account with no personal data, and a service that sits beside the game, never inside it.

## Who takes part

| Party | Role in the network | Status |
|---|---|---|
| Player | Holds the PlayerPal Account, connects casinos and games, earns Points | [Available] |
| Operator (casino) | Links its players to PlayerPal, sends commercial facts, reads analytics | [Available] |
| Game provider (studio) | Sends gameplay activity, reads analytics about players reached through its integrations | [Available] |
| Affiliate | Receives attribution and performance figures for the players it referred | [In development] |
| Reward partner | Funds or fulfils rewards that players redeem with Points | [Planned] |

## What each party gets

**Players** get one Account that works across casinos and games, Points that accumulate wherever they play, and full control: they can disconnect any partner or delete the Account at any time. See [Player experience](./player-experience.mdx).

**Operators** get a loyalty programme that players already carry with them, analytics about their own linked players, and an anonymous comparison with the rest of the network. See [For operators](./for-operators.mdx).

**Game providers** get loyalty for their players across every casino that runs their games, and analytics counted in distinct players rather than per-casino fragments. See [For game providers](./for-game-providers.mdx).

**Affiliates** get attribution and performance figures for the players they referred, reported by the operator as the authoritative source. See [For affiliates](./for-affiliates.mdx).

**Reward partners** will be able to fund or fulfil rewards for an engaged, pseudonymous audience. This role is planned. See [For reward partners](./for-reward-partners.mdx).

## Core principles

### No player personal data

[Available]

PlayerPal never asks for, and does not store, a player's email address, name or telephone number. Sign-in keeps only an opaque reference from the sign-in method. Partners send activity against PlayerPal-issued aliases, and anything shaped like an email address is rejected. Read more in [Privacy](../trust/privacy.mdx).

### Casino play never depends on PlayerPal

[Available]

PlayerPal is not called during game launch, betting, settlement or payout. Partners record activity locally and send it in batches afterwards. If PlayerPal is unavailable, players keep playing and activity is delivered once it is back. Read more in [Availability](../developers/availability.mdx).

### Partners see only their own players

[Available]

Each partner receives its own random alias for a player, so two partners cannot match the same person by comparing identifiers. A game provider receives a separate alias for each casino it is integrated with, so it cannot follow a player from one casino to another. Partner scope always comes from the partner's credentials, never from the request.

### Anonymous comparison

[Available]

Partners can compare their players with the rest of the network without learning anything about a named competitor. Figures are only shown when enough players and enough peers contribute, and are withheld when one competitor would dominate the result. Read more in [Privacy thresholds](../analytics/privacy-thresholds.mdx).

## Where things stand

The core platform is built and tested: player sign-in, linking, activity ingestion, Points earning and partner analytics. Partner portals, the embeddable widget and the rewards shop are in development, and Points redemption in the platform API is planned. The reward-partner role and enterprise sign-in for partner staff are planned. The full list is in [Capabilities](./capabilities.mdx).

## Explore

  - [How it works](./how-it-works.mdx): 
    The journey from sign-up to Points, and what data moves where.
  
  - [For operators](./for-operators.mdx): 
    Portable loyalty and analytics for your casino.
  
  - [For game providers](./for-game-providers.mdx): 
    Loyalty and distinct-player analytics across every casino you run on.
  
  - [For affiliates](./for-affiliates.mdx): 
    Attribution and performance for the players you refer.
  
  - [Business value](./business-value.mdx): 
    Why a shared, privacy-first loyalty layer matters.
  
  - [Developer quickstart](../developers/quickstart.mdx): 
    Authenticate, send a batch and read analytics back.
  

## Related

- [Capabilities](./capabilities.mdx)
- [Frequently asked questions](./faq.mdx)
- [Privacy](../trust/privacy.mdx)
- [Glossary](./glossary.mdx)