App Security Check

How secure is your app?

A quick check for Flutter, web and AI-built apps. Answer yes or no about your own app and get a score, what to fix first, and a prompt your AI coding agent can run on your code.

Pick a level

No signup. Your answers stay in this browser.

All 28 checks

Every question, why it matters and how to fix it, with a Flutter note where Flutter has its own answer.

Quick check10 checks · Any app: web, mobile or AI-built+
  • Critical

    Are private API keys kept out of your app's code?

    Anything shipped to a phone or a browser can be read. That includes .env files bundled as assets and frontend variables like NEXT_PUBLIC_ and VITE_.

    Fix: Call paid or private APIs from your server and give the app short-lived tokens. Rotate any key that has already shipped.

    In Flutter: Values passed with --dart-define are still inside the app. Obfuscation only slows people down.

  • Critical

    Is your database locked with access rules?

    Firebase and Supabase keys are public by design. The rules are the only thing deciding who can read and write your data. Test-mode rules leave it all open.

    Fix: Turn on Row Level Security for every Supabase table, or write Firebase Security Rules that check request.auth. Never ship the Supabase service_role key to the client.

    In Flutter: Same rules apply to firebase_core and supabase_flutter apps. Test them in the emulator before release.

  • Critical

    Does every API endpoint check who is calling and what they can access?

    Hiding a button in the app does not protect the endpoint behind it. Anyone can call your API directly and change an ID in the request.

    Fix: Check the session or token on every route, then check that the user owns the record they ask for. Deny by default.

  • Critical

    Does every request use HTTPS?

    Plain HTTP can be read and changed by anyone on the same network, like public Wi-Fi.

    Fix: Use https:// everywhere, redirect HTTP to HTTPS, and keep cleartext settings out of release builds.

    In Flutter: Check usesCleartextTraffic and network_security_config on Android, and NSAllowsArbitraryLoads on iOS.

  • High

    Are login and expensive endpoints rate-limited?

    Without limits, bots guess passwords, spam OTPs and run up your AI or SMS bill overnight.

    Fix: Limit attempts per user and per IP on login, OTP and AI endpoints, and set a spending cap with every paid API provider.

  • High

    Are the keys that must be public restricted to your app?

    Maps and Firebase keys have to ship in the app. Without restrictions, anyone who copies them can use your quota and your bill.

    Fix: Restrict each key to your website domain, Android package name with SHA-1, or iOS bundle ID, and only to the APIs it needs. Add a budget alert.

  • High

    Is your Git history free of secrets?

    Deleting a file does not remove it from history. Public repos are scanned for keys by bots, often within minutes.

    Fix: Turn on secret scanning and push protection. Rotate any key that was ever committed, even if you deleted it later.

  • High

    Are tokens and personal data kept out of logs and crash reports?

    Logs end up on devices, in dashboards and in crash reports that many people can read.

    Fix: Never log tokens, headers, passwords or personal fields. Scrub data before it goes to Sentry, Crashlytics or any log service.

    In Flutter: print and debugPrint output shows up in device logs. Use a logger that drops verbose output in release.

  • High

    Can users delete their account and their data?

    Privacy laws expect it, and Google Play and the App Store both require in-app account deletion when users can sign up.

    Fix: Add a delete account option in settings, delete or anonymise the data on the server, and say how long any copies are kept.

  • Medium

    Are your packages up to date and checked for known issues?

    Every package runs with your app's permissions. An outdated or abandoned one can carry a known hole straight into your app.

    Fix: Update regularly and scan your lock file with OSV-Scanner, npm audit or GitHub Dependabot.

    In Flutter: Run flutter pub outdated, and check the publisher and recent activity on pub.dev before adding a package.

Mobile app10 checks · Adds storage, sessions, links and store rules+
  • Critical

    Are login tokens stored in the phone's secure storage?

    Plain preferences are simple files. On a rooted phone, or from some backups, anyone can read them.

    Fix: Use the Android Keystore and the iOS Keychain for tokens and keys, not plain preferences.

    In Flutter: Use flutter_secure_storage instead of SharedPreferences.

  • High

    Is sensitive data cached on the phone encrypted?

    Offline caches often hold addresses, phone numbers and orders, and they outlive the session.

    Fix: Encrypt local databases that hold personal data, and keep the key in secure storage, never in code.

    In Flutter: Use SQLCipher (sqflite_sqlcipher or sqlcipher_flutter_libs) or Hive encrypted boxes.

  • High

    Does logout clear tokens, caches and local data?

    Phones get shared, sold and handed over. An app that keeps the data after logout has not logged out.

    Fix: Write one logout routine that deletes stored tokens, local databases and cached files, and revokes the session on the server.

  • High

    Can you end a user's session from your server?

    Phones get lost and stolen. If only the phone can log out, you cannot log out a phone you do not have.

    Fix: Keep sessions or refresh tokens on the server so you can revoke them, and offer a log out of all devices option.

    In Flutter: With Firebase Auth, the Admin SDK's revokeRefreshTokens ends every session for a user.

  • High

    Are certificate checks always on in release builds?

    Code that accepts any certificate lets anyone on the same Wi-Fi read and change your traffic. It is a common copy-paste fix that ships by mistake.

    Fix: Remove any code that trusts all certificates. Fix the server's certificate instead.

    In Flutter: Search for badCertificateCallback that returns true.

  • Medium

    Are your release builds obfuscated?

    Obfuscation makes reverse engineering slower and more expensive. It is a speed bump, not a lock.

    Fix: Turn on code shrinking and obfuscation for release builds, and keep the mapping files for crash reports.

    In Flutter: Build with --obfuscate --split-debug-info=build/symbols and keep the symbols folder.

  • High

    Are deep links verified and treated as untrusted input?

    Anyone can craft a link that opens your app with any parameters they like.

    Fix: Use Android App Links and iOS Universal Links, validate every parameter, and never finish a payment or login straight from a link.

  • Medium

    Are sensitive screens hidden from screenshots and the app switcher?

    OTP, payment and personal data screens end up in screenshots, screen recordings and the recent apps preview.

    Fix: Set FLAG_SECURE on Android for those screens, and cover the content on iOS when the app goes to the background.

  • Medium

    Are sensitive files excluded from Android backups?

    Android Auto Backup can copy app data to the user's cloud and restore it on another device.

    Fix: Set android:allowBackup to false, or exclude sensitive files with dataExtractionRules and fullBackupContent.

  • High

    Do your store privacy forms match what the app really collects?

    Google Play's Data safety form and the App Store privacy labels must cover every SDK too. A wrong form can get an update rejected.

    Fix: List every SDK and what it collects, and update both forms whenever you add one.

