PRIVACY
POLICY.

Hosting and storage

The RCC website and Royal Scorer's shared online records use Hostinger hosting and a MySQL database for royalcricketclub.com. The selected hosting plan reports its server location as Arizona, United States, and its backup location as Boston, United States. Information submitted to the online service may therefore be stored outside India. Hostinger also provides the [email protected] mailbox used for account-related email. Cloudflare sits in front of the domain for traffic delivery and security and can process connection information such as IP addresses and request metadata; its infrastructure may process information in more than one country. See Cloudflare’s privacy policy for its practices. Local practice records remain on the phone unless you choose to export or share them.

Independent clubs and registration

Independent club registration collects the manager’s name and email, club name and locality, and consent timestamps. The password is chosen through an expiring email-verification link and stored as a hash. Verification proves control of the email address; it does not certify the club’s identity. Managers control their own clubs and authorised tournament records, with RCC retaining platform moderation powers. Participating clubs confirm their own tournament participation and keep control of their squads. Club-submitted results must not be presented as independently verified RCC records.

Royal Scorer mobile app

This policy also covers Royal Scorer for Android and iPhone, operated with the RCC website. Local practice match details, player names entered for those matches and scoring events are stored on the phone. Match contents are encrypted with keys held in the device’s secure storage. Local practice records do not automatically create online player profiles and are not automatically uploaded to RCC.

When you connect to an RCC server and sign in, the app sends authentication requests and authorised official scoring actions to that server. It keeps a local copy and pending actions for offline use. The server controls account permissions, shared player identities, club memberships and official records. A successful sign-in does not give permission to edit every player or match.

PDF scorecards and event-review exports contain match information and player names. They are shared only when you choose a destination in the phone’s share menu. Export files in temporary app storage are eligible for cleanup after 24 hours when the app next runs its cleanup; copies saved or shared elsewhere are not removed by that cleanup. Avoid sharing private exports publicly.

The current app does not include advertising or behavioural analytics. The hosting details above identify the selected online storage and email provider. Apple and Google process app distribution and store-related information under their own service terms.

You can initiate an account or personal-data deletion request through the Royal Scorer account and data deletion form. Deleting local practice data does not delete an online account, and an online deletion request does not remotely erase files on your phone.

1. Who is responsible for the information?

Royal Cricket Club (“RCC”, “we”, “our” or “us”) operates this website for club, cricket, tournament and community activities in Mehatpur, District Una, Himachal Pradesh, India. Privacy questions, correction requests and grievances may be sent to [email protected].

2. Information we collect

Depending on how you use the website, RCC may collect:

• Trial applications: name, date of birth, location, contact details, cricket role and experience, optional video link, and parent or guardian details and consent where the applicant is under 18.
• Contact enquiries: name, email address, optional phone number, enquiry category, subject, message and consent time.
• Player and club records: approved profile information, memberships, squads, match participation and cricket performance. Dates of birth and private contact details are not displayed publicly.
• Administrator accounts: name, email, role, account status, authentication information, two-factor setup state, invitation state and security/audit events.
• Uploads and historical records: club-approved photographs, logos, news, gallery items, kits, spreadsheets and associated record details.
• Technical information: necessary session, security and CSRF cookies; and, for security audit events, IP address and browser/user-agent information.

3. Why we use it

RCC uses personal information only for identified club purposes, including reviewing trial applications and enquiries, administering teams and tournaments, maintaining verified cricket history and statistics, operating authorized accounts, protecting the website, investigating misuse, keeping an audit trail, and publishing information only after the relevant RCC approval and visibility controls are satisfied.

4. Consent and choices

Trial and contact forms require a clear consent action before submission. You may ask to withdraw consent for future use by contacting RCC. Withdrawal does not automatically require RCC to erase information that must be retained for legitimate security, dispute, record-integrity or legal reasons. RCC will review each request and explain the outcome.

5. Children and young players

RCC treats information about children with additional care. Trial applicants under 18 must provide a parent or guardian’s name, contact information and consent. A minor player cannot enter a published squad or receive a public profile through the current administration workflow without recorded guardian consent. Parents or guardians may contact RCC to review or correct a child’s information.

6. Public information

Approved public pages may show a player’s display name, cricket role, approved photograph, club membership, squad participation and published match statistics. They do not show dates of birth, private phone numbers, email addresses, guardian details, trial applications or contact enquiries. RCC administrators can keep profiles hidden or private.

7. Sharing and external services

