Skip to main content
LaunchGateAUDIT TODAY. LAUNCH TOMORROW.
Run a free launch check

Launch readiness self-check

Launch readiness self-check.

Twenty questions in five short steps. You get a preliminary profile of where your launch risk sits, the areas worth reviewing first, and the LaunchGate package that fits what you told us.

  • Worked out in your browser
  • Nothing saved or sent unless you email it

The profile is worked out in your browser with JavaScript, which seems to be turned off. You can still use the questions below as a checklist, or email hello@launchgatehq.com.

Step 1 of 5 · Surface

What people can reach

Where is your app in its launch?

Tells us whether checks can happen before real users arrive.

Do people create accounts or sign in?

With accounts, one person's data has to stay out of everyone else's reach.

Is there an admin dashboard or staff-only area?

Admin pages need to be blocked on the server, not just hidden from the menu.

Can people upload files, such as images, documents or avatars?

Uploads need type and size limits, and storage that isn't public by default.

Step 2 of 5 · Money & AI

Money and AI

Does your app take payments?

Prices and payment confirmations should come from your server, not the browser.

Do you sell subscriptions or anything that renews automatically?

Renewal and cancellation wording is a common topic for attorney review.

Does your app send user content to an AI model, for chat, summaries or generation?

That content is shared with an outside provider, and prompts can be manipulated.

Can an AI agent take actions with tools, such as sending email, changing records, browsing or spending money?

An agent with tools should have the smallest set of permissions that still does the job.

Step 3 of 5 · Sensitive data

Who it's for and what it holds

Could children under 13 use it, or is it aimed at kids?

Children's data comes with stricter rules, such as COPPA in the US.

Will schools, teachers or students use it?

Schools usually ask how student data is stored, shared and deleted.

Does it collect health, wellness or medical information?

Health details are among the most sensitive data an app can hold.

Do you store financial details yourself, such as bank details, income or account numbers?

Card numbers that only your payment provider handles don't count. Anything you keep does.

Step 4 of 5 · Data flows

Where data goes

Do you use analytics, ad pixels or other tracking scripts?

Trackers that fire before a visitor agrees are a frequent source of privacy complaints.

How many outside services receive your users' data?

Count your database host, email, payments, analytics, AI, file storage and support chat.

Do you expect visitors or users in the EU or UK?

EU and UK users bring GDPR-style expectations for consent, access and deletion.

Does your privacy policy match what the app really collects and shares?

Having a policy isn't the same as having an accurate one.

Step 5 of 5 · Safety nets

Your safety nets

Can people delete their account and data?

Deletion should also reach backups and outside services on the schedule your policy states.

Have you restored a backup to check that it works?

A backup only counts once you've restored it and confirmed the data is all there.

Would you find out quickly if the app broke or started throwing errors?

You want to hear about an outage before your users email you.

Have you tested sign-up, checkout and other key flows with only a keyboard and a screen reader?

If a flow can't be finished without a mouse, some visitors can't finish it at all.

How the profile works

Four readings, all from your own answers

Security exposure
How much of your app someone could reach and misuse: accounts, admin areas, payments, uploads, stored financial details and AI tools.
Privacy complexity
How much personal data you handle, how many places it goes, and how many consent and policy questions that raises.
Legal review need
Topics that often need an attorney or specialist: children, schools, health, renewals, EU users and policy accuracy. LaunchGate flags them; it does not give legal advice.
Reliability maturity
Which safety nets you already have: tested backups, error alerts and accessibility testing. Unlike the other three, higher is better here.

"Not sure" answers count as partial risk, because an unknown is worth checking. The self-check never looks at your app or code. For that, start with a Free Launch Check: a preliminary public-surface review, not a full audit.