Sensitive data scanning

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Sensitive data scanning working in a real project rather than a sandbox.

   Set up Sensitive data scanning in this project — detect personally identifiable information easily. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Scan chat history for exposed PII before an audit

   The record lists this as one of the jobs Sensitive data scanning is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Sensitive data scanning for scan chat history for exposed PII before an audit. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Sensitive data scanning is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Sensitive data scanning before I publish. Check PII detection across projects and customizable admin settings, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Run an on-demand check for sensitive data across a project

   A second job the record lists for Sensitive data scanning, useful once the first path works.

   Extend this project so Sensitive data scanning also covers run an on-demand check for sensitive data across a project. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Sensitive data scanning?

  Sensitive data scanning is Lovable's Security feature: Detect personally identifiable information easily. Enterprise workspaces can enable sensitive data scanning to detect PII across projects.

• Is Sensitive data scanning GA or in beta?

  Sensitive data scanning is generally available (GA) on Lovable.

• What Lovable plan includes Sensitive data scanning?

  Sensitive data scanning is available on all Lovable plans.

• When did Sensitive data scanning launch?

  Sensitive data scanning launched on May 27, 2026.

• Automatic fixes for Basic scan findingsSame category, also GA · Jun 2026
• Scheduled security scans (Enterprise)Same category, also GA · Jun 2026
• Security scan profilesSame category, also GA · Jun 2026