Built to protect your players and your property.
Sonar is the platform your team uses to reach players by voice and SMS — gift reminders, confirmations, invitations, and win-backs. Compliance isn't a feature we bolt on — it's how the platform is designed. Here's exactly how consent, security, and disclosure work, and who's responsible for what.
Five things that are always true on a Sonar call.
These aren't settings a campaign can switch off. They're enforced in the agent itself and shown to your team as locked rules in the portal.
Every call opens by telling the player they're speaking with an automated assistant on behalf of the property. No impersonation, ever.
Locked ruleA player can opt out mid-call, by text, or by callback. Once they do, they're removed and never contacted again — no talking them out of it.
Locked ruleThe agent never connects a gift to wagering, spend, points, tier, or qualification. It's a thank-you to a member — a critical line for responsible gaming.
Locked ruleOn an informational campaign the agent answers a player's factual question briefly, then returns to the gift. It never pivots a reminder into a sales pitch.
Locked ruleReach, confirmation, opt-out, sentiment, and redemption lift are reported against a matched holdout group — proof, not promises.
If a player answers in another language, the agent follows and switches back naturally — inclusion built in, not a separate campaign.
The classification that keeps consent where it belongs.
Every campaign is classified before it runs. The classification decides which consent applies — and the platform holds you to it. You choose; Sonar surfaces the requirement so nothing slips through.
A reminder about something already earned
Gift pickup reminders, confirmations, and service notices like a closure or an hours change. These run on your standard players-club consent. This is the everyday Sonar call.
A reason to visit, spend, or play
Events, offers, come-back messages, drawings. Promotional outreach requires marketing consent — a higher bar. The portal blocks a promotional campaign until you confirm you hold that consent for the list.
Why it's built this way: a call's compliance treatment follows the purpose it was placed for. An informational gift reminder stays informational even when a player asks a question — the agent answers briefly and returns to the gift. Proactively promoting would change what the call is, so the informational agent simply can't do it. When you do want to run promotional outreach, you classify it as such and confirm consent up front, and a purpose-built agent handles it within that scope.
You operate the platform. We provide it.
Sonar is a tool your team runs — not a service that runs your outreach for you. That distinction protects you, and it's reflected in how responsibilities divide.
Your property owns
- Consent. The permission to contact your players belongs to you and travels with your player file.
- Who's contacted. You choose the list, the segment, and the timing for every campaign.
- Classification. You classify each campaign, and confirm marketing consent for promotional sends.
- Your content. You define what the host says; you approve every word before it goes live.
- DNC & opt-outs. You maintain your suppression lists; the platform captures opt-outs for you to honor.
Sonar provides
- Platform access. The dashboards, campaign tools, and voice/SMS infrastructure you operate.
- Configuration. GPS enters your own words and rules into the platform exactly as you specify — you stay the author.
- The guardrails. Disclosure, opt-out, and no-play-linkage enforced in the agent itself.
- Security. A SOC 2 Type II platform with PII minimization and configurable retention.
- The measurement. Honest reporting against a holdout control, every cycle.
Enterprise-grade, and independently verified.
Sonar runs on a SOC 2 Type II platform. Our live security posture, certifications, and subprocessors are published in our Trust Center — not asserted on a page you can't verify.
| Area | How Sonar handles it |
|---|---|
| Certification | SOC 2 Type II. Report available under NDA through our Trust Center. |
| Player data | Processed only to run your outreach. Never sold. Model-training terms for each subprocessor are documented in your program agreement. |
| PII minimization | The platform is configured to minimize personal data exposed to the AI, with PII redaction available. You control which fields you upload. |
| Data retention | Configurable retention windows, with automatic deletion when the window expires. |
| Tenant isolation | Each property's data is isolated. One property's data is never accessible to another. |
| Recording & transcripts | Available to you for QA and audit. Two-party-consent disclosure supported where you contact those jurisdictions. |
| Subprocessors | Our voice/AI infrastructure providers operate under a Data Processing Addendum. Current list published in the Trust Center. |
Live certifications, security controls, and subprocessors — maintained continuously, not point-in-time.
The questions your compliance team will ask.
Is this telemarketing?
Who is responsible for TCPA consent?
What happens when a player asks "anything new going on?"
Does the AI ever tie a gift to gambling?
How is our player data handled?
Can you produce a SOC 2 report?
How do players opt out, and does it stick?
Do you handle call-recording consent?
This page describes how the Sonar platform is designed and configured. It is provided for information and is not legal advice. Compliance obligations depend on your lists, your consent records, and the laws of the jurisdictions you contact. The allocation of responsibilities between your property and GPS is governed by your Sonar platform agreement.
Compliance you can show your regulator.
We'll walk your team and your compliance reviewer through a live Sonar call — disclosure, opt-out, the guardrails in action — and share the documentation your procurement process needs.