Lovable gets a working app live fast. What visitors can see without logging in depends on the app's access settings. This check shows which data and actions your app opens to visitors without a login. To show how the check works, Flow Lab built a booking app in Lovable for a mobile dog grooming business and published it. Then the app went through the same check as client apps: first from the outside, using only the public link, then through every main step a customer and the owner take on a phone. The top-priority finding concerned the owner role. Sign-up is now turned off and the one-time "Make me the owner" button is removed, so no visitor can claim that role. The full report is below: 7 findings, all fixed and retested on the working app.
From the outside, using only the public link. Your app is checked exactly as anyone without a password would see it. The check shows whether customer data stays hidden without a login, whether new accounts get only the access they're meant to have, whether uploaded files are closed to the public and whether the page code is free of secret keys that give access to customer data. The check is view-only: nothing in the app is changed or copied.
On a phone, as your customer and as the owner. Each main step is tested on a phone screen: booking, rescheduling, late cancellation, the waitlist, reminders and the owner dashboard.
This check doesn't include a line-by-line review of the code and the access settings for your data. That's part of the full review, and the Walkwren sample shows what it covers.
| 1 | The owner role is now closed to visitors | top priority | fixed |
| 2 | A freed-up slot now goes only to a client whose visit fits | protects revenue | fixed |
| 3 | At most one reminder per person every 7 days | protects message delivery | fixed |
| 4 | The Book button now works in one tap | protects bookings | fixed |
| 5 | Messages now have full links to the site | working links | fixed |
| 6 | 6 Screens now show accurate message status | customer trust | fixed |
| 7 | The owner dashboard now loads the same way every time | low priority | fixed |
| Checked: customer data stays hidden without a login, there are no secret keys in the page code and no files are publicly open. | checked | ||
What was found. The owner role was reachable through the "First time? Create the owner account" link on the public sign-in page and the one-time "Make me the owner" button in the dashboard, with sign-up open to everyone. Now no visitor can claim the owner role.
What it means for the business. Every customer's name, phone number and home address, the schedule and the message history stay hidden without a login.
What was fixed. The link and the button are removed, sign-up is turned off, and the owner role can no longer be claimed from inside the app.
How it was retested. The sign-in page now only lets people log in, and the login settings show that sign-up is turned off.
What was found. After a cancellation, the app offered the free 45 minutes to a waitlisted client whose dog needs 100 minutes. They tapped "Take it" and saw "Already taken, someone was a little faster," even though the slot was still free.
What it means for the business. The waitlist now does what it was built for: it fills empty slots. A visit booked from the waitlist shows up in the owner's week.
What was fixed. Offers now go only to people whose visit fits the gap, based on the area, travel time and closing time. The offer shows their own service and how long it takes. If the booking can't go through, the screen shows the actual reason.
How it was retested. A visit was canceled, the app offered the slot to a client whose visit fits, the client tapped "Take it" and saw "It's yours!", and the visit showed up in the owner's week.
What was found. Every booking someone started created a new lead, so a person who started twice from the same number got the same "Still want that groom?" message several times.
What it means for the business. Customers get one reminder instead of several. Email and text providers flag senders of repeat messages, and the app no longer sends them.
What was fixed. Leads are merged by phone and email. One person gets at most one reminder every 7 days, and reminders stop once a booking is finished.
How it was retested. Running the reminders twice in a row sends each message only once.
What was found. The first tap on "Book a groom" only checked the ZIP code, and the screen stayed the same until a second tap.
What was fixed and how it was retested. One tap now checks the ZIP code and opens the next step.
What was found. Links in emails and texts were missing the site address. Screens showed "sent" while the messages were still waiting in the outbox.
What was fixed and how it was retested. Messages now have full links to the site. The screens show the statuses "handled" and "ready to send," with a note that messages are actually sent once the business's own email address is connected.
What was found. On the first load, the dashboard could look different from the fully loaded version, because the server's copy didn't match the browser's. The browser also logged an error that the owner never sees.
What was fixed and how it was retested. The dashboard's first screen now matches the fully loaded version, and a fresh page load shows no errors.
The short version for the owner: customer data stays hidden without a login, the page code holds no secret keys, sign-up is turned off, and Lovable's own security scan passed with no findings.
The log below is exactly as it ran. Every request is read-only and uses the same public key any visitor's browser already gets. Values are never printed, only whether a table answers and how many rows it shows.
App: https://bramblewash-bookings.lovable.app
Backend: Lovable Cloud (found in the page code, 29 script files)
Secret keys in page code ........ none
Tables answering without login .. 15 checked · 0 rows visible in all 15
Sign-up ......................... disabled
Email confirmation .............. on
Functions exposed by name ....... 5 (not called: calling could change data; the builder
confirmed in the database that visitors can't run the admin ones)
Lovable security scan ........... 0 issues
You get a report on your working app within one business day, from $150. For every finding, you see what was found, what it means for the business and how to fix it. You can make the fixes yourself or have Flow Lab make them as a separate stage, and then the app is checked again. Flow Lab works only with your written permission. The check is view-only, and your customers' data is never copied.
The easiest way to start: send the link to your app and one sentence about what your customers do in it. Flow Lab will reply with where the check would begin and what it would cost. No commitment.
Demo app: bramblewash-bookings.lovable.app. Tap "Open Maya's dashboard (demo)" to see the owner side.
P.S. If your app already takes bookings or payments, the best time for the check is before the first few hundred customers sign up. The report then shows what to fix and how while your customer list is still small.