Customer files are visible when your app saves them in an open online folder
If your AI-built app saves uploads, invoices, exports, or backup files in an open online folder, strangers may be able to view customer information without signing in. Here is a simple review you can do now.
before you start
A file that should belong to one customer can become visible to anyone if it is saved in the wrong online folder.
A customer file can end up visible to strangers
in plain words
This means your app may save a receipt, photo, PDF, or report in a place that anyone on the internet can open if they have the link.
If your app lets people upload documents, download invoices, save profile images, or export reports, those files have to live somewhere online. The problem starts when that online folder is open to the public instead of limited to the right person. Then a customer file that feels private inside the app may actually be visible from outside the app.
Why this matters is simple: customer information can leak without you noticing. A stranger might open a receipt, see a customer name, email address, order number, home address, or account details, and you may only discover it later. Developers call this a public storage bucket. The technical name helps when you talk to an AI builder or hosting service, but the beginner rule is easier: if a signed-out visitor can open the file link, the file is too exposed.
- ▸A file link should not work for strangers just because they found or guessed it.
- ▸Customer uploads, invoices, and exports should only open for the right person.
- ▸Old test files can expose customer information too.
common risk
You copy a receipt link from your app, open a fresh browser window where you are signed out, and the file still loads with no warning or sign-in screen.
what to do now
Pick one file that belongs to a customer and try opening it while signed out. If it opens, treat that storage area as urgent and remove public reading first.
ask your AI
Inspect this app and list every place where files are stored or served. For each place, tell me in simple language whether a signed-out visitor can open files there, whether customer files are stored there, and what I should change first to stop public viewing.
First make a map of every place files are saved
in plain words
Before you fix anything, find every online folder or storage area your app uses and check who is allowed to open files there.
Many beginner-made apps save files in more than one place. Product images may go to one folder, customer uploads to another, and exported reports to a third. If you only review the obvious upload area, you can miss the folder that quietly stores invoices, backups, or support attachments. One open storage area is enough to expose real customer information.
This matters because file settings are often different from one location to another. The technical name is a permission review, which means checking who can read files in each storage area. In plain language, open the storage settings and look for words such as public, anyone, everyone, anonymous, or no sign-in required. If those settings allow reading, that area should not hold customer documents. Also check whether old folders created during testing are still active, because leftover sample data often stays forgotten long after launch.
- ▸Write down uploads, receipts, exports, backups, images, and logs separately.
- ▸Check both current folders and old test folders.
- ▸Look for settings that allow reading without sign-in.
common risk
Your app keeps profile images in one place and invoice PDFs in another. You lock down the image folder but never notice the invoice folder is still open to anyone with the link.
what to do now
Create a simple list of every file location your app uses, then review each one one by one and note whether it is open, protected, or unclear.
ask your AI
Trace this app and give me a plain-English inventory of every folder, bucket, or storage area it uses for uploads, images, documents, exports, backups, and logs. For each one, tell me whether reading is public, sign-in only, or unclear, and show me the exact setting I need to review.
Keep customer documents out of open download areas
in plain words
Files are safer when they are stored in a place that visitors cannot download directly from the public site.
Some file areas are meant for harmless public items, such as marketing images or documents you want everyone to read. Customer receipts, identity images, invoices, tax files, and exported reports do not belong there. If your app needs to show a customer file, it should first check that the person opening it is the right person. That way the app can still display the file without leaving it openly downloadable to strangers.
This matters even more when a file contains a password, payment key, access code, or backup data. Those are not vague technical items. They are concrete things that can unlock customer records, send money, or open admin actions. Developers may describe these as sensitive configuration files, but the plain rule is better: if a file contains a password, payment key, access code, or customer information, it should never sit in an area that the public can download from directly.
- ▸Open download areas are for harmless public files, not customer records.
- ▸Customer files should require a signed-in user or a short-lived file link.
- ▸A backup file can be as dangerous as a live customer document.
common risk
A backup file stored in an open folder includes a database password and exported customer rows, so anyone who reaches that file can see customer information and reuse the password elsewhere.
what to do now
Move customer documents, backups, and any file containing a password, payment key, or access code out of open download areas immediately.
ask your AI
Find every file location in this app that stores customer documents, invoices, receipts, backups, passwords, payment keys, or access codes. Move those items to protected storage, stop public reading there, and explain in simple language how the app should safely show files only to the correct signed-in user.
Also review file names, old links, and forgotten leftovers
in plain words
Even after storage settings improve, customer information can still leak through revealing file names, old shared links, or forgotten test exports.
A file does not have to be in a fully open folder to create trouble. Sometimes the file name itself reveals too much, such as a customer name, email address, order number, or date of birth. Sometimes an old shared link still works long after it should have stopped. Sometimes a test export, support attachment, or sample backup remains online because nobody cleaned it up. These are easy mistakes to miss because the main app screens may look fine.
Why this matters is that small clues make customer files easier to find and easier to understand. Developers call one version of this direct object access, but you do not need the term to fix it. Use plain steps instead: rename files so the names do not reveal customer details, delete files you no longer need, and shorten the life of shared links when possible. If your app creates links for downloads, those links should stop working after a short time or after the user signs out.
- ▸Use neutral file names that do not reveal customer details.
- ▸Delete old exports, sample files, and leftover backups.
- ▸Review whether shared links keep working longer than they should.
common risk
A file named emma-lee-order-4821-refund.pdf is saved online, and even if the folder is not obviously listed in the app, the file name tells a stranger exactly what the document is about.
what to do now
Search your stored files for names, email addresses, order numbers, dates, and old exports, then rename or remove anything that reveals customer information.
ask your AI
Scan this app’s stored files and file links for customer names, email addresses, order numbers, dates, old exports, old backups, and long-lived download links. Give me a cleanup plan that says what to rename, what to delete, and which links should expire sooner.
Test again after every change so the issue does not return
in plain words
A file problem can come back when a new feature creates a new online folder, so you need to recheck from the outside after updates.
Fixing one open folder is only the start. After any change, sign out and test again from a fresh browser window. Try the file links that should be protected and confirm they no longer open for strangers. Then test any new upload, export, invoice, or report feature, because AI building tools often create new storage paths automatically when you add features.
This matters because protection can slowly drift over time. A safe setup today can become unsafe after a later change, a copied project setting, or a new export screen. Ongoing watching helps here. VibeCodeWall checks the public app from the outside and watches for important changes over time. It does not see private code. That is why your best habit is to keep retesting the public-facing file paths, download links, and visible documents that a normal visitor could reach.
- ▸Test from a signed-out browser, not only from your own account.
- ▸Recheck after every new upload, export, or report feature.
- ▸Keep watching for newly created public file paths.
common risk
You lock one invoice folder today, but next month a new AI-generated report feature creates a different open folder and customer reports begin appearing there.
what to do now
After each update, test the file links a stranger could try, write down what still opens while signed out, and fix any new open storage area immediately.
ask your AI
After every update to this app, re-audit all publicly reachable file paths, download links, upload areas, and export features. Tell me in plain language whether any customer file can still open while signed out, identify any new open storage area, and suggest the exact fix.
Quick checklist
- 01List every place your app saves files, including uploads, images, PDFs, invoices, exports, backups, and logs.
- 02Test one real file link while signed out to see whether it opens.
- 03Turn off public reading anywhere customer files are stored.
- 04Check file names for names, email addresses, order numbers, or account details.
- 05Remove old test files, sample exports, and leftover backups.
- 06Make sure shared file links expire or require a signed-in user.
- 07Review every storage area one by one instead of assuming they all use the same rules.
- 08Repeat the check after each new feature that creates or shares files.
FAQ
How can I tell if a customer file is too open?
Open the file link in a fresh browser window while signed out. If it loads without sign-in, it is too open.
Do all files need to be hidden from the public?
No. Public images or documents meant for everyone can stay open. Customer uploads, invoices, receipts, exports, backups, and files containing a password, payment key, or access code should be protected.
What is the easiest first step?
Make a list of every place your app stores files, then test one file from each place while signed out.
Can this problem return after I fix it once?
Yes. A new feature can create a new storage area or change file settings, so repeat the review after updates.