Security & Trust
Each party's data stays its own.
GameShield Pro sits in the middle of provider–operator traffic, so trust is the product. Here's how the architecture enforces it.
Conflict isolation
GameShield Pro is a joint venture with Vivo Gaming — and built so that's not a conflict. No founder-shareholder can suppress, delay, or edit an alert about their own system; every party gets the same read-only evidence for incidents touching its traffic.
Strict per-tenant scoping
Every read of events, alerts, and cases goes through a tenant ViewScope — never a shared query. An operator sees only its own dimension; a supplier its own across operators; a SOC only the clients explicitly assigned to it. An unassigned SOC sees nothing by default.
Inbound integrity
A strict contract validates every inbound event; a malformed feed is rejected. An event whose operator/supplier id the API key doesn't own is quarantined and raises a spoof case — it never reaches another tenant's console.
Signed, reliable egress
Outbound alerts are Ed25519-signed (verifiable against a published key), connections are pinned to vetted public addresses to defeat SSRF/DNS-rebinding, and delivery retries with backoff. Every attempt is logged.
Reviewed + audited
The stack is reviewed against the OWASP Top 10, dependencies are audited, and detection-rule outputs are independently audited. SOC 2 and ISO 27001 readiness are on the roadmap.
Data minimization
We monitor transaction metadata, not player identities. Cross-tenant market benchmarks publish only k-anonymized ratios — never another tenant's raw numbers.
Security questions or want our posture summary? Talk to us.
See it on your own traffic.
We'll run a monitored pilot on a slice of your seamless-wallet feed and show you the drift, errors, and fraud signals it surfaces.