SnickCam logo
HomeLive BroadcastsSupportFeaturesHow It Works

SnickCam Privacy Policy

Version: v1.4.0 Last updated: 18 September 2026

This Privacy Policy explains how SnickCam ("SnickCam", "we", "us", or "our") collects, uses, stores, shares, and protects personal data when you use SnickCam products and services.

SnickCam provides cricket-related products and services, including account features, offline-first scoring, live match and overlay tools, tutorials, public match discovery, and optional notifications. This policy uses plain language so that players, scorers, parents, guardians, clubs, and other users can understand what happens to their information.

1. Who Controls the Data

SnickCam is operated by Kasun Nehinnage Don trading as SnickCam, an individual developer based in Scotland, United Kingdom, who is the controller of personal data processed through the Service unless another organization clearly acts as controller for its own use of the Service.

Privacy questions and requests can be sent to support@cricketclubbuilder.com.

The Service is made available worldwide. Users are responsible for ensuring that their use of the Service complies with the laws applicable in their jurisdiction.

2. Applications Covered

This Policy applies to:

  • The SnickCam website
  • The SnickCam Scorer iOS app
  • The SnickCam Scorer Android app
  • The SnickCam Scorer web app
  • SnickCam: Cricket Camera for iOS and Android
  • Public overlay pages generated for live score display
  • Account, profile, support, notification, and analytics preference features connected to the Service

This Policy is publicly available at www.snickcam.com/privacy-policy without signing in and is linked from the SnickCam homepage.

This Policy does not govern third-party websites, streaming platforms, app stores, identity providers, or services you access through links, embeds, or integrations outside our Service.

3. Information Users Provide

We collect the categories of information below depending on how you use the Service.

3.1 Account and identity data

When you create or use an account, we may collect:

  • First name
  • Last name
  • Email address
  • Password credentials if you sign up with email and password
  • Sign-in credentials or identity tokens supplied through Google Sign-In or Sign in with Apple
  • Account identifiers
  • Account creation date
  • Email verification status

3.2 Profile data

When you complete or edit your profile, we may collect:

  • Profile photo or avatar
  • Country or country code
  • Phone number
  • Date of birth, where this is collected for profile or service features
  • Player code
  • Batting style
  • Bowling style
  • Player role
  • Jersey number
  • Role or status data returned by the platform

3.3 Match, team, player, and scoring data

When you use scoring and match-management features, we may collect or generate:

  • Teams you create or manage
  • Player records you create, edit, or add to teams
  • Match records you create, update, search, score, stream, or manage
  • Match details such as title, description, venue name, match format, start time, and status
  • Match result and score summary data
  • Ball-by-ball scoring events, innings events, void or undo events, and sync metadata
  • Match media links you add, including public stream URLs, titles, provider names, and related metadata
  • Overlay configuration data, token status, and public overlay state data

Some of this information may relate to other people, such as players, team members, scorers, umpires, referees, or other participants whose details you enter into the Service. If you add information about someone else, you are responsible for having the authority and permissions required under applicable law and your organization's rules.

3.4 Support and communications data

If you contact us, we may receive:

  • Your email address
  • The contents of your message
  • Related troubleshooting details you choose to include

4. Automatically Processed Technical Information

We and our service providers may automatically process technical information needed to provide, secure, troubleshoot, and improve the Service. This may include:

  • IP address and standard request metadata
  • Request timing and network metadata
  • App version
  • Platform, such as iOS, Android, or web
  • Operating-system version
  • Device model and general device information
  • Language or locale
  • Crash, diagnostic, and reliability information
  • Protected device storage, local app preferences, and local app records needed for app features

When you open account-registration, club-creation, or organization-creation features, the app may make a best-effort HTTPS request to the third-party IP-geolocation service ipwho.is. The service necessarily receives your public IP address and standard request metadata and returns approximate geographic information. SnickCam reads only the returned country code to prefill the country selector. You can change or remove the suggested country before submitting the form. This request does not include your SnickCam authentication token, account ID, name, email address, or other profile information. If you submit the form, only the selected country code, not the geolocation response or your public IP address, is sent to SnickCam as part of the relevant account, club, or organization record. The provider may process request logs under its own privacy terms.

