Security & Data Handling

Why organizers use this

• Data is stored on managed cloud database infrastructure, not a single local device
• Role-based access limits who within an organization can see sensitive player data
• Audit logs track administrative actions for accountability
• A designated grievance officer is available for DPDP Act data principal concerns

Typical use cases

• An organizer reassuring players about how their registration data is handled
• An association wanting to understand data practices before adopting the platform
• A committee evaluating role-based access before assigning logins to volunteers

In plain language

We're a small operating team, not a large enterprise security department — what we can tell you honestly is that data lives on managed cloud infrastructure, access is role-scoped, and administrative actions are logged. We'd rather state that plainly than make broader claims we can't back up.

Frequently asked questions

Where is player data actually stored?

On managed cloud database infrastructure, not on any single organizer's device — see our privacy policy for full details on data handling.

Who can see a player's phone number or payment reference?

Access is scoped by role within an organization — not every team member automatically sees every player's contact or payment details.

Is there someone to contact about a data privacy concern?

Yes, we have a designated grievance officer for DPDP Act, 2023 data principal complaints — contact details are listed on our contact page.