← Back to Can I block a user who misuses my app?
A user says they see someone else's data. What do I do?
Short answer
Act at once: take away access that should not be there, note what they saw, and write to [email protected] straight away.
Deeper
Treat this as urgent. This help cannot tell you how serious it is or what the law asks of you, and this answer is not legal or security advice.
How access works. Your app keeps its data in vaults, not in a database of its own. This holds for an app that people sign in to; a website cannot read or write vaults. A vault is the place where a person or a group keeps their records. Each person sees only what they may reach: their own vault, and what others have shared with them. Your app gets no more than the signed-in person can. Some ways this can happen: they were given a way to reach it, it was put where anyone can open it, or another person's sign-in is open on a shared computer. A fault in your app or in GilbPlatform could also do it. This help cannot tell which it was; the places below are where to look.
Stop the sharing. Look in these places:
- A vault of yours that holds other people's records, such as a club's shared vault. Read lets a person read the vault. If they should not reach it, take their access away, as the answer How do I take access away? shows: from their next request they are refused.
- A vault made public by mistake. Make it private again. Making it private ends only its Everyone (public) line: a record or file made public on its own stays public, so check those too; the answer How do I make a vault public? says where.
- Your app's own files. Everything in the folder that was put live can be opened by anyone with the app's address. If real people's data was put in those files, for example as test data, ask your AI to take it out and put the app live again at the same address; see How do I put test data into my app, and clear it out before going live? and How do I update my app after it is live? Putting the app live again replaces what the address shows. This help cannot say whether copies of the earlier files can still be reached, so tell support as below.
- A shared computer. Your app can keep a person signed in on a browser for a while. Ask the user to press your app's button to sign out, then sign in again with their own e-mail.
Then find out what they saw. Ask them which page, what it showed and when. Take a screenshot, a picture of the screen, or ask them for one. Keep it only for support, because it shows someone else's data, and ask them not to pass the data on.
Tell support. Write to [email protected] at once, with your app's address, the vault, what was seen and when. If you need to know who held access and when, say so. The full history of who held access, and when, is read only by the account that runs GilbPlatform, the service that keeps the vaults.
Find the cause. Ask your AI to find the cause and to show you before it changes anything; the answer How do I tell my AI about a fault so it can fix it? shows what to tell it.
The law. Whether the law asks you to tell anyone, such as the people affected or an authority, and how fast, this help cannot tell you. Ask someone who knows the law where you and your users are, at once.
The answers I think my app leaked data. What do I do? and Who can see and use my app once it is live? tell more.
This answer is written for a computer screen.
Source: Live help pages, sentences shared: Who can see and use my app once it is live? (vaults, not a database of its own; each person sees only what they may reach; your app gets no more than the signed-in person can; everything in the folder put live can be opened; Read lets the person read the vault); I think my app leaked data. What do I do? (take access away; making a vault private ends only its Everyone (public) line; write to [email protected]; the history of access is read only by the account that runs GilbPlatform; ask your AI to show you before it changes anything; the law); How do I take access away? (from the next request); Can my app have its own users who sign in? (stay signed in from 5 minutes up to 14 days; a button to sign out); How do I put test data into my app, and clear it out before going live?; How do I update my app after it is live? Standards read from GilbPlatform on 13 November 2026: Proc_v_i_c_PublishPagesDev (step 3: a Sign out button).
Checked against GilbApp d529620.