The app uses protected device storage and local app records to support offline scoring and session continuity. This may include access and refresh tokens needed to keep you signed in, local match records and pending synchronization data, app session state, onboarding choices, notification preferences, Analytics consent status, policy version and timestamp, and the Crashlytics enabled or disabled preference and update timestamp.

5. Optional Usage Analytics

Firebase Analytics is disabled by default. The first time a guest or signed-in user reaches the Home screen, SnickCam Scorer presents a short choice with equally prominent "Allow analytics" and "No thanks" options. Refusing does not restrict any app feature.

The legal basis for optional Firebase Analytics is consent under UK GDPR, EU GDPR, and applicable device-storage rules. The choice is stored locally on the device with:

  • Consent status
  • Consent-policy version
  • Decision timestamp

The choice is not synchronized with an account or between devices. SnickCam does not set a Firebase Analytics user ID. Analytics may use a pseudonymous app-instance identifier. Events may distinguish only signed-out, guest, and authenticated states.

When a user explicitly allows Analytics, Google Analytics for Firebase may process:

  • A pseudonymous app-instance identifier
  • App sessions and session duration
  • App launches, opens, and updates
  • Screen views and approved feature-interaction events
  • Operating-system version
  • Device model and general device information
  • App version
  • Platform
  • Language or locale
  • Approximate or coarse geography
  • The SnickCam app environment and build mode

Google Analytics may use the IP address received with Analytics traffic to derive approximate geographic information, such as country, region, or city. Google states that Google Analytics does not log or store individual IP addresses.

SnickCam does not send the following values as Analytics event names or parameters:

  • Names
  • Email addresses
  • Telephone numbers
  • Account IDs, player IDs, team IDs, club IDs, or match IDs
  • Cricket scores
  • Cricket records
  • Search text
  • Advertising IDs
  • User-entered content
  • Authentication tokens
  • Precise location
  • Photographs
  • Raw service responses or raw error messages

The initial approved Analytics funnels are registration, team creation, match creation, and account/fill-in player membership addition.

We use optional Analytics only to:

  • Understand navigation and feature usage
  • Identify where users abandon important flows
  • Identify confusing or difficult product areas
  • Measure feature adoption
  • Improve reliability and user experience

Analytics can be changed under Profile → Privacy & analytics. We do not treat optional Analytics as a legitimate interest or as strictly necessary for the Service.

SnickCam does not display advertisements or use Analytics information for advertising, remarketing, or cross-app tracking. SnickCam does not use advertising identifiers for these purposes. If this changes, this Policy and any required consent controls will be updated before the change takes effect.

6. Crash Reporting

Firebase Crashlytics runs on Android and iOS release builds for narrowly limited technical-fault diagnosis. It is separate from optional Firebase Analytics and does not depend on Analytics consent. Crashlytics is enabled unless the user turns off "Share crash reports" under Profile → Privacy & analytics.

The intended device-storage and access purpose is preventing or detecting technical faults. Crashlytics is not used for advertising, behavioural analytics, user profiling, eligibility decisions, or measuring cricket performance. The legal basis is legitimate interests under Article 6(1)(f) UK GDPR and, where applicable, EU GDPR. Google acts as a processor under the applicable Firebase terms.

Crashlytics may process:

  • Crash stack traces and exception information
  • Relevant application state at the time of a crash
  • App version and build information
  • Device model, operating-system version, and technical device information
  • Crash time and session information
  • Crashlytics installation UUID
  • Firebase installation ID
  • Custom diagnostic fields limited to app environment, build mode, and platform

The only app-defined diagnostic fields are app environment, build mode, and platform. SnickCam does not intentionally attach account IDs, names, email addresses, advertising IDs, cricket records, service-request contents, authentication tokens, or user-entered information to Crashlytics reports. Crashlytics data is not fully anonymous because it uses pseudonymous installation identifiers.

