Privacy Policy

Effective date: 17 June 2026 · Last updated: 12 October 2026

This Privacy Policy explains what personal data CricCuts collects, why, how we use and protect it, and the choices and rights you have. It applies to the CricCuts mobile app (package com.criccuts) and this website.

1. Who we are

CricCuts is operated by Gokul Sundar, an individual developer ("CricCuts", "we", "us", "our"). For any privacy question or request, contact us at support@criccuts.com. For the purposes of India's Digital Personal Data Protection Act, 2023 (the "DPDP Act"), we act as the Data Fiduciary for the personal data described here, and the contact above also serves as our grievance/contact point.

2. Our privacy-first approach

CricCuts is built to keep your footage private. All video import, bat-on-ball detection, clip selection, trimming, and export happen locally on your device. Your raw videos and finished reels are stored only in the app's storage on your phone. They are not transmitted to us or to any server as part of normal use.

3. What we collect

(a) On-device content — stays on your device

• Your videos and the data derived from them: imported video files, detected events (audio/motion/ball-contact), generated clips, your keep/drop choices and labels, sessions, and exported highlight reels.
• This content is stored in the app's local database and file storage on your phone. We do not receive it. Deleting the relevant items in-app, clearing the app's storage, or uninstalling the app removes it.
• Voice search: if you tap the microphone in a search box, the app asks for the microphone permission (the first time only) and passes what you say to your phone's own on-device speech recogniser, which turns it into words on the phone. CricCuts uses only those words, to find the screen or answer you asked for. CricCuts never records, stores or uploads audio, and never uses a speech service that sends audio off the phone; where the phone has no on-device recogniser, the app shows no microphone at all. You can turn the microphone permission off for CricCuts in Android's settings at any time; typed search works without it.
• Voice replies when checking picks: if you turn on Voice while the app plays its picks back to you on the Review screen, it listens briefly after each pick so you can say "Keep" or "Remove" instead of tapping. It uses the same on-device speech recogniser as voice search, never listens while the clip's own sound plays, and uses the words only to keep or remove that pick. No audio is recorded, stored or uploaded. The Keep and Remove buttons do the same without the microphone.
• Coach Notes: notes you pin to frames of a video (the text, the tag, any marks you draw, the name you sign them with, and your recent short phrases) are kept on your phone and are never sent to us. If you tap the microphone while writing a note, what you say goes to your phone's own on-device speech recogniser, exactly as for voice search: the words become the note's text, and no audio is recorded, stored or uploaded. Notes leave your phone only when you share them yourself (as a message, a file, a link, subtitles or a video). A notes link carries the notes inside the link, after the "#"; your browser never sends that part to our website, and the page that shows them reads them in your browser and loads no analytics.
• Search history: the last few places you opened from search or the menu are kept on your phone, to show as "Recent". Not what you typed or said, only where you went. It is never sent to us, and "Delete everything on this device" in Settings clears it.
• Your player profile: your role, level, what you play, batting hand, bowling arm and style, and the language you want the Academy in. The questionnaire fills it in (see (c)), and you can change or clear it any time in Settings → Player profile. It is used only on your phone, to put the most relevant Academy videos first; it is never sent to us. "Delete everything on this device" in Settings clears it too.
• Your Academy learning: the lessons you have started and finished and the days you finished them (for your streak), your School or College level, your scores in the practice tests, papers and the LBW game, your training-plan answers, the sessions you tick and the fitness checks you enter, and your study-reminder setting. It is kept on your phone so you can carry on where you left off; it is never sent to us. "Delete everything on this device" in Settings clears it.
• Your age group: the app's first screen asks whether you are under 13, 13 to 17, or 18 or older. Your answer decides what the app may ask you for and send (see (b), (c), (e) and section 10). It is never sent to us. "Delete everything on this device" clears it, and the app then asks again.

(b) Account data

