Card payments are charged in full upfront via Stripe. If you cancel for any reason before our testers begin opting in — or if we fail to get your testers opted in within 48 hours of receiving a working opt-in link — you get a full refund. (If you arranged 50/50 via PayPal instead, this applies to your deposit.)

Same protections either way — payment method doesn't change your rights. Cancel before testers start: full refund. Google rejects after a completed run: free re-run first, then a full refund if the re-run is also rejected. Cancel mid-test: pro-rata refund for unused days. See the sections below for exact numbers.

Applies when you completed the full 14-day run with us, used our questionnaire guide for your answers, and acted on the bugs we reported (see the section below). Send us Google's rejection message within 14 days and we'll run the test again at no extra cost — most rejections are fixable, and this usually gets you through. If that re-run is also rejected for reasons covered by this guarantee, you get a full 100% refund at that point. No back-and-forth — one message with the rejection, and we move to the next step.

Once testers are opted in and active, they're being paid for their time. If you cancel during the 14 days, we refund the unused portion pro-rata (remaining days ÷ 14), calculated on the full plan price. Example: cancel after day 7 on the $29 plan → $14.50 back.

Rejections unrelated to testing: content-policy violations, misleading store listing or metadata, malware/security flags, developer-verification problems, or an app build that crashes on install and isn't fixed after we report it. We'll tell you before starting if we see an obvious risk in one of these areas — we'd rather lose the sale than run a test that can't pass.

Our job is to run the test and report what testers find — clearly and on time, every time. What you do with that report is your call. If our feedback report flagged real, reproducible bugs and you applied for production access without addressing them, a rejection tied to those same issues isn't covered by the guarantee. We're not the judge of your app's quality — Google is — but we also can't guarantee a result that depends on fixes only you can make. This is exactly why we push you to ship at least one update during the 14 days: it's your chance to act on what we find, before it costs you the guarantee.

Back to the same method you paid with — PayPal or the card you used — within 5 business days of approval. No store credit, no "contact support to escalate" loops — one message to the same person who ran your test.

No — tester payment and your refund are two separate things. Testers are paid based on completing their assigned days, not on whether Google approves your production access. If Google rejects your app and you choose a refund, the testers who did the work still get paid for it — that's on us, not deducted from your refund.