Crashlytics processing is limited to narrowly necessary fault diagnosis and is kept separate from advertising. It is not used for behavioural analytics, user profiling, eligibility decisions, or measuring cricket performance.

Our legitimate interest is preventing or detecting technical faults and maintaining a secure, reliable, and stable Service.

Crashlytics is enabled unless you turn off "Share crash reports" under Profile → Privacy & analytics. Turning it off disables future crash-report collection on that device and requests deletion of unsent cached reports. Opting out cannot retroactively delete reports already received by Google.

You may object to processing based on legitimate interests by contacting support@cricketclubbuilder.com.

Google's documented Crashlytics retention period is 90 days before removal from live and backup systems begins.

7. Notifications

SnickCam Scorer uses Firebase Cloud Messaging to deliver app notifications and match alerts when notifications are enabled or configured.

Firebase Cloud Messaging may process:

  • Firebase Installation ID
  • Notification or device token
  • Platform type, such as iOS or Android
  • Notification permission and preference state

Notification permission and notification preferences are separate from optional Analytics consent. You can change notification permissions in your device settings and, where available, change notification preferences in the app.

8. Purposes and Legal Bases

Where applicable law requires a legal basis, we process personal data for the following purposes and legal bases:

  • Performance of a contract: to create and manage accounts, authenticate users, provide profile, team, player, match, scoring, overlay, tutorial, support, and account deletion features, and sync scoring data created while offline
  • Consent: to provide optional Firebase Analytics where a user explicitly allows it, and to use optional device permissions where consent is required
  • Legal obligations: to comply with applicable law, lawful requests, and enforcement requirements
  • Legitimate interests: to operate, secure, support, debug, and improve the Service, prevent misuse, maintain service reliability, protect users and the Service, and process Crashlytics diagnostic information for application reliability and fault diagnosis, except where consent is required

Optional Firebase Analytics is based on consent only. Notification permission, Analytics consent, and the Crashlytics diagnostic preference are independent controls.

9. Children and Teenagers

SnickCam Scorer is not designed specifically for children. The declared target audience includes users aged 13-15, users aged 16-17, and adults.

Users aged 13-15 may use the app. No date of birth is collected for Analytics, and no account identity is attached to Analytics.

The Analytics explanation is written in plain language. No date of birth is collected for Analytics, no account identity is attached, and advertising and cross-app tracking remain disabled.

If a parent, guardian, club, school, or organizer adds information about a child or teenager, they are responsible for making sure they have the rights, permissions, and notices required by applicable law and their organization's rules.

10. Service Providers and Recipients

We may share personal data:

  • With service providers that help us operate, secure, support, and deliver the Service
  • With Google LLC and Firebase services, including Google Analytics for Firebase, Firebase Crashlytics, and Firebase Cloud Messaging
  • With authentication providers such as Google or Apple when you choose those sign-in methods
  • With ipwho.is, which provides the optional country-prefill lookup described above
  • With streaming, media, or browser-source tools when you use external links or overlays
  • With other users or viewers where sharing is part of the feature you use
  • If required by law, legal process, regulation, or to protect rights, safety, and security
  • In connection with a merger, acquisition, financing, reorganization, or sale of assets

The Service may link to or embed third-party services, including Google Sign-In, Sign in with Apple, YouTube content and thumbnails, external stream or media links, app stores, browser-source tools, and mail applications opened from support flows. Your use of those services is also governed by their own terms and privacy policies.

We do not sell personal data.

11. YouTube API Data

SnickCam: Cricket Camera uses YouTube API Services and requests the Google OAuth scope `https://www.googleapis.com/auth/youtube.force-ssl` when you choose YouTube streaming. This section describes exactly how SnickCam handles the information received through that authorization.

11.1 Data accessed