Authorized RCC administrators and properly scoped club administrators may access information needed for their roles. RCC does not currently sell personal information. Public pages may link to or embed external services such as YouTube, Instagram and Facebook. Those services apply their own privacy practices when you visit or interact with them. The Live page uses YouTube’s privacy-enhanced embed domain, but YouTube may still process information when you play a video.

8. Cookies

The current website uses cookies necessary for sessions, sign-in security, two-factor authentication and protection against forged form submissions. RCC has not enabled advertising or behavioural-analytics cookies in the current application. If analytics, advertising or optional cookies are added later, this policy and any required consent controls must be updated before they are enabled.

9. Retention and deletion

RCC keeps information while needed for the purpose collected, cricket record integrity, account security, administration, disputes or applicable legal obligations. The website does not yet run an automatic retention-deletion schedule. RCC will complete routine verified account and personal-data deletion requests within 30 days after verifying the request. If an identity dispute or applicable legal retention requirement prevents completion within that period, RCC will explain the reason, identify the affected information and provide progress updates until the request is resolved. This commitment does not mean that all shared cricket history, restricted backups or copies held by others are erased within 30 days.

The current password-confirmed account and associated-data deletion action removes sign-in details, revokes sessions and management access, hides the currently owned player profile, and starts erasure of its personal fields, uploaded photos and the account's authored news/gallery content. A private receipt lets you check server progress after sign-out without disclosing your identity. Identity disputes, changed ownership, unsafe files or files still used by someone else remain pending for review; the receipt does not report these as completed. Owner accounts require ownership transfer first. Older app versions that offer sign-in erasure alone do not automatically request associated-data erasure.

Shared match IDs, original scoring events and performance totals remain to preserve other players' cricket history, with the erased profile's direct personal fields removed. This is de-identification, not a guarantee of anonymity: earlier shared copies may still link those IDs. RCC must assess any retained personal information and explain its reason and retention period. Restricted backup snapshots may contain older information; the current private erasure records must be replayed and checked before a restored database is promoted. Shared exports and copies cached outside RCC cannot be recalled by deleting an account.

On the phone, unresolved official actions must be reconciled or exported before deletion. Confirmed deletion removes that account's cached official matches and encryption keys on that phone; practice matches and other accounts' saved matches remain separate. For information outside the automated scope, use the account and data deletion page to submit a verified request. RCC must explain pending work and confirm completion; deactivating an account alone does not complete a deletion request.

10. Security

The current application uses role-based access, verified-email checks, mandatory two-factor authentication for Owner and RCC Admin accounts, encrypted two-factor secrets, hashed recovery codes, rate limits, validation, audit logging and publication gates. No system can guarantee absolute security. If you believe information is exposed or misused, contact RCC promptly.

11. Your requests and grievances

You may contact RCC to ask what information it holds about you, request correction or erasure, withdraw consent for future processing, or raise a grievance. Provide enough information for RCC to verify the request without sending unnecessary sensitive documents. RCC may need to preserve verified match records while correcting the identity or visibility attached to them.

12. Indian data-protection framework

This policy has been written with reference to India’s Digital Personal Data Protection Act, 2023 and the final Digital Personal Data Protection Rules, 2025. Their provisions have phased commencement dates. RCC must review its obligations as each applicable provision comes into force and obtain legal advice before relying on this policy as a compliance document.

Official references: DPDP Act, 2023 · DPDP Rules, 2025 · Official commencement notification.

Royal Scorer accounts, following and review records

If you use Royal Scorer's online community features, the service stores your account identity, expiring hashed email-verification challenges, player associations and verification state, private ownership claims, profile-review explanations, reports, appeals and review outcomes. Registration verifies mailbox control; it does not automatically verify a player identity or publish a profile. Identity approval and public publication are separate decisions, with additional guardian-consent checks for minors.

Reports and claim explanations are not public. Authorised reviewers can read them. A person whose ownership association is removed can see the review outcome and submit a private appeal, without receiving the reporter's private explanation. The parties cannot read each other's private appeal notes. Review outcomes intended for affected parties are shared with them. A reviewed content hold can hide a player, club, team, tournament or match from public surfaces without deleting its cricket history. The affected profile owner or club manager can appeal; releasing a hold does not automatically republish the record. Reviewed ownership changes preserve cricket performances and are recorded for accountability.

Following lists, in-app alert preferences and read status are private. Alerts are checked in the app; no SMS or background push service is used for these alerts. Public match pages show only eligible published records. Provisional live totals require separate publication approval. Optional YouTube links open an external service at your choice; Royal Scorer does not host, relay or record that video.

