Cricket Core Media Privacy Policy

Version 1.2 | Prepared 10 October 2026 | Effective from the publication date shown with this version in the app

1 Who we are

Cricket Core Media operates Cricket Core, a cricket media and community service offering player profiles, cricket records, team and academy tools, live scoring, broadcasting and related features. This policy covers our handling of personal information through the website, app and supported desktop or mobile versions, including free access, Ad-Free subscriptions and Pro features when offered.

Operator: Cricket Core Media. Address: LP7 Boyce Trace, Chin Chin Road, Cunupia. Privacy, legal and support contact: cricketcorepro@gmail.com.

This policy explains our handling of information. Independent stores, fundraising organisers, advertisers and payment providers also have their own responsibilities and notices. Agreeing to our Terms or acknowledging this policy does not amount to consent to every optional use of information.

2 Information we handle

Account information includes names, email addresses, sign-in credentials and account identifiers, profile details, roles and subscription information. Email registration uses a name, email and password; Google sign-in is also supported. Information received through Google sign-in depends on the authorisation and provider response. Profile or registration forms may ask for additional information relevant to the activity.

Cricket records can include player names, photographs, birthdates, sex or gender, nationality, playing roles, batting and bowling styles, clubs, teams, fixtures, results, scores, statistics and performance assessments. Academy, team or player registration tools can also handle guardian and emergency contacts, clothing preferences, attendance, assessments, and health information such as allergies or health concerns where supplied. Only provide information relevant to the activity and authorised for that use. Do not put medical details, private contacts or a child's full birthdate in public descriptions or media.

Content includes photos, video, audio, broadcasts, replay clips, messages, comments, listings, campaign descriptions and other supported submissions. Feedback and support information includes the report or request, relevant supporting details and communications about it.

Payment-related records can include a PayPal subscription or transaction identifier, selected plan, billing interval, status, billing period and payment confirmations. PayPal handles information supplied to its payment service under its own notice. Our records and the provider's financial records are different; this policy does not claim that every payment method has the same data flow.

Technical information includes the information received in normal server requests, such as IP address and request details, and information associated with browser or app storage. Site analytics use a browser visitor identifier, page path, event identifier and event time to count visits. Features may request access to the camera, microphone, files or notifications. The operating system or browser presents permission controls; declining a permission may prevent the relevant feature from working.

3 Sources and purposes

Information comes from you, authorised team or academy contributors, other users supplying cricket records and media, sign-in or payment providers, and use of the service. A profile or match record can concern a person who has not opened an account. Possession of information about another person does not by itself authorise its upload or publication.

We use information to provide accounts and roles; maintain player, team, academy and match records; display content; support scoring, broadcasting and replay features; manage paid access; provide support and reporting; measure use; display advertising where enabled; and administer the service. Relevant records may also be used to investigate misuse, maintain the service and comply with applicable legal obligations. Uses requiring a particular legal basis or consent remain subject to those requirements.

4 Public information profiles and merges

Names, cricket participation, statistics, photographs and other content submitted to public profiles or coverage can be visible to other people. A public audience may include visitors who are not registered users. Content can be copied, captured or shared, and external copies may remain after a correction or removal from Cricket Core.

Player profiles can be self-claimed or associated with an authorised account or team. A self-claim is an assertion of identity, not a general promise that Cricket Core independently verified the person. Duplicate profiles or records may be merged or consolidated, affecting the records attributed to a player. Claims and merges do not transfer another person's copyright or make incorrect records accurate.

To dispute identity, an incorrect association, a merge or an inaccurate record, use the app's feedback/support facility or email cricketcorepro@gmail.com. Explain the record concerned and the requested correction. Provide evidence relevant to the request without including unnecessary private information.

5 Children and sensitive information

The service includes youth cricket and may display public photographs of children. Anyone submitting a child's photo, voice, footage or information must have the necessary authority and permissions, including parent or guardian permission where required. A photo made public may be copied or shared by its audience.

Full birthdates are collected where needed for league age limits, participation or identity checks. The structured player and registration interfaces restrict full dates to the player or linked guardian account and assigned officials for the relevant team, academy or competition. Other viewers receive age information where available. League officials' birthdate access does not by itself grant access to unrelated health or private-contact details. Identity documents are restricted to authorised verification access. Having a public profile, an unclaimed profile or a self-selected role does not by itself confer authority.

Do not put a child's full birthdate, health details or private contacts into public descriptions, posts, score commentary or broadcasts. These controls cover supported structured records and do not automatically screen free text, images, footage or external copies. Use less detailed age information where sufficient and report inappropriate exposure to cricketcorepro@gmail.com.

Parents, guardians and affected players may contact us about a child's information, permissions, correction or removal. We do not represent that an automated age-verification system, parental dashboard or automatic image screening operates throughout the service. Health and emergency information should be supplied only where needed for an authorised activity and should not be published as general profile content.

6 Live coverage recordings and permissions

Scoring and broadcasts can disclose names, participation, images and voices while an event is in progress. Broadcasting, recording and replay tools can also create files or clips on a device or supported server. Whether coverage is retained, replayed, downloaded or shared depends on the feature and the contributor's configuration. Participants should not assume that a live stream disappears when the match ends.

Contributors must obtain required event, venue, media and personal permissions, including those concerning children. Connected broadcast destinations and software may handle information under their own terms. Removing a recording from one device or service does not necessarily remove a copy on another service. Report unauthorised footage or personal information through support or the privacy contact.

7 Advertising local storage and analytics