With your authorization, SnickCam may access:

  • The Google account email used to authorize the connection
  • YouTube broadcast IDs, stream IDs, titles, status, privacy settings, and watch URLs
  • YouTube stream connection details required to send the camera feed, including the ingest address and stream key
  • A short-lived OAuth access token used to make authorized YouTube requests

SnickCam does not receive or store your Google password or a Google refresh token.

11.2 How the data is used

SnickCam uses YouTube data only to:

  • List your upcoming and active broadcasts
  • Let you select or create a broadcast
  • Apply your selected Public, Unlisted, or Private visibility
  • Start the selected broadcast when the camera signal is ready
  • End the broadcast when you stop streaming
  • Save the selected YouTube watch link to the relevant match

You can select an existing YouTube broadcast or create a new broadcast through SnickCam.

The Camera app sends the camera feed directly to YouTube using the connection details required for the selected stream.

11.3 User control

  • YouTube access is requested only after you select YouTube streaming.
  • You must explicitly authorize access in Google's consent flow.
  • You can disconnect YouTube from the Camera app.
  • You can revoke SnickCam's access through your Google Account permissions.
  • You can request deletion of SnickCam-stored YouTube data by contacting support@cricketclubbuilder.com or using the account-deletion process.

11.4 Storage and retention

The short-lived OAuth access token and YouTube broadcast and stream details are held temporarily in the Camera app's memory during the active authorization or streaming session. They are not written to SnickCam's persistent account records or stored by SnickCam. SnickCam does not store a YouTube refresh token.

The selected watch URL, title, provider, and related display settings are sent to SnickCam as match media information and retained under the match-history rules in Section 13. Other YouTube metadata is used only for the active session and is cleared when the session ends or YouTube is disconnected. SnickCam does not retain the stream key, ingest details, OAuth token, or camera feed after the active session.

When you disconnect YouTube, revoke access, delete your SnickCam account, or make a verified deletion request, SnickCam clears the active YouTube session and deletes YouTube metadata and credentials that it controls. Because SnickCam does not persist YouTube OAuth tokens or refresh tokens, there is no SnickCam-stored token to retain or delete. YouTube may retain broadcasts, recordings, and other content under Google's own policies; disconnecting SnickCam does not delete that YouTube-hosted content.

11.5 Sharing

YouTube requests and the live camera feed are sent directly from the Camera app to Google and YouTube. SnickCam receives the selected watch URL and related match media information so it can display the stream with the relevant match. OAuth tokens, refresh tokens, stream keys, and ingest details are not sent to SnickCam.

Google LLC processes YouTube API data as the YouTube service provider. Google/Firebase services process the analytics, crash-reporting, and notification data described elsewhere in this Policy. ipwho.is processes only the optional country suggestion described in Section 4. SnickCam does not sell YouTube data, use it for advertising, use it to train AI models, or share it with unrelated third parties.

11.6 Security

  • YouTube and SnickCam requests use HTTPS/TLS. The camera feed uses the secure streaming connection provided for the selected YouTube stream.
  • Active authorization data is protected by the device's security controls. SnickCam applies access controls to match media information stored for the Service.
  • OAuth access tokens, refresh tokens, and stream keys are not placed in logs, analytics, URLs, crash reports, or error messages shown to you.

11.7 Required third-party terms and policies

12. International Data Transfers

Your personal data may be processed in countries other than the one where you live, including countries where our service providers operate.

Google Analytics for Firebase, Firebase Crashlytics, and Firebase Cloud Messaging are provided by Google LLC. Google may process data in different countries. Google describes privacy and data-processing information for Firebase and partner services at:

  • https://firebase.google.com/support/privacy
  • https://policies.google.com/privacy
  • https://policies.google.com/technologies/partner-sites

Where required, we rely on appropriate safeguards for international transfers, such as contractual protections used by our service providers, including standard contractual clauses where applicable. These safeguards are intended to protect personal data during transfer, but they do not mean that data will only be processed in the country where you live.

13. Retention