• When you use the app we create an account through Firebase Authentication (a Google service). This generates a unique user identifier (UID). If you sign in with a provider such as Google (offered only if you told the app you are 18 or older), we also receive the basic profile information that provider returns (for example your name, email address, and profile photo).

(c) Onboarding questionnaire and early-access information

• The app shows a one-time questionnaire the first time you open it (you must complete it to continue; you can answer with whatever fits you best). It asks your role, level, what you do and how often you film. It uses the age group you gave on the first screen (see (a)) rather than asking again. The website's early-access form asks similar questions, and asks "Are you 18 or older?"
• If you said you are under 18, the app asks for no contact details and sends nothing — none of your answers leave your device (they only fill the on-device player profile described in (a)). We do this so that we never collect a minor's personal data without a parent or guardian's involvement.
• If you said you are 18 or older, we collect what you provide: name, email address, phone number (optional), a CricHeroes or social profile link (optional), your cricketing details (role, level, gender, disciplines, batting/bowling style), the problems you'd like solved, your city (see (j) — we store the city, state and country and a location rounded to roughly 11 km, never a precise position), and your consent to be contacted. We do not verify the email address. Your answer to the age question itself stays on your device.
• We use this to send you the build, occasional product updates, to find cricket activity near you, and to shape what we build. Website submissions may be stored with a forms provider or with Google Firestore; in-app submissions are stored in Google Firestore.
• iPhone list. If you use the website's "On an iPhone?" form, we store your email address and, only if you pick one, whether you are a player, a parent, a coach, an academy/school/club, or something else, in Google Firestore. We use it to count how many people would use CricCuts on an iPhone and, if an iPhone version is made, to email you once about it — nothing else, and it is not added to any other list. Spam protection works as described in (h).

(d) Content you choose to share

• If you publish or share a reel, any metadata you add (such as player names, a social handle, location, or watermark details) is included with what you share, on the platform you share to.

(e) Diagnostics and usage

• We use Firebase Analytics and Firebase Crashlytics (Google services) to understand how the app is used and to receive crash reports. Usage means things like sign-in and sign-out, which screens are opened and, in the Academy: which lessons, courses, tests and simulators are opened and finished, a test's score as a range (for example 50–74%), which option was picked for each practice-test question, the LBW game's score, the language a lesson is read in, and your one-tap answer to "Was this lesson clear?". It never includes your videos, anything you type, or what you search for: a search that finds nothing is counted with its length and the closest thing the app has, not your words. These may include your Firebase UID, a device/installation identifier, device model and OS version, app version, and technical logs around a crash. We do not use this to identify you personally beyond your account.
• Both are switched off until you have told the app you are 18 or older and continued past the sign-in screen (where the Terms and this policy are linked) — continuing is what turns them on. If you are under 18, they stay off, and the switch in Settings stays off too: a child can't give this consent. You can turn them off again at any time in the app under Settings → Anonymous usage & crash reports; it takes effect immediately. Reports the SDK had already queued before you switched it off may still be sent. The app does not read or collect your Android advertising ID and shows no ads.

(f) Push notifications (optional)

• CricCuts can send optional push notifications with exclusive offers and product updates. They are off by default — you turn them on in Settings → Notifications inside the app, and you can turn them off again at any time. When enabled, we use Firebase Cloud Messaging (a Google service), which generates a device messaging token used solely to deliver these notifications. We do not use it to track you, and turning the option off unsubscribes your device so we stop sending them.

(g) Feedback and supporter messages (optional)

• If you use the app's "Send feedback" form, we store your message and, if you choose to provide one, a reply email address, in Google Firestore. To help us reproduce and fix reported bugs, this also includes your device model, Android version, app version, and whether the app crashed just before you sent the message — never your videos, clips, or footage.
• If you use the "buy me a coffee" supporter recognition form (in the app or on this website), we store your recognition preference (public or anonymous), and — if you choose public recognition — the name/handle and optional thank-you message you provide, in Google Firestore. A name given for public recognition may be shown on a public supporters page.

(h) Business enquiries (optional)

