No checklist can promise an app is secure, but a few checks catch most real problems in apps built quickly. Work through these before you share the link widely.
1. Run Bolt's security audit
Bolt can audit your project from the publish menu. According to Bolt's announcement, it looks for issues like broken access control, secrets in code and database policies, fixes what it can and flags the rest for you. Bolt's release notes say it's available on paid plans. Read what it flags, especially anything it couldn't fix automatically.
2. Know where your app and data live
Bolt can host your app on a bolt.host address (Bolt hosting docs), and store data in a database Bolt manages or in your own Supabase project (Bolt database docs). Write down which one you use: the checks below differ slightly.
3. Keep secret keys out of the front end
The quickest way to call OpenAI or Stripe is from the page, and that's how keys leak. Keep keys in Bolt's secrets and call those services from server-side code (for example a Supabase Edge Function). Then open your published app, the browser's developer tools → Sources, and search for sk-, sk_live and service_role. Nothing should come up. In a Vite project, anything named VITE_… ends up in the browser (Vite docs).
4. Check what the public database key can read
Your app's browser code talks to the database with a public key. That's fine only if access rules limit what it can read. For Supabase, that means Row Level Security on every table with policies that match each row's owner; see is the Supabase anon key safe?. Test it: as a signed-out visitor and as a second user, try to read data that isn't yours.
5. Review sign-up settings
Email confirmation on, login redirects limited to your own address, and a Site URL that isn't localhost. In a Supabase project these are under Authentication.
6. Check the address users will visit
If you add a custom domain, check that one, not only the bolt.host address. Headers, redirects and certificates can differ between them. Every page should load over HTTPS with security headers; our headers guide lists what to send.
7. Make sure nothing extra is served
Try /.env, /.git/config and a few .map files on your live address. They should all fail to load.
8. Add the pages users expect
If you collect emails or take payments, publish a privacy policy, terms and clear contact and refund details, written for your app rather than copied from a template.
9. Scan the published app
Finally, check it the way a stranger would. The free Securick scan runs 46 tests from your public URL in about a minute, including:
- #2 OpenAI API key exposed Free
- #3 Anthropic API key exposed Free
- #1 Stripe live secret key exposed Free
- #10 Secret values in public env variables Free
- #11 .env file public Free
- #13 JavaScript source maps public Free
- #19 HTTP redirects to HTTPS Free
- #23 Content-Security-Policy present Free
- #29 Not open to every website Free
Pro runs all 130 for $10, one payment; on a domain you verify, Deep tests check what your database answers to the public key:
- #59 Supabase tables not readable with the public key Deep
- #61 Firebase Realtime Database not open to read Deep
- #62 Firestore not open to read Deep
- #96 Data isolation between users Deep
A short version to keep
- Bolt's audit run, flagged items handled.
- No secret keys in the browser.
- Database access rules tested as a stranger and as another user.
- Sign-up settings reviewed.
- HTTPS and headers on the address users visit.
- No .env, .git or source maps served.
- Legal pages written for your app.
- Live app scanned, issues fixed, scanned again.
Questions
Bolt's audit passed. Is my app safe?
It's a good sign. Bolt describes its audit as a first pass, so also check the live app from the outside: keys in the built code, what the public database key can read, and your headers.
Is a bolt.host address fine for launch?
It works. Many people move to a custom domain for trust and branding; if you do, re-check the new address, since headers and redirects can differ.
Does Securick need access to my Bolt project?
No. The free and Pro scans only use your public address. Deep tests need you to verify the domain, and still don't need access to your Bolt account.