Catch rejections before they happen.
42+ automated rules scan your app for privacy violations, missing configurations, and guideline breaches. Get a compliance score and auto-fix PRs before you submit — not after your app sits in review for three days.
Everything you need. Nothing you don't.
42 automated rules
Privacy manifests, entitlements, Info.plist, permissions, in-app purchases, accessibility, performance. Apple + Google guidelines fully mapped.
AI deep analysis
LLM-powered review reads your codebase in context. Catches subtle violations — undocumented tracking SDKs, dark-pattern subscription flows — that regex rules miss.
Auto-fix pull requests
One-click PRs for fixable issues. Missing privacy manifest? We draft it. Entitlement mismatch? We patch the plist. You review, merge, resubmit.
Go/no-go readiness
A single score and a ranked list of blockers. Know in 90 seconds whether today's submission will clear review — not whether it *might*.
From scan to ship-ready in four steps.
- 01
Connect the repo
One-click GitHub authorization. Stora reads your Xcode project, Info.plist, entitlements, and build settings directly — no uploads.
- 02
Run the scan
Every rule runs against the current commit. Findings are grouped by severity (blockers / warnings / style) and cross-referenced with Apple & Google policy sections.
- 03
Auto-fix what we can
Privacy manifest missing? We generate it. Camera permission undocumented? We draft the NSCameraUsageDescription entry. Each fix lands as a PR you review.
- 04
Resubmit with confidence
Score ≥ 90 = cleared for review. Ship. If a rule changes mid-review cycle, the watcher agent notifies you and offers an update PR.
Rejections aren't random — and they're getting worse.
Apple's rejection rate for new iOS apps sat around 30% in 2019. In 2026 it's closer to 40%, driven by privacy manifest enforcement (shipped in May 2024), required-reason APIs, and tightening guidelines around AI-generated content, subscription dark patterns, and tracking SDKs. Google Play's review algorithm went through a similar tightening during the Epic settlement rollout.
Most of those rejections are preventable. The top five categories — privacy string missing, entitlement mismatch, purchase-outside-iap, misleading metadata, and crash-on-launch — account for ~70% of rejections and every single one of them is a deterministic check a machine can run. Stora runs all of them, plus the long tail.
What's harder is keeping up. Apple silently updates their review guidelines roughly every three weeks. Stora's compliance watcher tracks the official guideline diff and updates the ruleset within 24 hours of a change. If one of your recent submissions now violates a newly-added rule, you'll get a PR in your inbox before you ship the next release.
Who benefits most.
Frequently asked.
- Do you send my source code anywhere?
- No. Compliance scans run inside a Stora-hosted sandbox with read-only access to the repo for the duration of the scan. No code leaves the runtime; logs are redacted; nothing persists past the scan completion.
- How fast does the ruleset update after Apple changes a guideline?
- Within 24 hours of Apple publishing a guideline update. We track the official guideline page via a watcher, diff the changes, and ship ruleset updates through the same delivery path as our app updates.
- Can I skip specific rules?
- Yes. Rules can be muted at the project level with a written justification that's logged in the audit trail. Blocking rules (privacy, entitlements, IAP policy) require a manual admin override.
- What about Google Play?
- Google Play rules are covered from the same scan. The ruleset is policy-tagged so you see iOS, Android, or both as applicable for each finding.
- Does it check my screenshots?
- Screenshot metadata only (resolution, device class, required counts). Visual compliance — dark patterns, misleading promises, unsupported device mockups — is covered by the QA product.
Ready to ship?
Connect your GitHub repo and let agents handle the rest. Your next release, out the door in minutes.