Who is Fidelis for? Sweepstakes and social casino operators who want one place for player data, segments, campaigns, rewards and responsible-gaming controls.
How does our data get in? Your platform sends signed events (registrations, purchases, plays, redemptions, consent changes) to one endpoint. Duplicates are ignored, so you can resend safely.
Does Fidelis touch our ledger? No. It asks your platform for each reward through one signed call, and your code decides and writes. A retried call is never paid twice.
Can a marketer skip a guardrail? No. Consent, responsible-gaming suppression, frequency caps, quiet hours and regions run before every send, and there is no setting to turn them off.
What does the AI do? It turns plain English into segment rules, drafts message variants and summarises campaign results. It never sends anything: a staff member approves first, and no personal player data goes into prompts.
How do you keep operators apart? Every table carries a tenant ID and Postgres row-level security fails closed, so a request can only ever see its own operator’s rows.
What can we show a regulator? An export of the audit log, with a tamper check across every row, and a per-player trace of why each message or reward happened.
Which channels work today? Email, push and web push, the on-site inbox and Telegram. SMS is ready behind an adapter and switched on per operator.
Can it live in our own cloud? Fidelis runs as a set of containers with Postgres and Redis. Talk to us about hosting on your infrastructure.
What does a demo cover? Thirty minutes on a demo operator with simulated players: a segment, a journey, a held send and its audit trail.