BoundaryBack to home →

PRIVACY

Privacy policy

Effective 18 August 2026

Boundary is a cricket team, tournament and scoring service. This policy explains what information the service handles and which information becomes public.

Information we collect

When you sign in with Google, we receive your name, email address, profile image and the identifiers needed to maintain your account and session. We do not receive or store your Google password.

Team managers and scorers may enter team names, player names, playing roles, fixtures, venues, line-ups, ball-by-ball events, results and tournament information. Technical records can include session identifiers, timestamps, request logs and error details.

Public cricket records

Fixtures, live scores, completed scorecards, team names, registered player profiles and performance statistics are designed to be publicly viewable. A team manager must have authority to register a player and publish their cricket information. Quick-match players do not enter the public player directory, although the match scorecard itself can be public.

How we use information

We use information to authenticate users, operate teams and tournaments, enforce manager and scorer permissions, maintain historical scorecards, calculate standings and player statistics, recover scoring sessions, prevent conflicting scorers, secure the service and diagnose faults.

Cookies and sessions

Boundary uses essential, secure cookies for sign-in, scorer access and quick-match recovery. These are required for the requested features and are not used for advertising.

Service providers and storage

Google provides authentication. Cloudflare provides application hosting, database storage, security and operational logs. Information may be processed in locations where those providers operate, subject to their safeguards and terms.

Retention and deletion

Registered match records are retained as historical cricket records. Account sessions expire automatically. Revoked scorer sessions and score corrections may be retained as an audit trail. Quick-match data may be removed after it is no longer reasonably needed. You may request correction or deletion of account information, subject to legitimate record-keeping, security and dispute requirements.

Children and player information

Managers must obtain any consent required before entering information about children or other players who cannot provide it themselves. Do not enter sensitive personal information in player names, match notes or other public fields.

Security

Boundary uses encrypted HTTPS connections, restricted manager permissions, hashed access codes, protected session cookies and provider-managed authentication. No internet service can guarantee absolute security, so scorer and tournament codes should only be shared with intended recipients.

Your choices and contact

You can ask to access, correct or remove information associated with you. Public match results may be preserved where they form part of an official historical record.

Contact rishikcaptain@gmail.com for privacy or account requests.

Changes

We may update this policy as the service changes. The effective date above will be updated when material changes are published.

Boundary

Community cricket, properly recorded.

PrivacyTermsPublic matches
© 2026 Boundary