For most teams, uploading a binary to a third party is a bigger perceived risk than a store rejection. Fair. So here is exactly what happens to your build, and exactly who touches our infrastructure.
The life of your build
- Upload: encrypted in transit, straight into an isolated scan environment.
- Scan: the engine reads the binary, runs all checks, and writes findings with evidence.
- Delete: the binary is destroyed the moment the scan finishes. Automatically, every time, not as a setting you have to find.
- Findings: stored encrypted for your plan's retention window, then deleted.
EU vendors, one exception
Our infrastructure and vendors are EU-based. The single exception is Stripe, which processes payments; Stripe never sees your builds or findings. We name the exception because an absolute claim you cannot verify is worth less than an honest list.
- Hosting and scanning: EU infrastructure, EU region only.
- Email and support tooling: EU vendors.
- Analytics: cookieless and EU-hosted. No Google Analytics.
- Payments: Stripe (the exception).
What never happens
- Your builds, code and findings never train AI models, ours or anyone's.
- Nothing is sold, shared or moved outside the EU, Stripe's payment processing excepted.
- Nobody at AppCompliance browses customer findings; internal access is limited and logged.
Verify us
Ask for the current sub-processor list, the DPA, or a summary of our security measures before you upload anything: info@appcompliance.io. A vendor that answers those questions slowly is telling you something; we aim to answer within one business day.