Guarantee and refunds

This English text is a translation. The French version is the binding one.

Google alone decides whether to grant production access. Peerbeta cannot promise that decision. What Peerbeta guarantees is that you do not pay for nothing if the refusal comes from the test itself.

What the guarantee covers

The guarantee does not cover an update test, which is not used to apply for production access, or an order already refunded or whose payment dispute was lost. There is one guarantee per app; a refused claim does not count.

Conditions (Pro and Launch)

1. The test report is delivered.
2. You applied for production access within 7 days after the eligibility date shown on the test page, and not before that date.
3. Google's refusal is about the test: more testing needed, not enough tester participation. A refusal for a breach of Google's rules or a defect of the app is not covered.
4. You attach a screenshot of the refusal message.

How to claim it

From the test page, open the guarantee claim. Attach the screenshot of the refusal (an image under 10 MB) and enter the date of your application. A person on the team reviews the screenshot, the dates and the message, then accepts or refuses the claim with a reason. You are notified by email.

• Relaunch accepted: a new 14-day test starts with priority, with the same setup, the same number of testers and the same required country, at no cost. An extension bought with the order is not carried over.
• Google refuses again after the relaunch (Pro and Launch): send the new refusal from the relaunch test; after review, what is still paid on the order (offer and add-ons) is refunded, less any refund already made.

For Express, you ask for the relaunch from the test page once the test has ended, and a person reviews it the same way. It does not lead to a refund.

Examples

1. Relaunch accepted (Pro). Lina's eligibility date falls on a Tuesday. She applies on Thursday. Google refuses, asking for more testing. She sends the screenshot the same day. The conditions are met: a 14-day relaunch test starts with priority.

2. Refund (Launch). After Marc's relaunch, Google refuses again for the same reason. Marc sends this second refusal from the relaunch test. His order is refunded in full, add-ons included, to his original card.

3. Refused: breach of Google's rules (Pro). Google refuses Sofia's app because its Data safety declaration does not match the data the app collects. The refusal is not about the test: the guarantee does not apply. The report stays useful for her next application, once the declaration is fixed.

4. Refused: application too late (Pro). David applies 12 days after the eligibility date. The 7-day window has passed: the claim is refused.

5. Refused: application too early (Launch). Aïcha applies the day before the eligibility date shown on the test page. Google refuses. The application came before that date: the guarantee does not apply. Always wait for the eligibility date shown on the test page.

6. Relaunch accepted (Express). Tom's test ends with 10 active testers, below the threshold of 12. He requests the relaunch from the test page; once the claim is accepted, a new 14-day test starts with priority.

7. Refused: Express with enough testers. Nora's test ends with 15 active testers. Google then refuses production access. Express covers the number of active testers, not Google's decision: the claim is refused. For a guarantee on Google's refusal, choose Pro or Launch.

Refunds

Refunds, full or partial, are made by Stripe to the original payment method, with their reason. The time it takes to reach your account depends on your bank. If you are a consumer, you can also exercise your right of withdrawal, described in the terms of sale.

For any question: [email protected].