Make Your App Save Data Safely
Every app stores data somewhere. The question is where, and who can see it. Get this right and the rest of the project is ordinary work. Get it wrong and you find out from a stranger.
Your case: the browser is enough
A personal habit tracker can keep everything in the browser's local storage, which is what you already built. Nothing leaves the device, so there is nothing to leak and no server to pay for.
The cost is honest to state: the data lives in one browser on one device. Clear the browser's data and it is gone. Add a button that downloads the data as a file and one that loads it back. That is your backup, and it takes the AI a few minutes to add.
Your case: a hosted database and a way in
A shared list must live on a server so both phones see the same thing. The simplest route for a beginner is a hosted database service with a free starter plan, one that also handles logins, so you are not writing password code yourself. Read What Is a Database first if the word still feels vague.
Ask the AI to swap the local storage code for the hosted database, and to make each list visible only to the people who belong to it. Then test that rule on purpose: make a second account that is not in your household and check it cannot see your list.
Your case: a hosted database, a locked owner page and a deletion plan
Booking requests hold other people's names and contact details. Use a hosted database service that handles logins, so the owner's inbox sits behind a proper sign-in and nobody else can read it. Read Security Basics before you start this part.
Ask the AI to save each request to the database, to put the owner's inbox behind a login, and to add a way to delete old requests. Then try to open the inbox while signed out. If you can see anything, stop and fix that before any real customer uses it.
Say on the form what you keep and why, in a sentence. People are more willing to fill in a form that tells them.
Your case: nothing to save, on purpose
If your quiz shows the score and forgets it, there is no personal data at all, and the quiz can stay as plain files. That is the safest design available, so keep it unless you have a real reason to change.
If you do want to keep scores, ask yourself who needs them. If only the person taking the quiz does, the browser's local storage is enough. If you want a public leaderboard, you now store names from strangers, and you need a hosted database and a plan for rude names.
Keys stay out of the browser
A hosted database gives you secret keys. Any key that lets someone write or read everything must never be in code that runs in the visitor's browser, because anyone can read that code. Ask the AI directly: "Is any secret key in code that the browser downloads?" Then check the answer yourself by searching the project for the key.
Your turn
Put your data where your case says, test the privacy rule by trying to break it, and take a save point.
Video deep dives for this stage
Official showcase
Community picks
No videos for this stage yet.