Is there an active refund guarantee?
Service-delivery terms are under review. No approval guarantee or active money-back offer. Payments remain disabled. The proposal below is for review and is not an active sales promise.
What is the proposed service-delivery remedy?
If TestPogo cannot supply the agreed campaign, the proposed remedy is a customer choice between an agreed replacement or extension and a refund of the campaign fee. The final policy must define how delivery is assessed and when the customer can choose a refund.
The proposed scope of a refund is the amount paid to TestPogo for the affected campaign. It does not include Google fees, development costs or other third-party expenses. Tax handling and processing time remain to be agreed before sales.
What would you need to provide?
Supply a working closed testing build, correct access details and a way for testers to complete the agreed tasks. Tell TestPogo about access changes and address problems that prevent testing. Any effect on timing must be explained and agreed, not hidden in a broad exclusion.
What if Google does not approve production access?
A rejection alone would not prove that the coordination service was not delivered. Review the reason, compare the delivered work with the agreed scope and decide whether more testing or an app fix is needed.
A separate production-access money-back proposal is recorded for owner review. It must define eligibility, response to a rejection, evidence, refund scope and request/processing deadlines before it can be offered. It is not advertised as a guarantee here.
How would a refund be requested?
A verified support channel and request process must be published before payment opens. There is no payment to refund in this preview and no functioning refund submission endpoint.