Vikrant Deshmukh Human review for AI-built apps

Sample report · a real review of a test app

FitPlate, reviewed.

On 5 and 6 October 2026 I built FitPlate, a client portal for a nutrition coach, with Lovable, the way a non-coder would: four plain-English prompts, every default accepted. It has sign-up, an intake form with health details, a coach area, meal plans and progress photos. Then I reviewed it as a Launch Check.

Lovable’s own scan, run when I published it, said “No security issues found.” Here is the full report. It’s my own app, so nothing is redacted.

Checked
  • Code
  • Live site
  • Database rules
  • Logins
  • File storage
  • Coach area
  • Backups
  • Building blocks
Couldn’t check
Payments, because this app doesn’t take any. A real photo upload, because no photos existed yet; the storage rules were checked in the database instead.

Findings

11 confirmed · most urgent first

  1. Fix today

    Health details are collected with no privacy notice

    Sign-up and intake form

  2. This week

    Clients’ progress photos aren’t in any backup

    File storage

  3. This week

    Nobody is told when the app breaks

    Monitoring

  4. This week

    Passwords can be six characters

    Sign-in settings

  5. This week

    There’s no “forgot password”

    Sign-in page

  6. Noted

    Any signed-in client can ask who the coach is

    Coach permission check

  7. Noted

    Progress photos accept any type of file

    File storage

  8. Noted

    Intake limits exist only in the form

    Intake form

  9. Noted

    Only a database change can add or replace the coach

    Coach setup

  10. Noted

    Two browser protections are missing

    Hosting

  11. Noted

    Thirteen “high” warnings in build tools, none of them reachable

    Building blocks

Built by
Lovable, from four prompts
Checked by
Vikrant Deshmukh
Date
6–7 October 2026

Every finding, in full

Each one says what’s wrong, what it could cost you, how I confirmed it, and what the fix is. In a paid report you also get the exact steps, or I make the fix for you.

Fix today

Fix today 1 of 11

Health details are collected with no privacy notice

Sign-up and intake form

What’s wrong
The intake form asks for health conditions, medications and allergies. Nowhere does the app say who sees them, how long they’re kept or how to delete them, and it accepts sign-ups from age 13.
What it could cost you
Health information is the most sensitive data a small app usually holds. Collecting it with no notice or consent is a legal exposure (India’s DPDP Act, for one, treats anyone under 18 as a child who needs a parent’s consent), and it’s the first thing a careful client or partner asks about.
How I confirmed it
Read every page and route the app ships: no privacy page and no consent wording. The usual addresses for one all return “not found”.
How it gets fixed
A short privacy notice linked from sign-up and the intake form, a consent line before the form is submitted, and a minimum age of 18 or a parental-consent step.

Fix this week

This week 2 of 11

Clients’ progress photos aren’t in any backup

File storage

What’s wrong
Lovable backs up the database once a day. Files in storage, including your clients’ progress photos, are not part of those backups.
What it could cost you
If photos are deleted by mistake or by a bug, they’re gone for good. Restoring the database also loses up to a day of changes.
How I confirmed it
Lovable’s own backup documentation (checked 6 October 2026), compared with how the app stores photos.
How it gets fixed
Decide whether that’s acceptable and say so in your terms, or copy the photos somewhere else on a schedule.

This week 3 of 11

Nobody is told when the app breaks

Monitoring

What’s wrong
When a client hits an error, nothing reaches you. The app has no error alerts.
What it could cost you
You find out about a broken sign-up or a failing save when a client complains, or when they quietly leave.
How I confirmed it
Read the app’s error handling. The reporting hooks it does have only work inside Lovable’s editor, not on the live site.
How it gets fixed
An error-alerting service, so failures reach your inbox the day they happen.

This week 4 of 11

Passwords can be six characters

Sign-in settings

What’s wrong
The sign-in settings accept six-character passwords, below even Lovable’s own recommendation, for accounts that hold health details.
What it could cost you
Short passwords are the easiest to guess, and one guessed password opens that client’s health details and photos.
How I confirmed it
Read the app’s sign-in settings. Common breached passwords are already rejected, which helps.
How it gets fixed
Raise the minimum to at least ten characters. It’s a setting, not a code change.

This week 5 of 11

There’s no “forgot password”

Sign-in page

What’s wrong
A client who forgets their password has no way back in, and the coach can’t help from inside the app.
What it could cost you
Locked-out clients email you or give up. I hit this myself during the review.
How I confirmed it
Read the sign-in page and every route: no reset link and no reset page.
How it gets fixed
A “Forgot password?” link and a page to set a new one.

Noted

Noted 6 of 11

Any signed-in client can ask who the coach is

Coach permission check

What’s wrong
The check that decides who is the coach answers questions about any account, from any signed-in client.
What it could cost you
Low today, because client accounts can’t see each other, so there’s little to learn. Worth closing before the app grows.
How I confirmed it
Asked as a signed-in test client, and it answered. Lovable’s chat had flagged this too; its publish scan didn’t.
How it gets fixed
Let the check answer only about the person asking.

Noted 7 of 11

Progress photos accept any type of file

File storage

What’s wrong
The “images only” rule lives only in the page. Storage itself accepts any file up to 10 MB.
What it could cost you
Files that aren’t photos could end up in your storage. A low risk, but it’s your storage and your bill.
How I confirmed it
Compared the storage settings with the upload code.
How it gets fixed
Restrict the photo storage to image types.

Noted 8 of 11

Intake limits exist only in the form

Intake form

What’s wrong
Age, weight and height ranges are checked by the form, but the database accepts anything.
What it could cost you
Bad values could reach the meal-plan calculations if anything ever gets past the form.
How I confirmed it
Compared the form’s rules with the database’s.
How it gets fixed
Add the same limits to the database.

Noted 9 of 11

Only a database change can add or replace the coach

Coach setup

What’s wrong
The coach is set by a one-off database change tied to a single account.
What it could cost you
Fine with one coach. If that account is lost, or you take on a second coach, you’ll need a developer.
How I confirmed it
Read how the coach role was set up.
How it gets fixed
Write the steps down now, or add a simple way to manage coaches.

Noted 10 of 11

Two browser protections are missing

Hosting

What’s wrong
The site doesn’t send two standard settings that limit what scripts may run and stop other sites framing your pages.
What it could cost you
Small on their own. They’re the layers that help when something else goes wrong.
How I confirmed it
Read the live site’s response settings. Lovable’s hosting doesn’t currently let you add one of them.
How it gets fixed
Add the one Lovable allows, and note the other.

Noted 11 of 11

Thirteen “high” warnings in build tools, none of them reachable

Building blocks

What’s wrong
Four tools used to build the app have published warnings.
What it could cost you
None for your users. All four only run while the app is being built, on your own files, and none of them ships in the live app. An automated scanner would still show you “13 high”.
How I confirmed it
Checked every pinned version against a public vulnerability database, then checked which code the live app actually ships.
How it gets fixed
Update when convenient.

Checked and fine

A short report should mean “checked”, not “skipped”, so here’s what held up.

  • One client can’t reach another client’s details, meal plan or photos. Tested as one test client trying to read another’s data.
  • Visitors who aren’t signed in get nothing back from the database or from file storage.
  • Only the coach can open the coach area, and the database enforces it, not just the page.
  • No secret keys anywhere in the live app’s code or in the project’s history.
  • Email confirmation is required, and common breached passwords are rejected.

This report describes the app on the day it was checked. It is not a certificate, and nobody can honestly promise an app is 100% safe.