Check it yourselfSearch 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 toolPaste 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. Copy prompt