Will my users notice, or lose their data, when I update my app?
Checked against GilbApp d529620.
An update changes only your app's files, not your users' data, which stays in vaults. They should see the new version on their next visit.
Deeper
Your app stays at the same address, https://<name>.pages.dev, where <name> is the name given to your site. An update puts a new version at that address: it is published again under the same name. The answer How do I update my app after it is live? shows how.
What an update changes. What is put live is the folder of your app's files: its pages, its pictures and its scripts, the code that makes a page work. Your users' data is kept in vaults. A vault is the place where a person or a group keeps their records; a record is one piece of data, such as a person, a place, a thing or a note. When your app is published, GilbPlatform also makes a vault for it, named after your app and owned by you; who can reach it is set by that vault's access, as for any vault. Your users' own data stays in their own vaults. Publishing sends only those files; it does not change or delete what people saved in vaults. So what your users saved before an update is still there after it. A site published as a website cannot read or write vaults, so it keeps no users' data at all.
What your users see. People should get the new version the next time they open your app. A page someone already has open stays as it was until it is loaded again. Its files are served by Cloudflare, a web company, which says a published file stays ready on its network until the next time the site is published (https://developers.cloudflare.com/pages/configuration/serving-pages/, read 13 November 2026). GilbPlatform does not tell your users that a new version is out: it sends them no message and no e-mail about it. If you want them to know, the answer How do I tell my users what changed, and keep a list of changes? shows ways.
Staying signed in. How long a person stays signed in to your app is decided when your AI builds the app, and you choose the time. This page does not show that an update by itself keeps people signed in, and it has not been tried on a live app, so some people may have to sign in again after an update, for example when the update changes how your app signs people in. The answer Why must my app's users sign in again on every reload, or after a week? tells more.
When a change touches data. An update does not change your users' data, but from then on the new version is what reads and writes it. If the new version expects the data laid out in another way, what people saved before may not show or work as it did. When a change alters stored data or how that data is laid out, Kai-Zen, the planning agent (an agent is your AI following one written procedure, its standing instructions, for one kind of work), before it puts the change live, tells you what changes and asks you, a person, not an agent, for go. You could also tell your AI, in your own words, that what people saved with the old version must keep working in the new one, and check that yourself with something you saved before the update.
Try it before your users do. Your AI builds and tests the next version on your computer while the live version keeps running; it goes live only with your yes. When you sign in to the version on your computer, it saves into the same vaults as the live one, so what you save while you test is saved for real. The answer Can I have a test version and a live version of my app at the same time? tells more. Once the change is live, Kai-Zen asks you to check it live.
If an update broke something, see How do I fix a fault in my live app quickly, or go back to the last version?
This answer is written for a computer screen.
Source: Standards read from GilbPlatform on 13 November 2026: Kai-Zen.GoLive (Ask: if a change alters stored data or its shape, tell the requester what changes and ask a person for go), Kai-Zen.Update (Live, Human), Kai-Zen.HumanCheck, Agent.Coder (AskGoLive), Proc_v_i_c_PublishPagesDev, Standard Rule_Code_deployment (RuleDeployPagesDev). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/routes/publish.ts:442-486 (publishing admits the address and records the site; it writes nothing into users' vaults), src/publish/admission.ts:1-9 (a publish admits the same address again), src/routes/renew-sign-in.ts:1-6 and :100-108 (a sign-in renews only from its own address, while that address is admitted), src/auth/renewable-sign-in.ts:3-5 (a sign-in is bound to one device key and one exact address). This page does not state what an update does to people who are signed in; it was not tried on a live app. Also: workers/publish-ingest/src/checks.ts (only the folder's files are uploaded). Cloudflare, Serving Pages (https://developers.cloudflare.com/pages/configuration/serving-pages/, read 13 November 2026). Live help pages, sentences shared: How do I update my app after it is live?; Who can see and use my app once it is live?; Can I have a test version and a live version of my app at the same time?; How does Kai-Zen put a change live?; Why must my app's users sign in again on every reload, or after a week? (kept in the browser's storage for your app's address only when the app is built to keep it; people sign in once more after a sign-in change).