The short answer
SafeLaunch scores your website or app from 0 to 100 for each market you launch in, based on the severity of every open finding against 138 laws in 54 markets. 80 or above is Low risk, 55 to 79 is Needs work, and below 55 is High risk. Fixing critical and high findings moves the score most, and a re-check shows the new number.
Key takeaways
- No tool can certify that a website is compliant. A score tells you how close you are and what to fix first.
- Every market gets its own score, because the same tracker can break the law in the EU and be fine in another market.
- Bands: 80 to 100 is Low risk, 55 to 79 is Needs work, below 55 is High risk.
- Critical findings weigh the most, then high, medium and low. Many small issues never drag a score to zero.
- The free scan shows red, amber or green for each area of law and the top problems. A paid report scores every market and lists every finding with its fix.
On this page
01
Why can't anyone just tell me "compliant" or "not compliant"?
Because compliance depends on facts no scan can see on its own: where your customers are, what your contracts with vendors say, how your team handles a deletion request, whether children use the product. A scan can prove that a tracker loads before consent. It can't prove that every process behind the website works.
So SafeLaunch never labels a product "compliant". It measures what it can verify, asks you in plain English about what it can't, and reports how close you are as a score with a risk label. The labels deliberately say risk, not compliance: Low risk, Needs work, High risk.
02
How is the SafeLaunch score calculated?
Each finding has a severity, set by the rulebook: critical, high, medium or low. Each severity carries a weight, with critical findings weighing the most, roughly twice a high one and four times a medium one. The weights of all open findings that apply in a market are combined into a score from 0 to 100, with diminishing returns so a long list of minor issues never reads as zero.
| Score | Label | What it usually means |
|---|---|---|
| 80 to 100 | Low risk | A few open issues, mostly medium or low |
| 55 to 79 | Needs work | A critical or high issue, or several medium ones |
| 0 to 54 | High risk | Several serious issues at once, such as open data plus tracking without consent |
Scores are per market. A finding about EU cookie consent lowers your EU and UK scores, not your Texas score. A missing California "Do Not Sell or Share" link lowers California only. The overall score summarises the markets you chose.
03
A worked example: from 36 to 94
Here is how the score moves for a typical AI-built app checked for the EU, using SafeLaunch's actual scoring. It starts with one critical finding, two high, three medium and two low.
| After fixing | Open findings | EU score | Label |
|---|---|---|---|
| Nothing yet | 1 critical, 2 high, 3 medium, 2 low | 36 | High risk |
| The critical one (database table readable by anyone) | 2 high, 3 medium, 2 low | 50 | High risk |
| The two high ones (trackers before consent; privacy notice missing vendors) | 3 medium, 2 low | 73 | Needs work |
| The three medium ones (form labels, security headers, retention) | 2 low | 94 | Low risk |
04
What does the free scan tell me, and what does a report add?
Free scan (3 a month)
- What your product is and does
- Which legal pages exist
- Red, amber or green for each area of law
- The most serious problems
- What already passes
Launch Report and Launch Fix
- A score for every market you launch in
- Every finding, cited to the article or section
- Evidence: the page, or the file and line
- Launch Fix: code changes, builder prompts, draft policies
- Launch Fix: one free re-check within 30 days
In the free scan, an area turns red when it has a critical or high finding, amber when it has only medium or low ones, and green when the checks found nothing. Areas cover privacy and personal data, security, consumer law and terms, content and age checks, AI rules, accessibility, marketing claims and professional rules.
05
How do I raise my compliance score fastest?
- 01
Close anything critical today
Usually exposed data: a database table anyone can read, a secret key in the browser, a public file bucket. These carry the most weight and the most real-world risk.
- 02
Stop tracking before consent
Load analytics and ad tags only after Accept, and keep them off after Reject. See how the real-browser test checks this.
- 03
Make your privacy notice match reality
Name every service that receives data, every purpose and how people exercise their rights. SafeLaunch drafts it from what it found.
- 04
Fix the mediums in one sweep
Form labels, security headers, retention periods and terms gaps are usually small code and copy changes. A fix prompt can handle several in one pass.
- 05
Re-check and keep the record
Run a re-check on the new version. Resolved findings show as "no longer detected", new ones are flagged as new, and code reports can be signed off for the exact commit.
One free fix in your inbox each week
A new copy-paste prompt for Lovable, Cursor or Claude Code every week, with the rule behind it and how to check it worked. No spam, unsubscribe in one click.
By signing up you agree to get this weekly email. We send it with Kit, and you can unsubscribe at any time. What we share with Kit is in our privacy notice.
FAQ
Frequently asked questions.
Sources and further reading
This article is general information, not legal advice. SafeLaunch is automated software, not a law firm; a report records what was checked on one version and is not a certificate of compliance. Read the disclaimer.
From the founder
SafeLaunch is built by Raghav R Handa, a lawyer-turned-builder in New Delhi. He writes about this topic in plain English:
See what SafeLaunch finds on your product.
Paste a link and get your score, the most serious problems and what already passes, in about a minute.
Keep reading