SwiftAppLab logo SwiftAppLab See the offer
Security review · $500 one-time

App & website security review, from the developer who'd fix it

For $500 I review one web app, mobile app, or website for the security mistakes that actually get small products breached — leaked keys, broken logins, users who can read each other's data. You get a written report with severity and fix steps within 5 business days. If you hire me to fix what I find, the $500 comes off the bill.

One-time · credited toward the fix

App & Website Security Review

$500 one app or site

Starts within 2 business days · report within 5

  • One web app, iOS app, Android app, or website — plus the API behind it
  • Source-code review if you share the repo (recommended)
  • Written report: every finding rated high / medium / low, with fix steps
  • 30-minute walkthrough call on the findings
  • Fixed-price quote to fix them, if you want one
  • $500 credited toward that fix within 30 days
Book the review — $500

After checkout you'll get a short scope form and an authorization to sign. Nothing is tested until it's signed. Full refund if I decline the job before starting.

What this is not — read before you buy

Not a penetration test. A pentest is a longer, adversarial engagement by a dedicated security firm. If a customer contract, cyber insurer, or auditor asks for a pentest report, buy a pentest.

Not SOC 2, HIPAA, or PCI compliance. Those need an accredited assessor and process work that isn't code. This review can find the code-level problems an assessor would flag, so you fix them before paying for the assessment.

Not a guarantee. No review finds everything. You get my honest best effort on the scope we agree, in writing.

Who's doing it: me — an app developer who has shipped production code on Fidelity Investments' iOS app and runs four AI products of my own. I'm not a security firm and won't pretend to be one. I'm the engineer who'd look at your app the way an attacker's first afternoon would.

What does a security review check?

These are the areas every review covers. Each one maps to a public standard, so you can check my work against something other than my word.

AreaWhat I look forStandard
Secrets & keysAPI keys, database URLs, and service tokens shipped in the front end, the mobile app bundle, or the git history.OWASP A02, MASVS-STORAGE
Who can see whatCan user A read or change user B's data by editing an ID? Do database rules (Supabase row-level security, Firebase rules) actually restrict anything?OWASP A01 Broken Access Control
Login & sessionsPassword reset flows, session expiry, token storage, sign-in rate limits, and whether "admin" is checked on the server or only hidden in the UI.OWASP A07, MASVS-AUTH
Input handlingSQL and NoSQL injection, cross-site scripting, unsafe file uploads, and server-side request forgery from user-supplied URLs.OWASP A03, A10
Your APIEndpoints that return more fields than the app shows, missing auth on "internal" routes, and webhooks that don't verify their sender.OWASP API Security Top 10
On-device storage (mobile)Tokens or personal data in plain files or UserDefaults/SharedPreferences instead of the Keychain/Keystore; sensitive data in logs.MASVS-STORAGE
LibrariesDependencies with published vulnerabilities, and abandoned packages doing security-sensitive work.OWASP A06
Transport & headersHTTPS everywhere, HSTS, a content security policy, cookie flags, and CORS settings that don't allow any site to call your API.MDN Web Security
Config & error leaksDebug mode on in production, stack traces shown to users, open admin panels, public storage buckets.OWASP A05

What does a finding look like?

Every finding in the report has the same five parts, so you (or whoever fixes it) can act on it without a call. This is a made-up example of the most common one I'd expect in an app built fast:

HighAny signed-in user can read every customer's orders

Where
GET /api/orders/:id and the orders table's database rules.
How I confirmed it
Signed in as test user A, requested an order ID belonging to test user B, got it back in full.
Why it matters
Names, addresses, and order history for every customer are one changed number away.
How to fix
Check that the order's owner matches the signed-in user on the server, and add a row-level rule so the database refuses it even if the check is missed.
Effort
About 2 hours including a test.

How does it work?

  1. Book and pay. $500 through Stripe checkout. You'll land on a short form asking what to review.
  2. Tell me the scope. URLs, App Store / Play Store links or a test build, a staging environment if you have one, and repo access if you're willing (it finds far more).
  3. Sign the authorization. A one-page agreement naming exactly which systems I may test, that you own them, and what I won't do. No testing happens before this.
  4. I review. Non-destructive only: no load testing, no denial-of-service, no touching real customer data beyond what's needed to confirm a finding, no phishing your staff.
  5. You get the report. Within 5 business days of starting, plus a 30-minute call to walk through it.
  6. Fix it yourself, or have me fix it. If you want me to, I quote a fixed price. Hire me within 30 days and the $500 comes off that quote.

Who is this for?

Security review vs. penetration test vs. automated scanner

Automated scanner
Free or cheap tools that check headers, known library versions, and obvious misconfigurations. Useful, and I use them as a starting point — but they can't tell that user A can read user B's data, because they don't know what your app is supposed to do.
This security review
A developer reads your code and uses your app with intent: two test accounts, an intercepting proxy, and a checklist built on OWASP. It finds the logic and access-control bugs scanners miss. Bounded at one app and five business days.
Penetration test
A longer engagement by a dedicated security firm, often with a formal report your auditor or insurer will accept. Buy one when someone requires it, or when the stakes justify it. A review first usually makes the pentest cheaper, because the easy findings are already gone.

Questions people ask before booking

Is this a penetration test?
No. It's a developer's security review: I read your code (if you share it), inspect the app and its traffic, and check it against the common mistakes in the OWASP Top 10 and OWASP MASVS. If a contract, insurer, or auditor asks you for a pentest report, this isn't it.
Will this get me SOC 2, HIPAA, or PCI compliant?
No. Compliance needs an accredited assessor and a lot of process work that isn't code. What this review can do is find the code-level problems an assessor would flag, so you fix them first.
What do I get at the end?
A written report with every finding rated high, medium, or low, where it is, how I confirmed it, and how to fix it. Plus a 30-minute walkthrough call and, if you want it, a fixed quote to fix the findings. The $500 is credited toward that fix if you hire me within 30 days.
How long does it take?
I start within 2 business days of receiving the signed authorization and access. The report lands within 5 business days of starting.
Will you break anything?
Testing is non-destructive: no load testing, no denial-of-service, no deleting or changing real data, no social engineering. I'd rather test a staging copy if you have one. Nothing is tested until you've signed a written authorization naming exactly what's in scope.
My app was built with an AI coding tool. Is that a problem?
It's a common reason people ask for this. AI-generated apps often ship with API keys in the front end, database rules that let any logged-in user read every row, and admin routes with no check on who's calling them. Those are exactly what this review looks for.
What if you can't review my kind of app?
Then I'll say so and refund you in full before starting. I review web apps, iOS and Android apps, and the APIs behind them. I don't review hardware, smart-contract code, or large WordPress plugin stacks.
Is my code kept confidential?
Yes. The agreement covers it: your code and the findings are used only for this review, access is removed when it's done, and nothing about your app is ever published or used as a case study without your written OK.

Related

Know what's wrong before someone else finds it.

$500, one app or site, a written report in 5 business days — credited toward the fix. Or email me what you've got and I'll tell you honestly whether this review fits.

Book the review — $500 nikolai@swiftapplab.com

Last updated November 9, 2026