The platform
Every design decision answers one question: can we prove this to a regulator, an auditor and a bank? The result is a platform where going live is a configuration change, not a rebuild.
Data protection by design
Customer data is held only where it must be, and only for as long as it must be. Systems that do not need personal data never receive it. The boundary is part of the system design itself, not a policy document, which is how the platform is designed to meet the data-protection obligations the law places on gambling software.
Access is scoped to the minimum each component needs, and every access is written to an immutable log. Consent, retention and data-subject requests are handled as first-class functions rather than manual processes.
Core capabilities
Pluggable identity verification (local or global vendors) with age and residency checks at onboarding, behind a single provider interface.
Screening, risk scoring and velocity monitoring with escalation hooks, producing the records a compliance officer needs on demand.
Self-imposed limits on spend, time and loss, cool-off periods, prominent addiction warnings with support links, and enforced self-exclusion.
Consent capture, retention rules and data-subject requests handled as first-class functions, aligned to the Personal Data Protection Act.
Double-checked, decimal-exact accounting of balances and payouts. Money is never approximated.
Payouts are reconciled back to every account automatically, with breaks surfaced rather than absorbed.
Structured, regulator-ready exports produced in the operator's reporting identity, on demand.
A hash-chained, append-only record with a verification routine that detects any tampering across the entire history.
End to end
Money is exact from the first cent to the last, and every step is recorded so it can be examined later. The lifecycle below is how we design every product we take to an operator.
Identity, age and eligibility checks run at registration and are recorded in the audit chain.
Responsible-gambling limits are enforced in real time, and self-exclusion holds once set.
Monitoring flags unusual activity and escalates it, with every decision written down.
Every balance and payout is tracked in exact decimals, reconciling to the cent.
Each step is written to the hash-chained audit log, where it cannot be quietly changed.
Regulator-ready exports are produced in the operator's reporting identity whenever needed.
The whole chain re-checks on request and detects any tampering across its history.
Engineering principles