• If you use a register-interest form on this website (for schools, NGOs and community programmes, academies, clubs and venues, or brands), or the app's "Partner with CricCuts" form, we store what you enter — your name, email address, organisation or company and its type, your city, and whatever optional details you choose to give (your role, phone number, website, the rough size of your programme, what you are interested in, your timing, and your message) — in Google Firestore. We use it only to reply to you about your enquiry. These forms ask for no information about any child, and we ask you not to include any.
• Scene proposals. If you use the "Propose a scene" form on our backdrop scenes page, we store your name, email address, your scene idea as you describe it (including any links to pictures and any AI prompt you share), how you'd like to be credited, and, only if you pick one, what best describes you (player, parent, coach, teacher, student, artist, designer or other) in Google Firestore. We use it only to consider your idea, reply to you and, if we build the scene and you asked to be credited, to credit you by the name you chose. We don't download or store your pictures unless you email them to us. Under 18? Please ask a parent or guardian to send it for you.
• Academy reviews and suggestions. If you offer to review the Academy on our reviewers page, send a review or a suggestion from our Academy review page, or use "Suggest a change" in the app, we store your name, email address, what you tell us (your answers, comments, suggested wording and sources, and which lesson or passage they are about), how you'd like to be credited, and any optional details you give (your role, qualification, organisation, phone number, and a Google account email if you'd like the app) in Google Firestore. From the app, a suggestion also carries the app's version and, if you are signed in, your account's user ID. We use it only to check and improve the Academy, to reply to you and, if we use your suggestion and you asked to be credited, to thank you by the name you chose, in the app and on this website. These forms are for adults: the app never sends a suggestion for someone who has told it they are under 18, and instead offers to show the passage to a parent or coach.
• To keep these forms from being flooded with spam we count submissions per connection using a one-way hash of your IP address (never the address itself). The hash cannot be turned back into your address and is kept only in short-lived counters.

(i) Website analytics (optional)

• If — and only if — you press Allow on the small banner on this website, we use Google Analytics 4 to count visits, which pages are read, clicks on the download button and our Instagram/YouTube links, and which enquiry form was submitted (never what you typed into it). Google sets cookies (_ga…) in your browser and receives your IP address and browser details to produce these counts; we have switched off Google signals and ad personalisation, so it is not used for advertising or to follow you across sites.
• If you do nothing or choose No thanks, nothing is loaded and no cookie is set. Browsers that send Do-Not-Track or Global Privacy Control are treated as a "no" and are not asked. The app has its own separate analytics setting (see (e) above).
• You can change your mind at any time: change my analytics choice. Choosing "No thanks" also removes the Google Analytics cookies from this browser.
• Analytics data is kept for up to 14 months, then deleted by Google Analytics automatically.

(j) Requests the app makes to other services

A few features contact a service run by someone else. None of them carries your videos, and each is triggered by something you do. As with any internet request, the service you contact sees your IP address and basic technical details (such as your Android version) — we do not control what those services log; see their own policies.

• City search — OpenStreetMap / Nominatim. When you search for a city in the onboarding questionnaire (or a location on the Export screen) and press search, the text you typed is sent to OpenStreetMap's public Nominatim search service (nominatim.openstreetmap.org, run by the OpenStreetMap Foundation) to suggest places. It is not linked to your account. If you are offline or nothing is found you can type the city yourself. See the OSM Foundation privacy policy. The place you finally pick is stored as described in (c), with the location rounded.
• Academy videos — YouTube, and free coaching websites. The Academy lists coaching videos made by the players, boards and coaches who publish them on YouTube. The app itself shows no YouTube player and loads nothing from YouTube: when you tap a video, it opens in the YouTube app (or your browser), and from then on YouTube's Terms of Service and the Google Privacy Policy apply. Coaching websites open in your browser under their own policies. Your player profile is not passed to either.
• Downloads — GitHub. The optional sample video and the optional on-device speech model (a large one-time download of roughly 0.6 GB, with the size shown before it starts) are fetched from public GitHub Releases. GitHub sees the request and your IP address. After the download, the model runs entirely on your phone. See the GitHub privacy statement.