Sign-in erasure removes following, alerts, preferences, verification challenges and ownership associations and redacts the account's report and appeal prose. The current associated-data action also processes owned-profile and authored-material cleanup, with pending cases and backup restoration handled as described above. A historical claim approval does not imply that its account association remains active. A current owner can withdraw public-profile permission directly. Returning after withdrawal requires a new password-confirmed request bound to the current profile and independent permission review, including guardian verification for minors; consent approval keeps the profile private until a separate publication decision.

Player profiles, photographs and previous careers

An adult who creates their own player profile can activate it after verifying their email, without individual identity approval. Email verification proves mailbox control, not independent verification of the person or their cricket figures. Public discovery remains a separate choice; minors, existing-profile claims and disputed ownership retain additional checks. Optional gender and profile locality are private account details. Exact date of birth is not public.

You may select and preview a profile photograph. The service crops and compresses the image, removes its metadata and stores the processed photograph privately. It serves that photograph publicly only while the profile is eligible and shared publicly. You can replace or remove it. Club managers may separately upload logos, covers and news or gallery images for their club website; publication follows the club and content controls.

Previous career totals, source names, optional reference links and cutoff dates are supplied by the player. They are labelled separately from Royal Scorer records and do not enter Royal Scorer-only rankings or awards. Compatible totals may be combined, with rates recalculated from available underlying figures. Possible overlapping or undated matches prevent a combined total. Updating or removing imported figures leaves recorded match history unchanged; restricted audit records retain the revision history for accountability. The service does not retrieve another app’s account or collect its password.

Cricket connections and club websites

Adult users with eligible public profiles can request and accept mutual cricket connections. The service stores requests, acceptance or removal, blocks and each person’s own private labels such as friend or coach. These labels do not verify a qualification or team membership. Accepted connections can view already public cricket activity; acceptance gives no access to private matches, contact details or hidden profiles. Blocking removes the connection from activity and prevents new requests until unblocked. Account erasure removes its connection records. No contact book is uploaded, direct messaging provided or external invitation sent automatically.

Independent club websites use the same published club, team, tournament and result records as the app. Publishing a club page does not publish private practice, hidden players or private fixtures. Public links, QR codes and shared images can be copied by recipients; shared snapshots cannot be recalled and may become outdated after a correction or withdrawal.

13. Changes to this policy

RCC may update this page when the website, legal requirements or club practices change. The effective date above should be changed whenever a material revision is published.

Match administration and availability

The service stores permanent teams separately from temporary tournament squads, together with participation, fixture setup, selected playing XIs and captains. Private temporary player submissions do not automatically join a permanent roster or become public profiles. Your availability reply is associated with your current player account and the match arrangements you reviewed. Authorised management of your team can see your reply; other clubs and public spectators cannot. Changed arrangements require confirmation again. Removing an account removes its availability replies.

Organisers may enter match officials' names. These are encrypted in the online database and private by default. An organiser must confirm permission before enabling public display. Entering an official's name grants no scoring or account permissions. Submission identifiers and hashed request summaries prevent repeated tournament, match and temporary-player submissions from creating duplicate records; these summaries do not store a copy of the submitted personal information.

Awards and shared achievements

Player-of-the-match and tournament awards may include an organiser's selection reason and revision history. Private selections remain restricted to authorised management. Public selections require eligible public player profiles; hiding a profile removes its award from public responses. Calculated leaders use published completed scorecards and eligible public profiles, preserve equal totals and explain their limited coverage. They do not independently verify identity or scorekeeping.

You may choose to share an achievement PDF through your device's share menu. The app checks current public visibility again before creating that card. The card states its source, criteria and snapshot time. Copies held by recipients do not update automatically after a correction or removal.

Opponent requests and match insights

When a club manager publishes opponent availability, the service stores the selected team, chosen cricket type, overs, match time, venue or locality, public arrangements note and publishing account. Signed-in users can see current requests for eligible published teams. Interested clubs' responses and acceptance status are visible to the request's authorised management; each respondent can see their own response. Personal phone numbers and private contact details should not be placed in public arrangements notes. Closing a request removes it from the board and clears its note; expired requests are not listed. Account deletion removes that account's requests and responses, and its own request records are included in the password-protected account export.

In-app match alerts remain in the service and are read through the app. The current app does not register for background push notifications or send device tokens to Firebase. Recent-form and comparison screens use published completed records with the chosen filters. Match progress and partnership views use the recorded active delivery history, excluding deliveries marked as undone.