Privacy Policy
How PlayrSync collects, uses, shares, protects and retains personal data across its sports community platform.
This document is designed to support applicable privacy obligations. Rights may vary by jurisdiction, and final legal counsel review is required before production reliance.
Who operates PlayrSync
PlayrSync operates the PlayrSync Alpha sports community platform. Current contact details appear in the Grievance and Contact Information policy.
This operational draft is subject to final legal review and is designed to support applicable privacy obligations. It is not a certification or warranty of legal compliance.
Scope and jurisdictions
This policy applies to public visitors, account holders and people represented in Athlete, Guardian, Club, Organizer, Professional and Business workspaces.
PlayrSync is India-first. Indian privacy references include the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025, subject to applicable staged commencement and legal review. GDPR-specific rights apply only where its territorial scope applies to the relevant processing.
Data you provide
Account data may include name, email, phone number, password credentials in hashed form, timezone and workspace choices.
Profile and workspace data may include biography, sports, experience, location, public links, Club or Organizer identity, Professional or Business details and uploaded Media.
Information marked optional may be left blank unless a particular workflow explains why it is required.
Athlete, Guardian and child data
Athlete profiles may include date of birth, gender, height, weight, dominant hand, language, sports, positions, experience, categories and profile visibility.
Guardian workflows can create private dependent Athlete profiles and connect registrations, reservations, Results and Certificates to the child. Guardian authority and age-transition enforcement require continued operational and legal review.
Medical and emergency information
Restricted Athlete and registration fields can include blood group, allergies, medical conditions, medications and emergency contacts.
This information is used only for the profile, registration, safety or authorized operational purpose for which it was supplied. It is not included in public Athlete discovery projections.
Clubs, Events and registrations
Club data may include membership, role, team, training and attendance records. Event data may include ticket selections, add-ons, registration answers, waivers, discounts, taxes, QR Tickets, bibs, check-in and reservation activity.
Reservations keep configuration, tax, discount and cart snapshots so historical booking records do not depend entirely on later Event changes.
Payments and transaction data
PlayrSync may store payment order identifiers, payment status, amounts and audit records. Razorpay handles payment-entry information in its checkout flow; PlayrSync does not claim to store full card details.
Production payment activation remains subject to external webhook delivery revalidation. Refund automation is not currently promised.
Organizer verification and financial details
Organizer operations may collect legal identity, tax, verification documents and payout-account details. Account numbers are protected and public views expose neither complete bank details nor private verification documents.
Professional and Business verification fields currently provide a foundation. No third-party KYC assurance is made for those profiles.
Media, Community and public visibility
Media uploads may include files, captions, metadata, variants, albums, collections, attachments and moderation reports. Community data may include posts, comments, reactions, polls, follows and visibility audiences.
Public profiles and content can be viewed and shared by others. Private Media, private profiles, follower or Club-member content and Only Me content are filtered by current authorization rules.
Results, Rankings and technical data
Published Results, splits, Rankings, Series and certificates may appear in public performance histories. Timing imports can use email or mobile solely for matching and must not expose those identifiers publicly.
Technical data can include IP-related request data, device or browser information available to server logs, session and access tokens, CSRF data, security events and operational logs.
Purposes and processing grounds
PlayrSync processes data to create accounts and workspaces, deliver requested services, enable discovery and Community participation, manage registrations, secure the platform, communicate transactional updates and meet legal or safety obligations.
Depending on context and applicable law, processing may rely on consent, a user-requested service or contract, compliance with law, safety and security, or other legally permitted grounds. Final classification remains subject to legal review.
Service providers and international processing
Relevant providers can include hosting and storage infrastructure, SMTP delivery services and Razorpay. Provider identities, regions, contracts and transfer mechanisms are reviewed in PlayrSync’s internal processor register and are not assumed where unverified.
Where data is processed across borders, PlayrSync will assess the applicable notice, contractual and legal safeguards before relying on them.
Retention and security
Data is retained for as long as needed for the stated purpose, platform security, fraud prevention, historical Results or booking integrity, dispute handling and applicable legal obligations.
A detailed retention schedule is still being operationalized. PlayrSync uses access controls, private storage for restricted documents, encrypted or hashed credentials where implemented, audit records and visibility filtering, but no system can guarantee absolute security.
Your controls and rights
Current controls include editing account and profile information, changing supported profile and content visibility, managing workspace state and submitting privacy requests for access, correction, completion, export, deletion or consent withdrawal.
Rights and response duties vary by jurisdiction. Identity verification may be required, and deletion may be limited where records must be retained for legal, fraud, payment, Result, safety or audit purposes.
Account closure, children and complaints
Workspace archive is not the same as account deletion. PlayrSync does not currently promise immediate automated deletion across every data domain; requests receive review before action.
Guardians may request correction or deletion relating to a child they are authorized to manage. Safety concerns and grievances can be submitted through the Privacy & Data Requests page or the configured grievance contact.
Changes and contact
Material updates will change the version and last-updated date on this page. Features may change during Alpha, but Alpha status does not reduce PlayrSync’s commitment to privacy and security.
Use the Grievance and Contact Information page for the current Privacy Contact, Grievance Contact and support channels.
