I am writing to express my extreme frustration with Google’s handling of my refund requests for a subscription that has been essentially non-functional for 95% of its term.
Subscription facts:
-
I subscribed to an Ultra plan (via Google Play / Google One billing).
-
Total subscription period: until May 9th.
-
Actual usable time: Only 2 days of normal use.
-
Suspended for no valid reason: The service was then suspended for 16 consecutive days.
-
Unblocked 2 days ago – but I still cannot use it because every time I try, the app/server returns the error:
“Our servers are experiencing high traffic right now, please try again in a minute.”
-
This error persists continuously. The service is still unusable.
So out of the entire subscription, I have received zero working service except for the first 2 days. The remaining time is either suspension or a permanent server-side error that Google/developer has not fixed.
What I have done:
- I requested a refund twice.
- Both requests were rejected without any meaningful explanation or human review.
My position:
- I paid for a working service. Google (via its billing system) approved this subscription and continues to process payments – yet the service itself is not delivered.
- A 16-day suspension plus an ongoing fatal server error is not a minor glitch. It is a complete failure of the product.
- Rejecting refund requests under these circumstances, without even a human looking at the case, is unreasonable and arguably violates consumer protection laws (no service = no payment).
My demand:
- Immediately reverse the two rejection decisions and issue a full refund to my original payment method.
- Provide a written explanation from a human agent – not an automated template – justifying how a subscription that is unusable for >18 days does not qualify for a refund.
Google’s automated refund system cannot be allowed to hide behind “policy” when the product itself is broken. I expect a human to review this case immediately.
My refund request IDs: po.....@gmail.com
Subscription end date: May 9th
Current status: Still broken, same server error.