Skip to main content

Requesting Assistance with Project Suspension (Appeal ID: [removed by moderator] ) – Corrective Actions Completed

  • July 19, 2026
  • 1 reply
  • 12 views

mayfield276

Hello Google Cloud Team and Community,

I am writing to request a review of my suspended project (ID: repairbill-erp- [removed by moderator] ), which was flagged for a policy violation (CONSUMER_SUSPENDED).

The Issue: I have identified the root cause of the suspension: an API key was accidentally included in a public GitHub repository during the early development phase of my small business ERP.

Corrective Actions Taken:

  1. Credential Rotation: I have already deleted the compromised keys and generated new, restricted keys with strict domain-level security (repairbill.shop/*).
  2. Repository Scrubbing: The GitHub repository has been thoroughly scrubbed of all historical traces of the leaked keys using git filter-repo and the history has been rewritten.
  3. Infrastructure Security: I have migrated the application to a dedicated VPS and implemented environment variable security to ensure no sensitive data is ever stored in the code again.

Appeal Details:

  • Appeal ID: [removed by moderator]
  • Project Name: repairbill-erp

I am a small business owner (Mayfield Phone Repair) using these tools to manage my shop. This was an honest configuration error, and I have now implemented industry-standard security protocols to ensure it never happens again.

My appeal has been pending for some time, and my business operations are currently affected. Could a team member please assist in verifying my corrective steps and restoring the project?

Thank you for your time and assistance.

1 reply

a_aleinikov
Forum|alt.badge.img+8
  • Bronze 2
  • July 25, 2026

It looks like you’ve already taken the right remediation steps. Unfortunately, the community can’t review or expedite suspension appeals. If your appeal is still pending, I’d recommend replying to the original appeal email (rather than submitting a new appeal) with the details of the key rotation, repository cleanup, and the security improvements you’ve implemented. That helps keep all the relevant information with the existing case for the Trust & Safety team.