Free access is supported by advertising. The app contains integrations for Adsterra advertising and sponsored links, including resources served through profitableratecpmnetwork.com. Third-party advertising resources can receive technical information when loaded or clicked and may use cookies or similar technologies under their own practices. Advertising integrations and their availability can change; we do not guarantee that all ads are contextual or that no provider uses identifiers.

Cricket Core also uses an impact.com publisher tag, loaded from utt.impactcdn.com, to transform eligible external brand links into affiliate tracking links and measure impressions. This can involve page and referring URLs, link or campaign details, session identifiers and technical request information. A qualifying referral may generate compensation under an external brand programme. This is separate from Cricket Core's no-commission policy for independent Pro store sales and fundraising contributions. The supplied integration invokes link transformation and impression measurement; acknowledging this policy is not consent to optional tracking where separate consent is required.

Advertising providers and integrations may change. Material changes must be reflected in the notice and any controls required for them.

Browser and app storage support sign-in state, preferences, offline licences, local cricket records, replay functions and visit measurement. Ad-Free access is a paid advertising benefit; it is not a promise that essential storage, first-party usage measurement, third-party destination processing or sponsor material inside a user's content disappears. Browser storage and device permission settings provide relevant controls, although changing them may affect features.

8 Subscriptions independent stores and fundraising

Monthly and annual Ad-Free subscriptions use PayPal recurring payments. Subscription status and payment identifiers support access and billing administration. Cancelling a subscription, deleting an account and removing the app are distinct actions; do not assume that one automatically completes the others.

Pro is separately priced and does not automatically form part of an Ad-Free plan. Where Pro store or fundraising tools are offered, operators configure their own payment methods and arrangements. Cricket Core charges its Pro subscription fee and no Cricket Core transaction commission on sales or contributions. Payment providers may charge their own fees.

Listings, campaigns, operator contacts, payment instructions and any supported order or donor information may be handled to provide those features. What a provider or operator receives depends on the payment arrangement. Review its notice before giving buyer or donor information. We do not make an unverified claim that funds always bypass Cricket Core, that we hold funds in escrow, or that every operator is verified. Additional processing must be explained before a new payment integration or feature is used.

9 Recipients and international handling

Information is disclosed to the audience of public content and, as appropriate to the feature, authorised activity organisers and service providers. The service uses a PocketBase-backed server for accounts and records, browser/device storage for local functions, supported broadcast and file facilities, Google for supported sign-in, PayPal for its payment service, and the configured mail service for communications. Advertising providers receive information associated with their resources as explained above.

Hosting, advertising, sign-in, payment and broadcast providers may process information outside Trinidad and Tobago. The service does not represent that all information remains in Trinidad and Tobago. Any transfer or disclosure must meet the applicable legal requirements. We may disclose relevant information when lawfully required or necessary for a legally permitted service or rights-protection purpose; this is not unrestricted permission to disclose personal information.

10 Retention deletion and security

Retention is determined by the purpose and circumstances of each category rather than a single period for all information. Relevant considerations include maintaining an active account or cricket record, providing a recording or supported feature, resolving reports or disputes, managing subscriptions, keeping records required by law, and maintaining backups. Information should not be kept longer than needed for a lawful purpose. We do not promise a fixed automatic deletion deadline for every category.

The app has a configured routine to remove first-party page-view records older than 180 days and a routine to remove bin entries older than 30 days. The bin is available in App Settings for supported deleted records. Restoring a record may not recover attached files, deleted linked matches or other dependent records. Permanent deletion from the bin removes that entry; it is not a promise that all underlying files, public cricket records, payment data, external copies or backups are erased on the same schedule.

Account closure does not by itself establish that historical match records, contributions concerning other people, provider payment records or every backup copy has been removed. Requests to correct, close or remove information should specify what is concerned. We will consider applicable rights, the information's purpose and any lawful reasons for retaining it. No complete self-service deletion or universal erasure mechanism is promised by this policy.

Online services and devices carry security risks. This policy does not claim a security certification, universal encryption of stored information, automatic incident response, or an unverified notification deadline. Applicable obligations continue to apply. Keep credentials secure and notify support of suspected account misuse.

11 Requests communications and policy changes

Contact cricketcorepro@gmail.com for privacy questions, access or correction requests, account closure requests, child-photo concerns, or complaints. Use the app's support/feedback facility for service reports. We may ask for information reasonably needed to identify the relevant record and your authority. Available rights, exceptions and response requirements depend on applicable law.

App Settings at https://cricketcore.pro/#/settings lets an account choose whether to receive optional email news and updates, the weekly digest and daily feature spotlight. Optional mailing-list messages require the saved email opt-in. Turning off email news and updates excludes the account from those digests and marketing newsletters. Settings also control new in-app activity alerts, device notifications, and notification sound and vibration. Browser and operating-system permissions remain separate. Turning off device alerts removes the account's registered push subscriptions; existing notification history is not deleted by that choice.

Account, payment, security, verification, support and policy-change messages are service communications and may still be sent. An account can manage optional-message preferences at https://cricketcore.pro/#/legal/settings without accepting a new policy version. Acknowledging this policy is not marketing consent or permission for every optional tracking use. Contact cricketcorepro@gmail.com if a preference does not work as expected.

Published policy revisions are versioned. Users are asked to acknowledge current policies before completing registration or proceeding with authenticated member access, and a published revision queues a notification to existing accounts with email addresses. Delivery depends on the mail service; an email queued or accepted by a mail server is not proof that it reached an inbox. Optional processing still requires any separate notice or consent required by law.

Cricket Core is in beta through 31 December 2026. Beta status does not waive privacy duties. Trinidad and Tobago law governs the service subject to other mandatory laws that apply. The publication record supplies the effective date for this version.