·4 min read
ByDaniel A·Kraftwire Software

How to Earn and Embed a Security Badge for a WeWeb App

Illustration for How to Earn and Embed a Security Badge for a WeWeb App

Trust badges are small symbols placed on a website. They act as seals of approval for online shoppers. A security badge points to measures that protect personal data.1

What security trust badges show

Trust badges give visitors a visual sign that a website is trustworthy. They can help shoppers feel safer when buying online.1

Different badges address different worries. A security badge can ease concerns about data safety without adding words that reinforce those fears.1

Security badges signal that a site has measures to protect personal data. An SSL certificate is one such measure.1

Without SSL, most browsers warn visitors that a site is not secure. That warning can put customers off. The site owner adds badge code to the website’s HTML.1

Common security flaws in WeWeb apps

A no-code app can be secure when its platform offers the right controls. Those controls also need the right settings.2

A secure platform does not make every app built on it secure. Repeat the security review with each release and changes to data, roles, permissions or workflows.2

Loading a whole collection into WeWeb sends those records to the browser. A frontend filter may show only the current user’s rows.2

The hidden rows can still be seen through the browser’s inspect panel. This exposes data because the backend sends more than the page needs.2

Filter private data on the backend so other users’ records never reach the browser. In WeWeb’s backend, create a Table View filtered for the signed-in user.2

Bind the page to that view rather than the raw table. For Xano, use a user-specific endpoint; for Supabase, use Row Level Security.2

Signing in proves who a user is, not what they may do. A signed-in user may still reach or change someone else’s records if access checks are missing.2

Protect the resource, not just the page that displays it. Each WeWeb Table View and API endpoint has its own security setting.2

A private key exposed in the frontend can be copied. Someone with that key can run their own workloads on your bill.2

Move the call into a backend workflow, or use a WeWeb native connection that holds the key. For a backend HTTP request, keep the key in an environment variable and refer to it in the request header.2

Core controls beyond the badge

Web app security needs ongoing work, not just a one-off audit. Require MFA and short-lived tokens, and give users only the access they need.3

HTTP security headers offer a low-cost way to block whole groups of browser attacks. They can be added through a change to how the app is deployed.3

The controls include a strict Content Security Policy, HSTS and limits on framing. A nonce-based policy is part of this set of controls.3

Use queries with parameters for database calls. Check all inputs against a strict schema at the API gateway or controller.3

Define allowed inputs rather than relying on a list of banned ones. Encode user-controlled data before placing it in HTML, JavaScript, CSS or URLs.3

Scan staged files for credential patterns before each commit. Pin software dependencies to exact versions in a lock file.3

Review the dependency tree each week for known issues. Rotate long-lived secrets every 90 days, and at once after staff departures or a security incident.3

Qualifying for and embedding a SimplyScan badge

SimplyScan offers app scanning for tools including WeWeb, Supabase and Xano. Its scan covers security alongside areas such as speed, SEO and accessibility.4

SimplyScan unlocks a badge when a scan scores at least 80, with no critical or high-severity findings. Any qualifying free or Pro scan can generate a badge, with no charge for embedding or verification.5

SimplyScan provides HTML and Markdown snippets for a site footer, README or landing page. The badge links to a live public page on simplyscan.io showing the app’s score and scan date. Rescan after major changes to refresh the score.5

Sources

  1. saleswarp.com › trust-badges-to-boost-consumer-confidence
  2. weweb.io › how-to-make-secure-web-apps
  3. yusmpgroup.com › web-app-security-best-practices-2026
  4. simplyscan.io
  5. simplyscan.io › badge

Frequently asked questions

For a SimplyScan badge, the app must score at least 80 in a scan. There must be no critical or high-severity findings. Qualifying free and Pro scans can both generate a badge.
The SimplyScan badge links to a live public page on simplyscan.io. That page shows the app’s score and scan date, so visitors can verify the badge rather than trust a pasted image.

Is your app secure? Run a free security scan in 30 seconds · free account required.

Scan your app free →