We retain personal data for as long as reasonably necessary for the purposes described in this Policy, including to provide the Service, maintain security, resolve disputes, enforce agreements, and comply with legal obligations.

Retention may vary by data type:

  • Account and profile data may be retained while your account is active
  • Local offline data may remain on your device until synced, deleted, or the app is removed
  • Match, scorecard, and related historical records may be retained even if your account is deleted, especially where those records are part of match history, team history, or shared competition data
  • Notification tokens may be removed when you disable notifications, sign out, uninstall, or when tokens expire or rotate
  • Crashlytics crash information and associated identifiers are retained by Google for 90 days before removal from live and backup systems begins, according to Google's Crashlytics documentation
  • Analytics consent records remain stored locally on your device until they are changed, reset, or removed with the app
  • The local Analytics consent status, policy version, and timestamp remain on your device until changed, reset, or removed with the app
  • The local Crashlytics enabled or disabled preference and update timestamp remain on your device until changed, reset, or removed with the app

Google Analytics user-level and event-level data retention is configured to 2 months. "Reset user data on new activity" is disabled.

Standard aggregated Google Analytics reports may not be governed by the same user-level and event-level retention setting.

14. Consent Withdrawal and Controls

You can withdraw Analytics consent independently in SnickCam Scorer under Profile → Privacy & analytics. Withdrawal stops future Analytics collection, denies Analytics storage, clears any Firebase Analytics user ID, and resets local Analytics data where supported.

You can independently turn "Share crash reports" off from the same screen. Crash opt-out stops future Crashlytics collection on that device and requests deletion of unsent cached reports. Choices are device-local and should be repeated on other devices where you use SnickCam Scorer.

Withdrawal does not affect processing that occurred lawfully before withdrawal and does not automatically delete historical information already processed in Google Analytics. Historical aggregated reporting may remain and may not be attributable to an identifiable SnickCam account because SnickCam does not send account User-IDs to Analytics.

15. Data-Subject Rights

Depending on where you live, you may have rights to:

  • Access personal data
  • Correct inaccurate data
  • Delete personal data
  • Object to certain processing
  • Restrict certain processing
  • Withdraw consent where processing is based on consent
  • Receive a portable copy of certain data
  • Lodge a complaint with a regulator

You can also:

  • Edit profile information in the app
  • Control notification permissions in the app or device settings
  • Change optional Analytics consent under Profile → Privacy & analytics
  • Turn technical crash reporting on or off under Profile → Privacy & analytics
  • Use the in-app account deletion flow or the account deletion page where available

To exercise rights or request help, contact support@cricketclubbuilder.com.

16. Account and Data Deletion

The Service includes an account deletion workflow:

  • Deletion is normally scheduled after a 30-day grace period, and you may cancel it before it becomes final
  • The Service may check blockers, warnings, and related impacts before deletion proceeds
  • Your personal data is intended to be removed through that deletion flow
  • Matches, scorecards, and certain historical cricket records may remain after deletion

If deletion cannot proceed because of unresolved blockers, historical dependencies, or technical issues, the Service may delay, block, or retry the request.

You can also request account deletion through the SnickCam account deletion page if you cannot access the in-app flow.

17. Security

We use administrative, technical, and organizational measures intended to protect personal data. Examples reflected in the app include protected credential storage on the device, authenticated access controls, controlled account and notification flows, and local storage for offline scoring.

No method of transmission, storage, or security control is completely secure, and we cannot guarantee absolute security.

18. Policy Changes and Effective Date

We may update this Privacy Policy from time to time. When we do, we will update the version number and effective date above. Material changes may also be communicated through the Service or other appropriate channels.

This version is effective from 1 September 2026.

19. Privacy Contact and Supervisory-Authority Complaints

If you have questions, requests, or complaints about this Privacy Policy or our data practices, contact:

  • Kasun Nehinnage Don
  • support@cricketclubbuilder.com

If you are in the United Kingdom, you may have the right to complain to the Information Commissioner's Office. If you are in the European Economic Area, you may have the right to complain to your local data protection authority.