MyJackfruit

Help
Browse topics · Your data and vaults while building

Your data and vaults while building

← Back to Do I need a privacy page and a cookie banner?

Who can see and use my app once it is live?

Short answer

Anyone with its address can open your app. A person who signs in to it reaches only the data they themselves may reach.

Deeper

Also asked:

Who owns the data my users put in? MyJackfruit's Pricing page says: Each person owns their vault. What your users put in through your app is kept in their own vaults. Who owns what a person writes in a vault of yours, the Terms do not say; if you need to know, write to [email protected].

Who can open it. Your app is live at https://<name>.pages.dev, where <name> is the name given to your site. It is public: anyone on the internet who has that address can open it, and no sign-in is needed to open it. Everything in the folder that was put live can be opened that way, so keep passwords and keys out of your app's files. Publishing is refused when a file holds something shaped like a secret key, such as a Stripe secret key or a GitHub token, but the platform cannot know what else you want kept private.

An app and a website differ. An app can sign people in and read and write vaults. A website cannot read or write vaults. Your AI publishes an app unless you say it is a website, and a name that was published as one kind cannot become the other.

Who sees the data. Your app keeps its data in vaults, not in a database of its own. 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. People sign in to your app with GilbPlatform, by a code sent to their e-mail, and your app then reads and writes in that person's vault. 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. So one user does not see another's data unless that person shares it, and you do not see what your app's users keep in their own vaults, unless they share it with you.

Your own vaults. A vault you own is reached only by those you give access. Whoever holds Control on a vault decides who else may read or write there; you hold it on a vault you made. Control gives no Read or Write by itself, but whoever holds it can give themselves Read or Write. Read lets the person read the vault. Write + Read lets them read it and also write to it. Append lets them add to the vault only, not read or change what is there. The answer How do I share a vault with a person? shows how to give access, and How do I see who can reach my vault? shows who has it.

What exactly is put live. Only the files in the one folder your AI builds your app into, such as dist, with index.html at its top: the pages, code, styles, pictures, fonts, sounds, videos, text files and PDF files a browser opens. When your app goes live, all its own files together may be at most 5 MB and 2000 files. Other kinds of file are refused, and so is a file whose name has no ending, such as a file named .env. Your vaults and their records are not put live: they stay in the vaults, and your app reads them there only for a person who may reach them. Nothing else on your computer is put live either, such as your plan or your notes, unless it is in that folder. But anything your AI copied into that folder, such as a list of names in a file, is put live with it, and anyone with the address can read it.

Checking that nothing secret is left. Before you say yes, you could ask your AI to list the files in that folder and to check that none holds a password, a key or personal data, such as names or e-mail addresses. Your AI can first make a trial run that sends nothing; it shows how many files and bytes would go live and each file it skipped, but it does not check for secrets. When your app is put live, the whole publish is refused if any file looks like it holds a secret key, as above; the message names the file and says Nothing was published. A password, names or e-mail addresses are not looked for. If something secret did go live, first change that password or key where it was made; then ask your AI to take it out and put the app live again, and write to [email protected]. Someone may already have seen it, and this help cannot say whether older copies are gone.

The answer Where does my app keep its data, and can I see it? shows how to look at your app's data. How a site goes live is in How do I put my app or website live on the internet?, and how to change it in How do I update my app after it is live?

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder (AskGoLive: it becomes public on the internet at that address), 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:463-486 (an address is admitted to sign people in and reach vaults only for kind app); src/server/cors.ts (vault doors answer only admitted addresses); workers/publish-ingest/src/checks.ts:30-40, :153-158 (key-shaped strings, such as a Stripe secret key or a GitHub token, refuse a publish); src/publish/records.ts:386-391 (a name cannot change kind). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): src/components/VaultAccessManager.tsx:932 (Write + Read), src/components/records/recordIcons.tsx:307-310 (Read, Append, Control). Live help pages: Can my app have its own users who sign in? (sign-in by e-mail code; each person sees only what they may reach; your app gets no more than the signed-in person can); Where does my app keep its data, and can I see it?; What can I make, and is there something I can't make? (a vault you own is reached only by those you give access); Can my app have different kinds of users, such as admins and members? (Control); How do I share a vault with a person? (the access levels); How do I put my app or website live on the internet? (two kinds of site). GilbPlatform 0fc5a548: src/publish/ticket.ts:20,31 (at most 2000 files and 5 MiB); workers/publish-ingest/src/checks.ts:11-15 (the file types taken), :98-102 and :149-151 (a name with no ending, such as .env, is refused), :30-40 and :153-158 (the key shapes looked for; Nothing was published.). Standard Rule_Code_deployment (RuleDeployPagesDev: a built static folder, for example dist; at most 2000 files and 5 MiB). Standard Proc_v_i_c_PublishPagesDev (step 5: the trial run makes no network call). Live help pages, sentences shared: How do I publish my app from the terminal? (the trial run prints the number of files and the bytes and each file it skipped, and does not run the secret scan); Do big pictures and videos make my app slow? (5 MB and 2000 files). https://myjackfruit.com/pricing/, read 14 November 2026 (Each person owns their vault, and many apps can work in it.).

Checked against GilbApp d529620.