Dench Core · Compliance
Responsible gaming and AML, enforced where the money moves.
Limits per product, timeouts and self-exclusion as account states, three national registers, 40+ fraud and AML checks, an audit trail on every back-office action, and the registries and reports behind your filings. Your compliance team runs it from the same back office as everyone else.
01 · The back office
The screens your compliance team will live in.
Six screens from the product, with demo data, and the controls work. Put a player on a timeout, find it in the registry, clear a fraud alert, open the device two accounts share, read the audit record, block an address. On a call we open the real one, on your market.
Account-Wide Exclusion
Excludes the customer from the entire platform.
Permanently excluded, no end date.
Temporary cool-off applied to the whole account.
Per-Product Exclusions
Restrict access to individual products.
Permanently excluded, no end date.
Permanently excluded, no end date.
Permanently excluded, no end date.
Account Status Registry
Account status change log
| Registry Player ID | Created Date | Previous Status | New Status | Back Office User ID | By |
|---|---|---|---|---|---|
| 2049301 | 31/10/2026 10:41 | ACTIVE | SELF EXCLUDED | – | SYSTEM |
| 2049288 | 31/10/2026 09:15 | TIMEOUT | ACTIVE | – | SYSTEM |
| 2049270 | 31/10/2026 08:02 | ACTIVE | FROZEN | 14 | BACKOFFICE |
| 2049262 | 30/10/2026 23:48 | ACTIVE | TIMEOUT | – | CUSTOMER |
| 2049240 | 30/10/2026 21:17 | SELF EXCLUDED | COOLING OFF | – | SYSTEM |
| 2049231 | 30/10/2026 18:30 | COOLING OFF | ACTIVE | – | SYSTEM |
| 2049207 | 30/10/2026 16:05 | INACTIVE | ACTIVE | – | CUSTOMER |
| ID | Customer ID | Username | Date | IP | Type | Cleared | ||
|---|---|---|---|---|---|---|---|---|
| 9182 | 100512 | demo.player.512 | 31/10/2026 10:14 | 192.0.2.77 | Duplicate and SE | No | ||
| 9181 | 100447 | demo.player.447 | 31/10/2026 09:58 | 198.51.100.23 | Triangle Mismatch | No | ||
| 9179 | 100391 | demo.player.391 | 31/10/2026 09:31 | 203.0.113.80 | Shared Device | No | ||
| 9176 | 100208 | demo.player.208 | 31/10/2026 08:47 | 192.0.2.140 | Source of Wealth | No | ||
| 9170 | 100153 | demo.player.153 | 30/10/2026 23:12 | 198.51.100.7 | DUP IBAN | No | ||
| 9168 | 100086 | demo.player.086 | 30/10/2026 21:40 | 203.0.113.15 | Lifetime 20K+ | Yes | ||
| 9161 | 100274 | demo.player.274 | 30/10/2026 19:05 | 192.0.2.61 | HR C Deposit | Yes |
| Customer ID | Last Seen | Browser | OS | Device | IP Address | Country | Trust Level | Score | Logins | First Seen |
|---|---|---|---|---|---|---|---|---|---|---|
| 100418 | 31/10/2026 09:12 | Chrome 130 | Windows 10 | Desktop | 203.0.113.80 | LV | SUSPICIOUS | 30 | 38 | 12/08/2026 18:40 |
| 100418 | 30/10/2026 22:41 | Safari 18.1 | iOS 18.1 | Mobile | 192.0.2.77 | LV | FULLY_TRUSTED | 100 | 241 | 03/06/2025 19:12 |
| 100418 | 27/10/2026 23:58 | Firefox 131 | Windows 11 | Desktop | 198.51.100.23 | NL | UNKNOWN | 10 | 3 | 27/10/2026 23:40 |
| 100418 | 19/09/2026 13:05 | Chrome 129 | Android 14 | Mobile | 192.0.2.140 | LV | TRUSTED | 80 | 57 | 02/09/2025 08:30 |
Audit Trail
Track system activities and user actions
| ID | Date | Back Office User | Operation Group | Operation Name | IP | Customer ID |
|---|---|---|---|---|---|---|
| 552901 | 31/10/2026 10:52 | ops.manager | Customer | Responsible Gaming Update | 192.0.2.10 | 100207 |
| 552897 | 31/10/2026 10:38 | risk.analyst | Fraud Activity | Clear | 192.0.2.11 | 100086 |
| 552880 | 31/10/2026 10:20 | payments.lead | Payment Transaction | Reject | 192.0.2.12 | 100033 |
| 552871 | 31/10/2026 10:05 | compliance.officer | Customer | KYC Verified | 192.0.2.13 | 100512 |
| 552860 | 31/10/2026 09:51 | ops.manager | Configuration | Whitelist Blacklist | 192.0.2.10 | – |
| 552844 | 31/10/2026 09:30 | compliance.officer | Compliance | Account Status Registry Export | 192.0.2.13 | – |
| Property | Before | After |
|---|
Blacklists
Manage country and IP-based access controls
General
Whitelist ModeWhen enabled, all countries are allowed except those in the blacklist. When disabled, only countries in the whitelist are allowed.
Countries in this list will be allowed access (when whitelist everything is disabled)
Countries in this list will be blocked from access (when whitelist everything is enabled)
| IP | |
|---|---|
| 192.0.2.10 | |
| 192.0.2.11 |
| IP | |
|---|---|
| 203.0.113.45 | |
| 198.51.100.200 |
Timeout, self-exclusion and cooling-off are account states. Set one for the whole account or per product, for a period or for good, and every module reads it. A match on GAMSTOP, PIPARS or the Bulgarian register applies the same exclusion on its own.
Every status change, on the record as it happens. What it was, what it became, and whether the player, the system or your team changed it. Customers, sessions, wallet, payments and gaming keep registries of their own, each one exportable.
An uncleared alert blocks. Verification and withdrawal wait until someone reviews it, and which of the 40+ fraud and AML types block is yours to set. A self-excluded player registering again is a type of its own.
Every device a player signs in from, with a trust level. The detail holds the fingerprint, the network and any VPN, proxy or Tor flag. Failed sign-ins are rate-limited per device and per customer, a device trying account after account is blocked, and more accounts on one device than the limit our team sets for the brand raises a Shared Device alert.
Every back-office action, with the value before and after. Who did it, from which address and country, to which player. Roles and permissions per user and per brand keep the trail short.
Decide who reaches the site at all. Allow every country except the ones you block, or only the ones you list. Addresses on the IP whitelist always get in, the ones on the blacklist never do.
02 · What is in it
Compliance, in five parts.
- 01Limits and reality checkDeposit, loss, wager and session limits by day, week or month, bet and loss limits per product, set by the player or your team, and a maximum-win limit on a rolling window. A reality-check timer runs from the first real-money bet.Customers · Limits
- 02Exclusion and the registersTimeouts from 24 hours to a year. Self-exclusion for the whole account or per product, for a period or for good, with the national registers checked on top.Customers · Self-Exclusion
- 03Fraud, AML and accessPEP and sanctions matching, source of wealth, shared devices, duplicate IBANs, triangle mismatch and 40+ types in all. Country and IP lists, and a trust level on every device.Fraud Activities · Blacklists · Device History
- 04The audit trailEvery back-office action with who, when, from which address, and the value before and after. System-wide, and on each player’s record beside that player’s own reports.Management · Audit Trail · the player record
- 05Registries and reportsCustomers, sessions, wallet, payments, gaming and account-status registries; active games, the communication and game-data logs, complaints and errors. Daily self-exclusion and 168-hour inactivity reports.Compliance · Daily Reports
03 · Standard, and ours
Every platform has limits and an exclusion flag. Here is what is different.
Standard. Here too.
- Deposit, loss, wager and session limits
- Self-exclusion and timeouts
- KYC, document checks, PEP screening
- Fraud alerts and a review queue
- Country and IP blocking
- A log of back-office actions
- Exports for the monthly return
Different here.
- A limit change is a state, with a history.
Lowering applies at once. Raising goes pending, cools off for 24 hours, then the player accepts or refuses it at their next login, per product and per window. With no cooling-off set, it applies at once, and every step is on the limit history. Enforced at the transaction, not reported on afterwards.
- An exclusion reaches every module.
Timeout, self-exclusion and closure are states of the account, not a flag on one module. A bonus, a campaign reward or a tournament prize sent to an excluded or closed account is rejected, and the rejection says why.
- Integrated where the market runs a system.
Where a regulator runs an automated system, as in Bulgaria, player registrations, licence changes, active-games declarations and every game round go to it, with the request and the response in the log. A failed message is found, corrected and re-sent.
04 · The record
Ten years, measured.
Ran on it
- 138.comUnited Kingdom, 2017 to 2020, under our UK Gambling Commission licence.
- Bet99Canada from 2020, licensed in Ontario when the regulated market opened.
- KlondaikaLatvia, the full platform including CRM, until Entain acquired it in 2022.
- GGPokerA global poker brand, on the platform in 2019.
Running on it now
- Spins.lvLatvia
- EverbetBulgaria
- SlotinoBulgaria, the brand we built and ran ourselves
- AladinsBulgaria
- QbetBulgaria
- Slots99Canada, Europe and Latin America
- ISO/IEC 27001 since 2017
- UKGC licensed software supplier
- GLI certified in three jurisdictions
- Bulgarian manufacturer licence
05 · How it is bought
Four ways to take it. One price list.
Platform
You hold the licence and run the operation: marketing, support, payments relationships, compliance. We deliver and run the technology: the platform with its CRM and gamification suite, integrations, front end, hosting, releases, support. Your provider contracts or ours.
Enterprise
The platform built out to your market and your specification: dedicated environment, custom front end, features against your requirements. The way the largest accounts have been delivered for ten years.
White label
Our infrastructure end to end, run under the group’s Curaçao setup: licensing, provider contracts, payments. You bring the brand and the marketing.
Giselle Cloud
The engagement suite, journeys, loyalty, jackpots, tournaments, bonusing and the analyst, on the platform you already run.
A platform fee, a revenue share, and one-off costs for integrations and environment setup.
The mix moves with volume, and we are flexible on the model depending on the case and the size of the operation. The platform comes whole: the CRM and gamification suite and every module are in it, not a lighter edition.
To quote, we need four things
- The market you want to launch in.
- What you run on today, if anything.
- Whether the licence exists, is pending, or is the question.
- The studios and payment methods your players expect.
06 · Asked first
The three questions that arrive before the demo.
Who files the returns, you or us?
You do. The licence is yours, and so is the filing. The platform produces the data and the reports behind it, and carries the automated part where a market runs one.
Live operators in Latvia and in Bulgaria reconcile turnover and GGR with the regulator every month, from the platform’s numbers.
Is the platform certified for our market?
The player account platform is GLI-19 certified, held for the UK, Bulgaria and Latvia, and certified against the AGCO Registrar’s Standards for Internet Gaming in Ontario. We are licensed by the UK Gambling Commission as a remote gambling software supplier.
Where a market needs a new certification, the platform goes through the accredited laboratory in about two months, and the certifications we hold carry into the next submission. The licence register →
Can you plug in our national register?
GAMSTOP, PIPARS and the Bulgarian register are integrated today, and an exclusion from a national register is kept apart from a player taking a break. If your market runs one we do not have yet, we integrate it, and the exclusion it sets is the same account state your team already works with.
Tell us the licence. We send back the compliance fit.
The market, the licence you hold or expect, and what you run on today. The fit comes back in writing: what the platform covers, and the certifications that carry over.