This page is maintained by the Rollit team to answer common security and privacy questions about Rollit. It describes current, app-visible controls and is editable project content — not an independent certification or audit report.
Rollit runs on managed cloud infrastructure. The platform provider operates the underlying database, authentication and hosting services; the Rollit team is responsible for the application code, access rules, and how player data is handled inside the product. Players are responsible for protecting their own credentials, PIN and recovery email.
All traffic between your browser and Rollit is served over HTTPS/TLS. API requests authenticated as the signed-in user are constrained server-side by row-level access rules so that one player cannot read another player's account, balance or wallet data.
Rollit uses first-party cookies and local storage for sign-in sessions, preferences and basic product analytics. We do not sell personal data to third parties.
Rollit relies on managed providers for hosting, database, email delivery, push notifications, crypto payment processing and real-time voice/video during games. These providers receive only the data needed to deliver their part of the service.
If you believe you have found a security vulnerability, please email security@rollitplay.com with steps to reproduce. Please do not publicly disclose the issue until we have had a chance to respond.
Rollit is not currently certified under SOC 2, ISO 27001, PCI-DSS, HIPAA or GDPR adequacy programs. We follow common security best practices and continue to improve our controls; this page will be updated as that posture changes.