Trust

Fair by design. Checkable by your team.

Every outcome is decided on our servers, every draw is committed to before the first play, and your team can re-check the result afterwards. Here is exactly what that means, and what it doesn't.

The draw, step by step

A receipt for every draw.

Winners come from a seed we commit to before a campaign starts. Four steps, each one checkable.

KELIPLAY · DRAW PROOF SAMPLE
  1. STEP 1

    Commit

    Before the first play we generate a secret seed and record its SHA-256 hash. The hash is fixed from that moment.

  2. STEP 2

    Play

    Players play. Every run is scored on our servers and checked; runs with the patterns only scripts produce are kept out of the draw.

  3. STEP 3

    Draw

    When the draw runs, winners are picked from the eligible entries using the committed seed.

  4. STEP 4

    Reveal

    Afterwards the seed is revealed to your team through the authenticated API, so you can hash it, compare it with the commitment and recompute the winners yourself.

Plainly stated

What it proves, and what it doesn't.

It proves

  • The winners were decided by a seed fixed before anyone played.
  • Nobody, including us, changed the seed after seeing the entries.
  • Your team can recompute the result from the revealed seed.

It doesn't prove

  • That every player is a distinct real person. Play limits and checks reduce abuse; they don't eliminate it.
  • Anything to people outside your team. Verification runs through your authenticated API access.

Security

The controls, one by one.

What each control does, stated plainly. We only list certifications we actually hold.

  • Outcomes on our servers

    The browser reports what the player did. Scores, prizes and winners are worked out on our side.

  • Odds never reach the page

    Wheel weights, quiz answers and coin values are stripped before any config reaches the browser.

  • Scoped API keys

    A key holds only the permissions you give it. Keys can never manage members or roles.

  • Roles you define

    Every route declares the permission it needs, and nobody can grant a permission they don't hold.

  • Short-lived player tokens

    A player's token covers one campaign, one player and one origin, lives up to an hour, and opens one session.

  • Signed, checked webhooks

    HMAC-SHA256 with a timestamp. HTTPS only, with internal addresses refused at signup and again at delivery.

  • Uploads checked by content

    Images, audio and animations are verified from their bytes. SVG is refused, and animations can't carry script.

  • Committed draw seeds

    The seed's hash is published before play and revealed after, so your team can recompute each draw.

  • Verified accounts

    Dashboard accounts must confirm their email before they can sign in.

Bringing this to a security review?

We'll walk your team through the controls on a call.

Book a demo