SubmitCheck product preview
Privacy and data boundary
This preview explains the intended SubmitCheck data boundary. It does not collect app artifacts, App Store Connect credentials, or payment information. Optional public-portal analytics remain off unless you explicitly allow them.
What stays local
IPA and xcarchive files, source code, assets, dSYMs, Apple API private keys, JWTs, Apple Account passwords, reviewer credentials, private notes, screenshots, and raw executable bytes remain outside the hosted SubmitCheck boundary.
What a future hosted report may receive
Only an explicit, minimized, versioned JSON contract after local redaction and user inspection. Planned fields are limited to normalized facts, capability coverage, safe presence or classification signals, collection times, and fingerprints needed for deterministic correlation.
Optional website analytics
Google Analytics loads only after you choose Allow analytics. The preference is stored in this browser and can be withdrawn through Privacy settings in every public footer. Declining does not affect access. Analytics is limited to understanding aggregate public-portal usage and is separate from archive and App Store Connect evidence.
Authentication in this preview
The preview uses Firebase Authentication with Google. Access to the secure workspace is currently restricted to verified Google identities on the exact emonster.com email domain. No Firestore or Cloud Storage product data is used by this front-end preview.
Control and deletion
The planned product includes per-report, per-cycle, and account deletion controls. Retention periods, legal bases, processor details, and a verified support contact must be finalized and reviewed before a public paid launch.