CricNode Privacy Policy
Effective Date: June 14, 2026
App Name: CricNode
Package ID: com.cricnode.app
Company: CricNode (cricnode.com)
Contact: cricnode.support@gmail.com
1. Introduction
CricNode ("we," "our," or "us") is a video recording and live streaming app designed for cricket players, coaches, clubs, and match organizers. This Privacy Policy explains what information is collected, stored, used, and shared when you use the CricNode Android application.
CricNode can be used in a local Recorder mode for on-device recording. Account, subscription, live streaming, league, and YouTube-related features use Firebase, Google, YouTube, Google Play Billing, and CricNode server APIs as described below.
By using CricNode, you agree to the practices described in this Privacy Policy. If you do not agree, please discontinue use of the app.
2. Information We Collect or Process
2.1 Account and Sign-In Information
If you sign in to CricNode with Google, we use Firebase Authentication and CricNode account APIs to process:
- Your Google account email address, display name, profile photo URL, and Firebase user identifier
- Firebase authentication tokens used to prove your signed-in status to CricNode servers
- Your CricNode plan, subscription entitlement, league or club affiliations, streamer approval status, and account settings
- Recent processing job metadata if cloud or account-based processing features are enabled for your account
CricNode does not receive your Google password, and CricNode cannot delete or manage your Google account. Deletion requests apply only to CricNode sign-in data and CricNode-associated server data.
You may also use the Recorder mode without signing in. In that mode, your local recordings and local app settings remain on your device unless you choose to share or stream content.
2.2 Streaming Credentials and YouTube Data
If you connect streaming services, CricNode may process:
- YouTube OAuth tokens: Used to create, manage, and end YouTube live broadcasts that you request from the app. Tokens are stored locally using encrypted storage. If you use account-based YouTube connection features, tokens and YouTube channel metadata may also be sent to CricNode servers so those features can work.
- YouTube channel metadata: Channel ID, channel name, thumbnail URL, and broadcast identifiers for streams you create or select.
- Custom RTMP settings: Server URLs and stream keys you enter for custom RTMP destinations. These are stored locally in encrypted storage and are used only to connect to the streaming destination you configure.
- CricNode stream keys: If CricNode server streaming is enabled for your account, the app may request and store a CricNode stream key issued by CricNode servers.
2.3 Recordings, Media, and App Settings
- Recorded video and audio: Recordings are saved on your device, typically in
Movies/CricNode/or the app's private recording folder. In the current commercial build, cloud upload is hidden and disabled by default. - Scorecard and overlay data: If you use scorecard overlays, the app may request match, league, fixture, and scoreboard data from selected third-party providers such as CricClubs, CricHeroes, DCL, Play-Cricket, or PlayHQ.
- Local preferences: Camera selection, resolution, bitrate, language, overlay positions, streaming preferences, and similar settings are stored locally on your device.
If a future CricNode release enables cloud upload or cloud processing, recordings and match metadata will only be uploaded when that feature is available and you choose to use it. This Privacy Policy will be updated before such functionality is made user-facing.
2.4 Subscription and Billing Data
Streamer subscriptions are processed through Google Play Billing. Google handles payment card details and payment processing. CricNode does not collect or store your payment card details.
The app may store local subscription entitlement state, such as whether Google Play reports an active Streamer subscription, so paid features remain available after purchase.
2.5 Device and Technical Data
CricNode does not use advertising SDKs or analytics SDKs. The app may process limited technical data needed for app functionality, including:
- Network connection state for streaming and server requests
- Android notification state for recording, processing, streaming, and upload progress notifications
- Firebase Cloud Messaging registration data if push notification features are enabled
- Local system logs generated by Android while the app is running; CricNode does not upload diagnostic log files in the current commercial build
2.6 Information We Do Not Collect
CricNode does not:
- Collect personal data for advertising purposes
- Use advertising SDKs or behavioral analytics SDKs
- Sell, rent, or trade your personal information
- Upload your local recordings to CricNode servers in the current commercial build unless a future upload feature is enabled and you choose to use it
- Collect precise location, contacts, SMS, call logs, or advertising identifiers
3. How We Use Information
We use information only to provide, secure, and support CricNode features:
| Purpose | Data Involved |
|---|---|
| Authenticate your CricNode account | Firebase Auth email, display name, user ID, and ID token |
| Maintain your plan and feature access | CricNode plan, Google Play subscription entitlement, league status |
| Record and save video locally | Camera, microphone, and video data written to device storage |
| Stream to YouTube or custom RTMP destinations | OAuth tokens, stream keys, server URLs, broadcast metadata |
| Fetch scorecard overlays | Match, league, club, fixture, and scoreboard identifiers |
| Manage YouTube thumbnails or broadcasts | YouTube channel and broadcast metadata you choose to use |
| Process subscriptions | Google Play Billing purchase and entitlement state |
| Provide notifications | Recording, processing, streaming, or upload status notifications |
We do not use your information for profiling, targeted advertising, or unrelated marketing.
4. Data Security
CricNode uses the following safeguards:
- Encrypted local storage: Stream keys and OAuth tokens are stored using Android encrypted preferences where supported, with keys managed by the Android Keystore system.
- HTTPS: CricNode account and server APIs use HTTPS.
- Trusted server validation: Before sending authentication or OAuth tokens to a CricNode server endpoint, the app validates that the configured server is a trusted CricNode domain or local development address.
- Google Play Billing: Payment information is handled by Google Play, not by CricNode.
- No commercial diagnostic log upload: Diagnostic log file sharing has been disabled in the current commercial build.
No method of electronic storage or transmission is 100% secure. You should protect your device with a screen lock and keep Android and Google Play services up to date.
5. Permissions
CricNode requests Android permissions only for app functionality:
| Permission | Purpose |
|---|---|
CAMERA | Record video from the device camera |
RECORD_AUDIO | Record match audio and stream audio |
INTERNET and ACCESS_NETWORK_STATE | Sign in, fetch scoreboards, use YouTube APIs, stream video, and check network state |
android.hardware.usb.host | Connect to external UVC/USB cameras |
WAKE_LOCK and battery optimization access | Keep recording or streaming stable during long sessions |
ACCESS_WIFI_STATE and CHANGE_WIFI_STATE | Maintain network reliability for streaming where supported |
READ_MEDIA_VIDEO, READ_MEDIA_IMAGES, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE | Read, save, and manage videos/images according to Android version requirements |
POST_NOTIFICATIONS | Show recording, streaming, processing, and upload status notifications |
BLUETOOTH and BLUETOOTH_CONNECT | Detect and use Bluetooth audio devices |
SCHEDULE_EXACT_ALARM | Support scheduled recording starts |
| Foreground service permissions | Keep camera, microphone, media, connected device, and data-sync work running visibly while active |
Permissions are not used for advertising or behavioral tracking.
6. Third-Party Services
CricNode integrates with the following services:
6.1 Firebase Authentication and Firebase Cloud Messaging
- Used for Google sign-in-backed CricNode accounts and optional notification support.
- Firebase privacy information: https://firebase.google.com/support/privacy
6.2 Google Sign-In, YouTube APIs, and Google OAuth
- Used to authenticate your Google account, select YouTube channels, create or manage YouTube broadcasts, and revoke tokens when you sign out.
- Google Privacy Policy: https://policies.google.com/privacy
6.3 Google Play Billing
- Used for the CricNode Streamer subscription.
- Google Play privacy information: https://policies.google.com/privacy
6.4 CricNode Servers
- Used for account plan lookup, subscription/tier synchronization, league or club account features, stream key issuance, thumbnail settings, and account-based processing features.
- CricNode servers receive Firebase ID tokens for authenticated account requests.
6.5 Streaming and Scorecard Providers
- If you choose to stream or display overlays, CricNode communicates with the providers you select, such as YouTube, custom RTMP endpoints, CricClubs, CricHeroes, DCL, Play-Cricket, or PlayHQ.
- Your use of those providers is governed by their own terms and privacy policies.
7. Data Retention
- Local recordings and settings: Remain on your device until you delete them or clear app data.
- Local OAuth tokens and stream keys: Remain on your device until you disconnect the service, reset login, clear app data, or uninstall the app.
- CricNode account data: Account profile, plan, league, stream, thumbnail, and processing metadata are retained while your account remains active, unless deletion is requested and no legal or security reason requires limited retention.
- YouTube server-side connection data: If you connect YouTube account features that send tokens to CricNode servers, those tokens are retained until you disconnect YouTube or request account deletion.
- Google Play billing data: Retained by Google according to Google's policies. CricNode does not store payment card details.
8. Account and Data Deletion
If you use CricNode without an account, you can delete local data directly from your device by deleting recordings, clearing app data, or uninstalling the app.
If you signed in to CricNode with Google, you can request deletion or unlinking of CricNode sign-in data and associated CricNode server data from inside the app on the Account screen, or by emailing:
- cricnode.support@gmail.com
Use the subject line CricNode Account Deletion Request and include the Google account email address associated with your CricNode sign-in. We may need to verify account ownership before deleting or unlinking server-side CricNode data.
Deletion requests do not delete your Google account or data held by third-party services such as Google, YouTube, Google Play, or third-party streaming/scorecard providers. You can manage those services through their respective account controls.
We will respond to deletion requests within 30 days unless a shorter period is required by applicable law.
9. Children's Privacy
CricNode is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe a child has provided personal information to CricNode, please contact us at cricnode.support@gmail.com.
10. Your Rights
Depending on your jurisdiction, you may have rights to access, delete, correct, export, restrict, or object to processing of your personal data.
Because most recording data is stored locally, you can manage much of your data directly on your device. For CricNode account data stored on CricNode servers, contact cricnode.support@gmail.com.
11. International Users
CricNode is available globally. If you use CricNode outside the United Kingdom, your account data may be processed in the United Kingdom, the United States, or other locations where CricNode, Firebase, Google, YouTube, Google Play, or selected third-party providers operate.
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. When we do, we will:
- Update the "Effective Date" at the top of this policy
- Post the updated policy at https://cricnode.com/privacy
- Provide notice of material changes through the app or via email when appropriate
Your continued use of CricNode after changes become effective means you accept the updated Privacy Policy.
13. Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or CricNode's data practices, contact us:
- Email: cricnode.support@gmail.com
- Website: https://cricnode.com
*Last updated: June 14, 2026*