4. How we use your data

• To provide and operate the app and its on-device features.
• To create and maintain your account and keep you signed in.
• To respond to you and, where you've opted in, send you the build and product updates.
• Where you've opted in, to send you push notifications about exclusive offers and new features.
• To diagnose crashes, fix bugs, improve performance, and prioritise features.
• To keep the service secure and prevent abuse, and to comply with legal obligations.

5. Legal basis (DPDP Act, 2023)

We process your personal data based on your consent (which you give when you create an account, submit the questionnaire, or opt in to updates) and, where permitted, for certain legitimate uses such as security, fraud prevention, and complying with the law. You can withdraw your consent at any time (see Your rights); withdrawing it does not affect processing already carried out.

6. Who we share it with

We do not sell your personal data. We share limited data only with service providers who help us run CricCuts:

We may also disclose data if required by law, to enforce our terms, or to protect the rights, safety, and security of our users or others.

7. International transfers

Our service providers (notably Google) may process and store data on servers located outside your country. Where data is transferred internationally, it is handled under those providers' own safeguards and privacy commitments.

8. How long we keep it

• On-device content: kept on your device until you delete it or uninstall the app. We never hold it.
• Account data: kept while your account exists, then deleted on account deletion (see below).
• Early-access submissions: kept until you ask us to delete them or they are no longer needed.
• iPhone list: kept until we have emailed you about an iPhone version, or until you ask us to remove you.
• Feedback and supporter messages: kept until you ask us to delete them or they are no longer needed for the purpose collected (fixing the reported issue, or maintaining a public supporters page).
• Business enquiries: kept for as long as we are talking to you about them, then until you ask us to delete them.
• Scene proposals: kept while we consider the idea and, if we build it, for as long as we credit you; otherwise until you ask us to delete them. A deletion request removes them.
• Academy reviews and suggestions: a suggestion we use is kept for as long as we credit you; one we don't use is deleted after 12 months. Reviewer sign-ups are kept while you review with us, then until you ask us to delete them. A deletion request removes them, and your name from the credits.
• Website analytics (only if you allowed them): up to 14 months.
• Diagnostics: retained for a limited period per the providers' defaults, then deleted or aggregated into non-identifying form.

9. Your rights

Subject to applicable law (including the DPDP Act), you may:

• Access a summary of the personal data we hold about you and how we process it.
• Correct or update inaccurate or incomplete data.
• Erase your data and delete your account — see our Account & Data Deletion page.
• Withdraw consent or opt out of product emails and push notifications at any time.
• Raise a grievance about how we handle your data.

To exercise any of these, email support@criccuts.com. We aim to respond within 30 days.

10. Children

CricCuts is not directed to children under 13, and we do not knowingly collect their data. If you are a minor (under 18) under the DPDP Act, you should use CricCuts only with the consent and involvement of a parent or legal guardian; a child under 13 should have a parent or guardian help set it up.

The app's first screen asks your age group, and your answer never leaves your phone. If you are under 18:

• the app offers no Google sign-in, so we don't receive your name, email address or photo;
• usage analytics and crash reports stay off;
• the questionnaire asks for no contact details and sends nothing;
• everything else in the app works, on your phone.

We do not track children or show them targeted advertising. If you believe a child has provided us personal data, contact us and we will delete it.

11. Security

We use reasonable technical and organisational measures to protect personal data, and we rely on Google Firebase's infrastructure security for the data it processes. No method of transmission or storage is completely secure, but keeping your footage on-device by design significantly limits exposure.

12. Deleting your account and data

13. Changes to this policy

We may update this Privacy Policy as the app evolves. We'll change the "Last updated" date above and, for material changes, provide a more prominent notice. Continued use after an update means you accept the revised policy.

14. Contact

Questions, requests, or grievances about privacy:
Gokul Sundar — support@criccuts.com