Skip to content
SubmitCheck
ProdottoCome funzionaPrivacyPrezziFAQ
Lingua
🇺🇸English🇯🇵Japanese🇪🇸Spanish🇮🇹Italian
🇺🇸English🇯🇵Japanese🇪🇸Spanish🇮🇹Italian

SubmitCheck product preview

Security model

SubmitCheck is designed around least privilege, local inspection, deterministic rules, and explicit unknown states.

Last updated August 14, 2026
01

Local artifact handling

The planned CLI treats archives as hostile input and protects against path traversal, symlink escapes, decompression bombs, excessive file counts, nested depth, and unbounded memory use.

02

App Store Connect access

The planned collector keeps the .p8 key local, mints short-lived JWTs with scoped GET paths, and independently enforces an audited Apple host, method, endpoint, relationship, and field allowlist. SubmitCheck never requests an Apple Account password.

03

Evidence integrity

Rules are immutable and versioned. The same normalized input and ruleset should produce the same status. Missing evidence becomes Needs Evidence, Manual Review, or Not checked—never Passed.

04

Preview limitations

This interface uses simulated sample data. It does not run a scanner, contact App Store Connect, create reports, export customer data, or grant product entitlements.

Pre-launch legal review required.

Final privacy, security, terms, retention, refund, tax, processor, and support language must be reviewed and configured before paid public availability.

SubmitCheck

Submission readiness with inspectable evidence and an explicit local-first boundary.

Product

CapabilitiesHow it worksPricing

Resources

FAQSecurityData boundary

Legal

PrivacyTerms

© 1997–2026 emonster inc. All rights reserved.