Legal

Privacy policy

What IndianPlayers stores, why, and who can see it (draft pending legal review).

This describes the data the platform actually stores, taken from its database schema rather than from a template.

What is stored

Account
Your name, email address, role and a scrypt hash of your password. The password itself is never stored.
Sessions
A hash of your session token and its expiry. The token in your cookie is not stored in readable form, and the cookie is HTTP-only so scripts cannot read it.
Sign-in attempts
Failed attempt counts per email address, used to lock out repeated guessing. Cleared on a successful sign-in.
Records you create
Players, teams, clubs, academies, stadiums, districts, franchises, events, stores and programs, each linked to your account as owner.
Activity
Competition entries, fixtures, results, offers, orders, payments, tickets, returns, auctions and bids, contracts and transfers.
Financial records
Journal entries and revenue split calculations. These are append-only and are retained for reconciliation.
Support cases
Messages between you and the platform team, readable only by you and an administrator.
Audit log
A record of significant actions and who performed them. Append-only.

What is not collected

  • No third-party analytics, advertising or tracking scripts are loaded by this application.
  • No identity or KYC documents are collected, because that capability is not built.
  • No location data, contacts or device identifiers are collected.
  • No payment card details are collected or stored — no payment provider is configured.

Cookies

One cookie is set: a session cookie named ip_session. It is HTTP-only, restricted to same-site requests, marked secure in production, and expires after eight hours. There are no advertising or analytics cookies.

Who can see your data

  • You, for records you own.
  • A counterparty, for a contract or transfer you have proposed to them.
  • Anyone, for records you have explicitly published — and only the reviewed fields that publication exposes.
  • Administrators, for support and moderation. Administrative access to records is written to the audit log.

Device storage

The installed web app caches only public, credential-free assets — the offline page and the app icons. Account data, tickets, payment requests and API responses are explicitly excluded from the cache, so they are not readable from the device when you are signed out.

Your rights

You can withdraw publication of any record at any time. Self-service export and account deletion are not implemented yet; until they are, an administrator must action those requests. Append-only financial and audit records are retained for reconciliation and are not deleted.