Check your build before App Review does

    Upload the IPA, APK or AAB you're about to submit. PTKD reads the compiled build (no source code needed) and lists what App Store or Google Play review is likely to reject, each linked to the guideline and the fix. A full security scan runs alongside it.

    What it checks

    CheckStorePredicts
    Permissions used without a purpose string, or with one too vague to passApp StoreITMS-90683
    Required-reason APIs (UserDefaults, file timestamps, disk space…) missing from the privacy manifestApp StoreITMS-91053
    SDKs on Apple's list that ship without their own privacy manifestApp StoreITMS-91061
    Advertising or attribution SDKs without App Tracking TransparencyApp Store5.1.2
    Google or Facebook login without Sign in with AppleApp Store4.8
    References to private Apple APIsApp Store2.5.1
    Stripe, PayPal or Braintree without store billing (a problem for digital goods)Both3.1.1
    Sign-up without in-app account deletionBoth5.1.1(v)
    Capacitor or Cordova apps that load a live website instead of bundled codeBoth4.2
    Target API level below Google Play's yearly requirementGoogle PlayPlay policy
    Restricted permissions: SMS, call log, all-files access, background location, query all packages, exact alarms, package installsGoogle PlayPlay policy

    What you get

    • A review readiness score out of 100, separate from the security score, so a missing Sign in with Apple never looks like a vulnerability.
    • Each finding with the evidence from your build, the guideline it predicts and the fix.
    • Run it from CI on every build, so a rejection is caught in the pull request instead of in Resolution Center.

    What it can't see

    App Review also judges things no file can show: whether the app works for the reviewer, whether your metadata and screenshots match it, whether the business model fits the rules. Use the check to remove the mechanical rejections and the guideline reference for the rest.

    Free for 5 checks a month on one app.