Certari Submission reviewNeed help?
  1. 1Package
  2. 2Your app
  3. 3Confirm

Choose your review.

A reviewer installs your build and exercises it the way App Review would. Apple decides approval; Certari reports likely blockers with evidence. No source code is needed.

Package
What the reviewer checks in Essentials
  • Build installs and launches from TestFlight or the shared build
  • Up to six named workflows exercised for crashes, dead ends and placeholder content
  • Reviewer access, demo account and App Review notes checked for completeness
  • Account creation, sign in and account deletion flows where the app has accounts
  • Permission prompts and purpose strings observed in use
  • Privacy policy link, App Privacy answers and store metadata compared with observed behavior
  • Private report with likely blockers, evidence, guideline references and fix guidance

Before you pay, have ready

  • A demo account with synthetic data, if your app has accounts
  • The store listing text and screenshots you plan to submit
  • Your draft App Review notes, and any previous rejection message

These can follow through the access checklist after payment. The delivery clock starts once payment and complete reviewer access are in place.

Never share your Apple ID password, signing certificates, provisioning profiles, API keys or customer data with Certari. Reviewer access is through TestFlight or a build file over the agreed channel, with test accounts holding synthetic data.

Not included

Fixing or submitting the app, writing store metadata, App Store Connect administration, legal review, security testing and any promise about Apple's decision. One review covers one build.