The assessment follows one release from agreed scope to reasoned report. Technical work begins only after written permission.
Select a stage to see what you provide, what happens and what comes back. This is an illustrative process, not a live assessment.
We check whether the release fits the chosen tier. Beta, Indie and Enterprise test groups are agreed here before any build is shared.
Store link, platform and intended release
A written test scope that names the app and selected tier
Four checks establish the boundary and permission for the work.
Join the betaDefine which package and build are in scope.
Show you can request this assessment.
Set the confidentiality terms before the build is shared.
Record the technical work permitted for this release.
One release build and its permission documents go in. A reasoned record comes back.
One Android APK or AAB, or iOS IPA, plus a dependency lockfile and permission documents. Source code is not requested.
Confirmed findings carry evidence, impact and a practical fix. A control that could not be tested gets a reason. Standard includes one retest within 60 days.
