MyJackfruit

Help
Browse topics · Servers and hosting (Server)

Servers and hosting (Server)

← Servers and hosting (Server)

How do I make sure my app is secure?

Short answer

No one can promise it is fully secure; GilbPlatform guards sign-in and access, and you ask Kai-Zen for security advice as you build.

Before you start

Words used here (2)
GilbPlatform
GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
Kai-Zen
Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper

Also asked:

How do I test that my app is safe before real people use it? Sign in to your app with another e-mail address and check that this person sees nothing of yours or anyone else's; check who can reach each vault and that none is public by mistake; ask your AI to check that no password, key or personal data is in its files.

Is my live app safe from hackers? No one can promise it. Its files are public, so nothing secret may be in them; the access each person holds keeps the data safe, so keep each access small and take it away from anyone who no longer needs it.

No one can promise that an app is fully secure, and no check finds every weak point. This answer is not security advice from a professional. It says what GilbPlatform, the service that keeps the vaults, does for every app, what your AI does, and what is left to you.

What GilbPlatform does for every app today. People sign in with a 6-digit code sent to their e-mail, so your app keeps no passwords. There are no API keys and no shared secrets, fixed strings a program would send to prove who it is: your app acts for a person with that person's sign-in. Each request an app sends carries the person's sign-in and a freshly signed proof, a one-use stamp that shows the request is new, and MyJackfruit says a proof used twice is refused (https://myjackfruit.com/your-vault/, read 13 November 2026). Your app gets no more than the signed-in person can: each person reaches only their own vault, the place where their records are kept, and what others have shared with them. A web address can sign people in from a browser only once it is approved; when Agent.Coder, the agent that writes your app's code, puts your app live, the platform lets that one address sign people in on its own. An app put live at https://<name>.pages.dev, the address GilbPlatform gives, may today reach only its own address and GilbPlatform's own addresses, may run only scripts from its own files, has no code of its own running on a server, and cannot use the camera, the microphone or the browser's location; GilbPlatform refuses to publish a file that looks like it holds a secret key. MyJackfruit's Privacy page says how the servers themselves are protected (https://myjackfruit.com/privacy/).

What GilbPlatform does not do for you. It does not check your app's own code for weak points; when an app is published it only refuses a file that looks like it holds a secret key. What your app shows and keeps on a person's device is up to your app. An app reads what people let it read, and MyJackfruit says a badly behaved app could keep a copy (https://myjackfruit.com/your-vault/). Who may read or write a vault of yours is what you give: Make public lets anyone read a vault. Give each person, and each AI, only the access they need.

What your AI does. After each increment, a part of the app built in one go, Agent.Coder starts Agent.Tester, a separate agent that knows nothing of how it was built, to test it; if it cannot start one, it tests the part itself and says so in its report. When a change touches a write, a grant (giving access) or a delete, Agent.Coder's standing instructions, the written procedure it follows, have it answer a written checklist for that change. Never put a password or a key in your app's code or in a vault: a page in a browser cannot keep it secret. If you are not sure, ask [email protected].

Security advice. Kai-Zen, the planning agent, can have the threats to your app named: who could do what harm, and how, with a goal for how well your app must hold against each one. The answer How do I get security advice for my app? shows how to ask. Agent.Hacker, the Kai-Zen security specialist, has a second job, checking a live system for weak points; its standing instructions let only a person start that job, with the system and the parts to test named, and its findings are advice only. No screen lets you start it today; that answer tells more.

What you do. Tell Kai-Zen early what in your app is private and who may see it. Try your app as the people who will use it, and say what surprised you. For anything that matters, such as payments, health data or data about children, have a security professional check your app before you rely on it. If you think data has leaked, see I think my app leaked data. What do I do?; who sees your app once it is live is in Who can see and use my app once it is live?

A last safety check before real people use it. This is advice; no list finds every weak point. Before you say yes to going live, you could: sign in to your app as someone who has never used it, with another e-mail address, and check that this person sees nothing of yours and nothing of anyone else's; see who can reach each vault your app uses, as How do I see who can reach my vault? shows, and take away any access that is not needed; check that no vault is public by mistake; and ask your AI to check that no password, key or personal data is in the files it will put live. Who can see and use my app once it is live? says what is put live. If Kai-Zen has not had the threats to your app named yet, ask now; How do I get security advice for my app? shows how.

Once it is live: is it safe from hackers? No one can promise it. Your app's files are public: anyone who has the address can read its pages and its code, so nothing secret may be in them. What keeps the data safe is the access each person holds, as above. GilbApp has no screen that reports who opened your app or what they tried, and GilbPlatform's own publishing rule says that handling misuse of published sites is not live yet. So keep each access as small as it can be, take access away from anyone who should no longer have it, as How do I take access away? shows, and have each change tested before it goes live, as Agent.Coder does. If you think something is wrong, see I think my app leaked data. What do I do?, and write to [email protected].

This answer is written for a computer screen.

Source: Live help pages, sentences shared: Can my app have its own users who sign in?; What can I build on GilbPlatform? (There are no API keys and no shared secrets); How does a browser app get the owner's approval?; How does my app's server read its own vault? (Do not pass the token or the private key to a page or a user.; A page in a browser cannot keep the private key secret); How do I know my app works? (Agent.Tester, separate); How do I get security advice for my app? (Agent.Architect names threats; Agent.Hacker eval only when a person starts it; no screen); Can my AI break or delete my data? How do I stay safe? (the lock is the access you give); How do I make a vault public?. Standards: Agent.Coder (AfterIncrement: Agent.Tester; Contextual: a change that touches a write, a grant, a revive or a delete answers Checklist_Code_gilb-create-door-sweep), Agent.Hacker (Eval: HumanAgent only), Proc_v_i_c_PublishPagesDev (step 8: the platform admits that origin on its own). MyJackfruit, read 13 November 2026: https://myjackfruit.com/your-vault/ (Security: A proof used twice is refused.; Not finished yet … a badly behaved app could keep a copy.), https://myjackfruit.com/privacy/ (How we protect the servers). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:21 (no server code), :30-37 (key-shaped strings refused), :124-140 (file limits), :169-171 (what a published app may load and reach). Standard Rule_Code_deployment (RuleDeployPagesDev). Standard Rule_Code_deployment (RuleDeployPagesDev: Not live yet: takedown and abuse handling.). GilbPlatform 0fc5a548: workers/publish-ingest/src/index.ts:11-14 and src/routes/publish.ts:42-45 (a published site is the builder's own files, served to anyone); no route that reports visits or attacks to a site's owner (src/routes/publish.ts has only ticket, precheck and admit). Agent.Coder (AfterIncrement: each increment tested before hand-back). Live help pages, sentences shared: What should I do in the first week after my app is live? (sign in as someone who has never used it); How do I see who can reach my vault?; How do I take access away?; Which e-mail address should I use, and can I change it later? (each address makes its own account).

Checked against GilbApp d529620.