Android and iOS
Mobile app security testing, done by hand.
A person tests your app and writes a report you can hand to a partner, a customer or an auditor. One app on one platform, by quote, or included in Premium once a quarter.
By the Bug Circuit security team · Last updated
What we test
- The app file: keys, passwords and settings left inside the build, and the permissions the app asks for.
- Data on the phone: what the app stores on the device, and whether it is protected.
- Sign-in and sessions: how the app handles logins, tokens and signing out.
- Traffic to your backend: whether it is encrypted and checked properly, and what the app sends.
- How the app talks to the phone: links that open the app, and data it shares with other apps.
- Your backend API, only if it is also in scope as an API.
How access works
- Tell us about the app: its name, Android or iOS, the package name or bundle id, and the store link if it is live.
- Show us it is yours. Add our tester account, hello@bugcircuit.com, in TestFlight or Google Play internal testing. Or, if the app is in a store, its developer website must be on a domain you have verified with us. A store listing alone is not enough.
- Sign the Authorization to Test that names the app, and its backend API if that is in scope too.
- Give us the build through a TestFlight or Google Play internal testing invite.
- Add test accounts in the Test access card on your project, never in chat.
What we never do
- Start before the Authorization to Test that names your app is signed.
- Run your app on our production servers. We test on our own test devices.
- Send your build to an outside scanning service.
- Share or publish your build.
- Test your backend unless it is in scope as an API.
- Keep your build more than 30 days after your report, or your test logins more than 7 days.
What the report covers
The same layout as our sample report: an executive summary, the method, every finding with its severity, evidence and the exact fix, and a plan for what to fix first. It also names the app, the platform and the build we tested, so a reader can see exactly what was covered.
Price
By quote, or included in Premium once a quarter.
| Essential | Pro | Premium | |
|---|---|---|---|
| Mobile app assessment | By quote | By quote | 1 a quarter, then by quote |
| What one covers | One app on one platform | One app on one platform | One app on one platform |
| Uses your website audits | No | No | No |
| Written report | Included | Included | Included |
From app to report
- 1
Describe the app
Name, platform, package name or bundle id, in a new project.
- 2
Show it is yours
A TestFlight or Google Play invite, or a store listing on your verified domain.
- 3
Sign
The Authorization to Test that names the app.
- 4
Allowance or quote
Premium uses its quarterly assessment. Otherwise you pay a fixed quote first.
- 5
We test and report
A person tests your app on our own devices. You get the written report.
Frequently asked questions
Do you test Android and iOS?
How do I give you the app?
Can you test an app that is not in a store yet?
Is my app's backend tested?
What happens to my build afterwards?
Does it use my website audits?
Do you retest after we fix the issues?
How long does it take?
Can I add the 24-hour report?
Is the report a compliance certificate?
Keep reading
Start with a free check of your website
Then sign in to start a mobile app project, or ask us for a quote.
Ready for the full manual audit? See pricing