StoreReady / release assurance

Your app’s last review deserves better than hope.

A clear release report for what Google Play and the App Store can see—privacy, security, policy, and the evidence still missing.

Exact commit provenanceRead-only source accessUnknown is never PASS
MOBILE
RELEASE
EDITION
01
APP STOREREVIEW NOTES
Store
Ready
BY SYRAVA
RELEASE CANDIDATE1.4.0
RELEASE REPORTACTION REQUIRED

Pulse Notes

3 findings need a decision before you submit.

Exported activityBLOCKED
Privacy disclosuresPASS
Store-side proofREQUIRED
source
provenance
GOOGLE PLAY
APP STORE
01Store policyMetadata · permissions · SDK
02PrivacyDisclosures · deletion · data flow
03SecuritySecrets · CVEs · static analysis
04RuntimeNavigation · crashes · access

A short path to a defensible yes

Bring the release.
We bring the receipts.

StoreReady is built for the week when a release is almost done and “almost” is the expensive part.

01

Attach

Connect a read-only GitHub repository or upload a protected ZIP.

SOURCE · REF · SHA
02

Trace

Inspect signals across policy, privacy, security, artifacts, and runtime evidence.

SCANNERS · DECLARATIONS · MANIFESTS
03

Decide

Get one honest release decision, plus the next action for every unresolved signal.

PASS · BLOCKED · PLATFORM REQUIRED

Interactive report · illustrative data

Not another score.
A useful answer.

Select a finding to see the proof, why it matters, and the next action. The sample uses StoreReady’s real report states; it is not a customer scan.

Open your workspace
SPulse Notes1.4.0 · a1b2c3d
RELEASE DECISIONACTION REQUIRED

Two stores. Separate evidence.

One app, two very different review desks.

StoreReady keeps Google Play and App Store evidence distinct—so no check is presented as stronger than it is.

GOOGLE PLAY EVIDENCE

Android release configuration and policy declarations

Inspect target SDK, manifest exposure, permissions, Data Safety evidence, account deletion, signing, metadata, and release artifacts.

AutomatedPlatform requiredHuman evidence
Target SDK Manifest exposure Data Safety mapping Console declarations Account deletion Final review submission

For the way your team ships

A polished workspace for people.
An honest interface for agents.

Connect a repository, upload a ZIP, call the authenticated REST API, or give your coding agent the existing StoreReady MCP tools.

Read-only GitHub ZIP upload REST API MCP
POST /v1/github/audits
Authorization: Bearer pr_live_...
Content-Type: application/json

{
  "repository": "owner/mobile-app",
  "ref": "main",
  "sku": "deep"
}

Private by default

Your source is an input.
Never the product.

Read the privacy model
01

Scoped access

GitHub repository access stays within the installations and repositories you authorize.

02

Temporary source

ZIPs and fetched snapshots are removed after audit completion by default.

03

Honest uncertainty

Missing, unavailable, or store-side evidence never silently becomes PASS.

Pay for depth, not theatre

Start with the release in front of you.

Individual audits are pay-per-app. GitHub and ZIP inputs use the same credits, and eligible Quick or Deep audits can be retested within seven days.

Loading current audit options…

Human Audit requires supplied Human QA evidence or a configured private runner.

Ready when the evidence is

Every blocker named.
Every unknown visible.

RELEASE READYDecision derived from the evidence available to the audit
Audit your release