
Identify what stopped working
Write the last successful action and the first failing one. Was a fixture found? Did the app open? Was a charge taken? Is the problem a particular article or a full-match stream? This determines which evidence is useful.
A generic “app not working” report mixes technical, content and entitlement questions.
For a score correction, name the event
Include competition, full teams, date, innings, ball or player and the field in dispute. Compare the official event record where available. Preserve whether Cricbuzz showed the result as provisional or final.
If a notification is late but the scorecard is current, record both times instead of treating the notification as the latest score.
For Android feedback, keep the platform context
Use the feedback or publisher contact linked by the identified app. Retain installed version, system version and exact error. No response time, customer-care telephone number or individual case resolution has been verified by D1.
For language problems, state whether the missing element is text, audio, captions or menus.
For a payment, identify merchant and product
A Plus receipt and a Willow receipt concern different products. Match the charged account and billing channel before asking about activation or renewal. Retain transaction date, amount and reference privately.
If only one programme is absent, include the event and territory; a rights limitation can differ from an unactivated subscription.
Deleting software does not settle a privacy request
Uninstalling removes local software. Cancelling concerns future billing. Deleting a remote account or data needs the provider’s privacy process and may involve retention obligations. State the result you want and keep its acknowledgement.
D1’s editorial contact can correct a page here. It cannot authenticate a Cricbuzz account or resolve a charge on its behalf.
A compact report template
Use a short chronology with one unresolved question. For example: the named match opened on the web at a stated time, the Android app still showed the previous innings, and the issue persisted after a normal refresh. Add the relevant versions and a redacted screenshot.
Avoid publishing passwords, OTPs or full payment details. A clear record helps the correct provider inspect the issue without exposing account access.
READ THE SOURCE / CHECK THE DATE
Documents & references
Dates below belong to the historical references. The writing date does not represent a new account or file test.
- Google Play India — Cricbuzz main Android app2026-11-02 · play.google.com
- Cricbuzz — Terms of Service and paid-service provisions2026-11-02 · www.cricbuzz.com
- Cricbuzz — Privacy Notice, dated 1 April 20252026-11-02 · www.cricbuzz.com
- Cricbuzz — public login options and terms acknowledgements2026-11-02 · m.cricbuzz.com
- Cricbuzz — Willow linking FAQ and USA/Canada condition2026-11-02 · m.cricbuzz.com
- Google Play India — older language package, returned 4042026-11-02 · play.google.com
More on Cricbuzz
D1 is an independent information publisher. Product providers handle their own accounts, files and transactions. How we write →