Privacy
How information is handled
Sports Support separates public profile information from private account, document, communication, and payment information.
Information collected and why
| Category | Purpose | Who can access it | Public? |
|---|---|---|---|
| Account details: name, login email, mobile number, role, status, password hash, acceptance and adult-confirmation records | Sign-in, account security, eligibility, approval and communication | The account holder and authorised administrators as needed | No |
| Sportsperson profile: date of birth, address, biography, sporting history, goals, contact preferences and photograph | Build and review a support profile and establish adult eligibility | The sportsperson and authorised administrators. Donors and visitors receive only the approved public snapshot, which excludes contact details, full address and date of birth | Only approved profile fields |
| Identity proof, age proof, sports certificates and supporting documents | Administrator review of the application and sporting evidence | The owning sportsperson and authorised administrators through protected download routes | No |
| Support requirements, amounts, item links and progress totals | Explain current needs and distinguish commitments from confirmed direct support | Approved profile visitors and eligible donors; draft information remains in authorised account/admin screens | Approved requirements and totals may be public |
| Bank account details, UPI IDs, instructions and QR codes | Allow direct support outside the platform | The sportsperson and authorised administrators. A verified method is disclosed to signed-in, active approved donors only when the sportsperson has separately consented to that disclosure | No |
| Commitments and direct-support reports | Record intended support separately from confirmed support and manage disputes | The participants and authorised administrators according to the existing workflow; public statistics use limited aggregate activity | Only limited approved or aggregate information |
| On-site messages and reports | Participant communication, safety reporting and moderation | Conversation participants; authorised administrators may access a reported conversation for review, with an access audit | No |
| Audit, security and access records, including timestamps and IP addresses | Security, fraud prevention, accountability and investigation of access to sensitive features | Authorised administrators, with restricted retained-record access where configured | No |
Payment-detail consent
Consent to share a bank, UPI, or QR method is collected separately for each payment method and stored with a timestamp and consent version. It is not inferred from general Terms acceptance. Creating or editing a method returns it to Pending Verification. A method is hidden from donors unless its administrator status is Verified and its current disclosure consent is recorded. Donor views and reveals are audited without writing the payment value into the audit entry.
Storage and protection
Identity, age and certificate files, profile photographs, payment QR images, and support receipts use private storage rather than public storage URLs. Controllers check the signed-in user and role before serving a file. Bank and UPI payloads are encrypted at rest and hidden from ordinary model serialization. Public pages and search results do not include private document paths, contact details, bank account numbers, UPI IDs, or QR images.
Retention, correction and account choices
Information is kept while needed to operate an active account, review profiles, provide messaging and support records, resolve reports or disputes, and maintain required security and audit records. The application does not promise that every record is kept forever.
Account holders may correct editable profile information, request administrator-assisted correction after submission, temporarily deactivate, or request permanent closure from the Privacy & Account page. A closure request has a configurable cooling period, currently 30 days, during which cancellation is available unless processing has completed.
After the cooling period, the scheduled closure process removes or anonymises unnecessary profile data, private messages, payment values and private files when there is no case-specific legal hold. Limited retained records receive a recorded reason, basis, review date and scheduled deletion date. An active legal hold pauses only the records covered by that documented case.
Adults only
The service does not accept registrations, profiles, documents, payment details, or commitments from anyone under 18. A separate adult self-declaration is required before the registration form requests personal information. Donors are not asked for identity documents solely to check age. Sportspersons provide a date of birth later because the existing profile and age-proof review requires it. Their account remains pending, private, and ineligible for donor support until an administrator verifies the current age-proof document and approves the account. If review finds that an applicant is under 18, the application is rejected and its profile information and private files are removed unless a documented, case-specific legal retention requirement applies.
Questions, corrections and safety reports
Signed-in users can use the existing Help & Support, Messages, profile-correction, Privacy & Account, and reporting tools. Eligible donors can use “Report profile / suspected fraud” on an approved profile. No external contact address or operator identity is stated here because none is configured in the application.
Sign in to use account controls