Skip to content
Quick scan · self-check

Check your app before you ship it.

Ten plain questions about the app you plan to ship. No security background needed: every question shows how to check it, by hand or by asking your AI coding tool. No signup, and your answers never leave this browser.

01 · Your app

Start with the listing.

Optional. Paste a Google Play or App Store link and we read the platform and app ID from the link itself. Nothing is fetched or sent.

02 · Ten questions

Answer what you know.

"I don\'t know" is a fair answer. It goes on your list to check, never counts as safe. Stuck? Open "How do I check this?" under any question.

  1. 01Does your server check who is allowed to see or change each piece of data, every time?

    Backend (OWASP ASVS) Hiding a button in the app is not protection. Anyone can call your backend directly with their own login and ask for other people's data. This is backend security, outside MASVS itself, but it is where many apps leak data.

    How do I check this?

    Check it yourself

    • Supabase: open Table Editor. Every table should show Row Level Security as enabled, with policies that limit rows to the signed-in user. Check Storage policies too, and note that views skip Row Level Security unless they are created with security_invoker.
    • Firebase: open the Firestore, Realtime Database and Storage rules. Rules such as "allow read, write: if true" or rules that only check "request.auth != null" let anyone, or any signed-in user, read everyone's data.
    • Your own API: every endpoint that returns or changes user data should check that the signed-in user owns that data, on the server.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    Review how this app's backend decides who can read and change data. Check database security rules (Supabase Row Level Security policies, Firebase Firestore and Storage rules) and every API endpoint or cloud function. For each table, collection or endpoint, tell me whether a signed-in user could read or change another user's data by calling the backend directly, without using the app's screens. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  2. 02Is your app free of secret keys, such as admin API keys, private keys or service passwords?

    MASVS-STORAGE Everything inside the app can be extracted from the release build. Some keys are meant to be public, such as a Firebase web config or a Stripe publishable key. Secret ones are not.

    How do I check this?

    Check it yourself

    • Search the project for words like secret, private_key, sb_secret_, service_role, sk_live, password and api_key.
    • Check config files that ship with the app, such as .env files bundled into the build or Info.plist entries. Firebase config files like google-services.json are public by design; check what else is in them.
    • A Supabase secret key (sb_secret_..., or the older service_role key) or any key that grants admin access must never be in the app. The publishable key (or the older anon key) is designed to be public.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    List every API key, token, password and private key that ends up inside this mobile app build, including values from .env files, config files and code. Do not print full secret values: show only the variable name, the file and the first few characters. For each one, say which service it belongs to and whether it is designed to be public (for example a Firebase config, a Supabase publishable or anon key, or a Stripe publishable key) or secret (for example a Supabase sb_secret_ or service_role key, a Stripe secret key or an admin token). Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  3. 03Does your app keep login tokens and personal data in the phone's secure storage, and out of plain files and logs?

    MASVS-STORAGE Plain storage and logs can be read from backups, by debugging tools, or on a lost or shared phone.

    How do I check this?

    Check it yourself

    • Look at where the app saves the login token. Secure options use the iOS Keychain and the Android Keystore, for example flutter_secure_storage in Flutter or a Keychain and Keystore library in React Native.
    • Plain options are SharedPreferences, UserDefaults, AsyncStorage, localStorage and normal files. They are fine for settings; for tokens and personal data, secure storage is the safer choice.
    • Search for print, console.log and Log.d calls that output tokens, emails or other personal data.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    Find every place where this app saves data on the device (for example SharedPreferences, UserDefaults, AsyncStorage, localStorage, files or a local database) and every log or print statement. For each one, tell me whether it stores or logs a login token, password, API key or personal data, and whether it uses the iOS Keychain or Android Keystore. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  4. 04Does every connection your app makes use https://, with no http:// exceptions?

    MASVS-NETWORK Plain http:// traffic can be read and changed by anyone on the same Wi-Fi network.

    How do I check this?

    Check it yourself

    • Search the project for "http://". XML namespaces such as http://schemas.android.com and localhost links used during development are harmless; any address the release app actually calls is not.
    • Android: look for usesCleartextTraffic="true" in AndroidManifest.xml or cleartextTrafficPermitted="true" in the network security config.
    • iOS: look for NSAllowsArbitraryLoads, NSAllowsArbitraryLoadsInWebContent or NSExceptionAllowsInsecureHTTPLoads set to true in Info.plist.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    Check whether this app's release build can send any traffic over plain http://. Search code and config for http:// URLs, Android usesCleartextTraffic or cleartextTrafficPermitted settings, and iOS NSAllowsArbitraryLoads or other App Transport Security exceptions. List each one and whether it applies to the release build. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  5. 05Does your app keep the normal certificate checks switched on, with no code that accepts any certificate?

    MASVS-NETWORK Code that accepts every certificate lets an attacker on the same network pretend to be your server and read everything.

    How do I check this?

    Check it yourself

    • Flutter: search for badCertificateCallback returning true.
    • Android: search for a custom TrustManager or HostnameVerifier that accepts everything, and for onReceivedSslError calling proceed().
    • iOS: search for a URLSession delegate that answers every server-trust challenge with a credential. Node-based tools: search for rejectUnauthorized: false. In React Native, a bypass usually sits in the native Android or iOS code. Developer shortcuts like these are easy to leave in by accident.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    Search this project for code that weakens TLS certificate validation, for example a Flutter badCertificateCallback that returns true, an Android TrustManager or HostnameVerifier that accepts everything, a WebView onReceivedSslError that calls proceed(), or rejectUnauthorized: false. List each one with its file and whether it is active in the release build. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  6. 06Is the build you ship a real release build, with debug mode switched off?

    MASVS-RESILIENCE Debug builds are easier to inspect and change, and they can use looser network settings than the build your users should get.

    How do I check this?

    Check it yourself

    • Flutter: build with flutter build appbundle --release or flutter build ipa --release.
    • Expo or React Native: use the build profile you use for store builds (named production by default), not a development client.
    • Android: the release build type should not be debuggable. iOS: archive with the Release configuration.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    Check how this app is built for release. Tell me which build command or profile produces the store build, whether that build is debuggable (Android) or uses a Debug configuration (iOS), and whether any debug-only features, test menus or verbose logging are included in it. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  7. 07When someone logs out, does their session really end, and do logins expire after a while?

    MASVS-AUTH If a stolen token keeps working forever, logging out or changing a password does not protect the account.

    How do I check this?

    Check it yourself

    • Check that logging out deletes the token on the phone and, where your backend supports it, signs the session out on the server too.
    • Check that access tokens expire, and that refresh tokens can be revoked. Supabase's sign-out revokes the session's refresh token on the server; the current access token keeps working until it expires. Firebase's sign-out only clears the device; revoke refresh tokens with the Admin SDK when you need to end sessions, for example after a suspected theft. The current Firebase ID token stays valid for up to an hour unless your backend checks for revocation.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    Explain how this app handles login sessions. Does logging out delete the stored tokens and end the session on the server? Do access tokens expire, and can refresh tokens be revoked, for example after a password change? Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  8. 08Are your deep links and in-app web pages limited to what your app really needs?

    MASVS-PLATFORM Other apps and websites can open your deep links with any data they like. In-app web pages that can call app code are a common way in.

    How do I check this?

    Check it yourself

    • Check that every deep link handler validates its parameters before acting, for example before opening a screen or making a payment.
    • Check WebViews: JavaScript bridges (addJavascriptInterface, postMessage handlers) should only exist where needed and only for your own pages.
    • Android: components (activities, services, receivers and providers) marked android:exported="true" should be ones you intend other apps to use.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    List every deep link, universal link or app link this app handles, every WebView, and every Android component with android:exported="true". For each, tell me what input it accepts, whether that input is validated, and whether a WebView exposes a JavaScript bridge or loads pages that are not ours. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  9. 09Do you know which packages your app uses, and do you update them when security fixes come out?

    MASVS-CODE Most apps are mostly other people's code. A known security hole in one package is a hole in your app.

    How do I check this?

    Check it yourself

    • Check that a lockfile is committed, such as pubspec.lock, package-lock.json, yarn.lock, Podfile.lock or Package.resolved.
    • Run your package manager's check, for example npm audit, or read the security advisories that flutter pub get prints. Turn on automatic alerts such as GitHub Dependabot, which covers npm, pub, Swift Package Manager and Gradle, but not CocoaPods.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    List the third-party packages and SDKs this app ships with, using the lockfile. Point out any that are far out of date, unmaintained, or have known security advisories, and tell me how to check this automatically in the future. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.
  10. 10Does your app only ask for the permissions and data it truly needs, and do your store privacy details say so?

    MASVS-PRIVACY Extra permissions and silent data collection by SDKs are a privacy risk and can get an app rejected by Google Play or the App Store.

    How do I check this?

    Check it yourself

    • Check the merged Android manifest (SDKs add permissions there) and the Info.plist. Remove permissions your app and its SDKs do not use. On iOS, only remove a usage description once no included SDK needs it, or App Store Connect can reject the build.
    • Check which analytics, ads or crash SDKs are included and what they collect.
    • Compare all of this with your Google Play data safety form and your App Store privacy details.

    Ask your AI coding tool

    Paste this into Cursor, Claude Code, Copilot or any AI tool that can see your project.

    List every permission this app requests (AndroidManifest.xml, Info.plist) and every third-party SDK that collects data, such as analytics, ads or crash reporting. For each, tell me what data it collects and whether the app's features actually need it, so I can compare it with the store privacy details. Only answer yes if you checked the actual code and config. If you are not sure, say so and list what you could not check.

0 of 10 answered. Unanswered questions count as unknown.