Cricbuzz support: score errors, app feedback and Plus billing

For a score correction

Provide the match URL, innings, delivery or over, displayed value and time zone. Explain whether the issue appears in commentary, scorecard or alert. A screenshot without the match identifier can leave the event ambiguous.

For Android feedback

The reference Play item lists [email protected]. Use that listing to confirm the current channel and include package, app version, system and the exact error. This is a published route, not a measured response-time promise.

For login or a lost contact

Identify the service account and the contact used at registration. A public scorecard usually does not require a paid-plan diagnostic. Never share a password or OTP in a score report or public message.

For a charge without Plus access

Keep receipt, billing channel, account used to buy and product name. Distinguish a renewal from a new purchase. If the issue is a Willow link, retain the separate country and account requirements.

For privacy and account removal

The referenced privacy notice names [email protected] for its grievance and data-request route. Confirm the current notice and describe whether the request concerns consent, download or deletion. Uninstalling the app does not prove server-side records were deleted.

Keep acknowledgement and decision separately

Record the submitted reference, receipt of the message and any final response. A generic acknowledgement does not establish that the score changed, access returned or a refund was approved.

Keep the match and product in view

If the question changes from a score to a device error, a plan charge or a broadcast, switch to that product’s own record. The same name across those screens does not make their conditions interchangeable.

Cricbuzz·Cricbuzz live score·Cricbuzz app·Cricbuzz schedule