Full check8 checks · Adds tokens, attestation, pinning and privacy+
  • Critical

    Are access tokens short-lived and refreshed?

    A stolen token works until it expires. A token that lasts a month gives an attacker a month.

    Fix: Keep access tokens to minutes or an hour, refresh them with a refresh token, and rotate the refresh token on every use.

  • High

    Does your server check that requests come from your real app?

    Scripts and modified copies of your app can call your API directly and skip every check inside the app.

    Fix: Use the Play Integrity API on Android and App Attest on iOS, and verify the result on your server, never in the app.

    In Flutter: Firebase App Check wraps both for Flutter apps.

  • High

    Does your app have a clear rule for sessions that expire while offline?

    Real users stay offline for hours. Without a rule, the app either locks them out mid-task or keeps acting on a session that should be over.

    Fix: Decide what works offline, queue the rest, and re-authenticate before syncing the queue.

  • High

    Do you collect only the data you need, with clear consent?

    India's DPDP Act and GDPR both expect consent for a stated purpose and no more data than that purpose needs.

    Fix: Write down why you need each field, ask for consent in plain words, and delete data when the purpose is over.

  • Medium

    Have you decided about certificate pinning on purpose?

    Pinning blocks attacks that use a rogue certificate, but it breaks the app the day your certificate changes if you did not plan for it.

    Fix: If you pin, pin the public key and ship a backup pin. If you do not, write down why and rely on HTTPS and server checks.

  • Medium

    Have you decided what happens on rooted or jailbroken phones?

    On those phones, secure storage and app checks can be bypassed. Blocking everyone also hurts honest users.

    Fix: Detect it, then limit risky features like payments instead of blocking the whole app.

    In Flutter: freeRASP adds root, jailbreak and tamper detection.

  • Medium

    Do your WebViews only load pages you trust?

    A WebView with JavaScript and a bridge into your app lets a web page call your app's code.

    Fix: Allow only your own domains, keep JavaScript bridges minimal, and never load a URL that came from user input.

  • Medium

    Are debug menus and test endpoints out of production?

    Test URLs, debug menus and verbose logs left in production give attackers a map of your app.

    Fix: Keep debug code behind build flags and test URLs in debug builds only, and check the production build before every release.

    In Flutter: Guard debug code with kDebugMode, and keep test URLs in debug flavors.

Questions people ask

Can you hide an API key inside an app?+

No. Anything shipped to a phone or a browser can be read, including .env files bundled as assets and frontend variables like NEXT_PUBLIC_ and VITE_. In Flutter, values passed with --dart-define are still inside the app, and obfuscation only slows people down. Keep private keys on your server, and restrict the keys that have to be public to your app or domain.

Is it safe that my Firebase or Supabase key is public?+

Yes, those keys are meant to be public. What protects your data is the access rules: Firebase Security Rules, or Row Level Security on every Supabase table. If the rules are in test mode, anyone with the public key can read and write everything. The Supabase service_role key is different and must never reach the client.

What does the AI prompt do?+

It turns your No and Not sure answers into a review task for a coding agent like Claude Code, Cursor or Copilot. The agent checks each item against your actual code, reports pass or fail with the file paths it looked at, and waits for your approval before changing anything.

Where should a Flutter app store login tokens?+

In secure storage. The flutter_secure_storage package uses the Keychain on iOS and Keystore-backed encryption on Android. SharedPreferences is a plain file that can be read on a rooted phone.

Is this a security audit?+

No. It is a self-check that shows you where to look, built on the same areas as the OWASP Mobile Application Security Verification Standard (MASVS) and common web security practice. If your app handles payments, health or identity data, get a proper security review before release.

Made for flutterCon India 2026

Built as the companion to the roundtable “Hardening Flutter Security: Balancing Compliance and Operational Risks” on 21 November in Bengaluru, then opened up for any app.

Built by Zaid Sayyed. Want a second pair of eyes on your app? Tell me about it.