United Kingdom version. The same 35 technical checks, with the UK duties spelled out: reporting a breach to the ICO within 72 hours, answering an erasure request within one month, and PECR consent for anything stored on a visitor's device. US version

Launch Readiness Checklist (UK)

Pre-launch checks for apps built with Lovable, Bolt or v0, with the UK GDPR duties that apply: ICO breach reporting, erasure deadlines and PECR consent.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Launch Readiness Checklist?

An app built with Lovable, Bolt, v0, Replit Agent or Cursor usually works. Whether it is safe to launch in the UK is a separate question, and part of it is legal rather than technical. If your app holds anything about an identifiable person, you are a controller under the UK GDPR and the Data Protection Act 2018, and a handful of specific duties start the day you launch rather than when you reach some size.

The technical checks here are the same ones that apply anywhere: row-level security on every table, storage buckets with their own policies, secret keys kept out of the browser bundle, a backup you have actually restored. What this version adds is the deadline attached to each legal item. A personal data breach likely to risk people's rights must reach the ICO within 72 hours of you becoming aware of it, which is a hard deadline you cannot meet without logging that tells you a breach happened at all.

That link between the operational items and the legal ones is the point. Error reporting is not only good practice in the UK; without it, you will not know a breach occurred, and "we had no logging" is not a defence the ICO treats kindly.

  • 35 checks across eight themes, from data access to legal disclosure
  • Filter by stack: Supabase, Firebase, another hosted database or serverless functions
  • Filter by risk, so critical items can be worked first
  • A counter that tracks critical items separately from the total
  • Markdown export with unchecked items first and their "what to do" line attached
  • Runs entirely in your browser; ticks are never uploaded
Read the guide: What to Check Before Launching an App You Vibe-Coded

Updated

How to use the Launch Readiness Checklist

  1. Choose your stack and work the data-access theme first. Under UK GDPR this is your security obligation under Article 32, not merely good practice.
  2. Treat every critical item as launch-blocking. Row-level security left off is the most likely route to a reportable personal data breach.
  3. Note who in your organisation would make the ICO report. A sole trader is still a controller, and the 72 hours runs from awareness.
  4. Check the legal theme against what you actually do: a privacy notice naming real processors, an erasure path you have tested, and consent for any non-essential storage on the device.
  5. Export the remaining items as Markdown and keep the dated copy. Records of your decisions are part of demonstrating accountability.

Worked examples

Before launching a UK side project

Input

Stack: Supabase. Depth: Critical only

Output

Nine critical items, plus the ICO reporting path

The short pass. If a critical data-access item is open at launch, a breach is a question of when rather than whether.

An app holding customer records

Input

Stack: Everything. Depth: Everything, including medium

Output

All 35 items, with the legal theme mapped to UK duties

Erasure within one month, a privacy notice that names each processor, and PECR consent for any non-essential cookies or local storage.

After a near miss

Input

Tick what is confirmed, then download

Output

A dated Markdown record of what was checked

Accountability under Article 5(2) means being able to show the decisions you made, not only making them.

Background and insight

AI builders are excellent at the happy path and quiet about everything else. They will produce a working signup, a working dashboard and a working checkout, because those are the things a prompt describes. Nobody prompts for "and make sure a second user cannot read the first user's rows", so that part is left at whatever the default was.

The default is the problem. An app generated this way usually talks to its database straight from the browser using a key that ships inside the bundle, which is safe only because row-level security is supposed to stop that key from reading anything it should not. When row-level security is off, or on but missing a policy for one of the four operations, the interface looks completely normal and the data is readable by anyone who opens the network tab.

The second pattern is secrets. A payment or model-provider key pasted into a component ends up in the JavaScript every visitor downloads. Removing the line later does not help, because the key is already in git history and in the bundles people have. It has to be rotated at the provider and moved behind a server function.

The rest are the ordinary operational things that any application needs and that no prompt produces: a backup you have restored at least once, error cases that fail visibly rather than hanging, a way to learn about a failure before a customer tells you, and a copy of the code somewhere the platform does not control.

Common use cases

  • Before a first launch

    Find the data-access and secret problems while the user count is still zero.

  • Taking over an app

    A repeatable first pass when a client or a founder hands you something built in a builder.

  • After the app misbehaves

    Work out which operational gap produced the incident, and close the rest before they do the same.

  • Deciding whether to depend on a platform

    The portability items turn vendor lock-in from a feeling into a short list of facts.

Tips and limitations

  • Test access with a second account, not your own. When you are the only user every row belongs to you, so a cross-account leak cannot appear.
  • Row-level security being enabled and a policy existing are two different settings. A table with policies but RLS switched off is still open.
  • A key that was ever in a frontend bundle or a public repository has to be rotated, not deleted. The copies people already downloaded do not change.
  • A backup you have never restored is a file you hope is a backup. Restore it once into a scratch project.
  • Take an export before letting an agent change the schema. A prompt that drops a column looks exactly like a prompt that adds one.
  • Set a spend cap on anything billed by usage. A loop or a scraper turns a quiet week into a large invoice.

Sources and further reading

  1. Guide to the UK General Data Protection Regulation (UK GDPR), Information Commissioner's Office. Controller duties, security and accountability
  2. Personal data breaches: a guide, Information Commissioner's Office. The 72-hour reporting duty and what counts as a breach
  3. Right to erasure, Information Commissioner's Office. The one-month deadline and its extensions
  4. Cookies and similar technologies, Information Commissioner's Office. PECR consent for non-essential storage on a device
  5. Data protection fee, Information Commissioner's Office. Who must pay and the tiers

Frequently asked questions

Does UK GDPR apply to my small app?

Yes, if it processes personal data about identifiable people, whatever its size. There is no small-business exemption. A one-person project holding customer names and emails is a controller with the same core duties as a large company, though what is proportionate for you differs.

How quickly must I report a data breach to the ICO?

Within 72 hours of becoming aware of it, where the breach is likely to risk people's rights and freedoms. If the risk is high you must also tell the affected people without undue delay. The clock runs from awareness, which is why error reporting and logging matter legally and not only operationally.

Someone asked me to delete their data. How long do I have?

One month from the request, extendable by two further months for complex cases if you tell them within that first month. The practical problem is rarely the deadline but knowing every place the data sits, which is why the checklist asks you to map personal data to tables and buckets before launch.

Do I need a cookie banner for my analytics?

Under PECR you need consent before storing or accessing anything on a visitor's device that is not strictly necessary for the service they asked for, and analytics is not strictly necessary. Some analytics tools avoid device storage entirely, which is the simplest way to avoid the banner.

Do I have to register with the ICO?

Most organisations processing personal data must pay the data protection fee, which is tiered by size and turnover, unless an exemption applies. The ICO publishes a self-assessment to check. It is an annual fee, not an approval process, and it does not certify anything about your app.

Is there an in-depth guide to the Launch Readiness Checklist?

Yes. “What to Check Before Launching an App You Vibe-Coded” covers the background, how it works, common pitfalls and worked examples. Read the full guide.