MyJackfruit

Help
Browse topics · Account, privacy and safety

Account, privacy and safety

← Account, privacy and safety

Where do I keep the passwords and keys for the services my app uses?

Short answer

Never in your app's code, a vault or a chat; GilbPlatform needs none, and an app live at pages.dev has no safe place for one.

Before you start

Words used here (1)
GilbPlatform
GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
Deeper

A key here is a secret text a service gives you so your app can use it, like a password for a program. Anyone who has it can use the service as you, often at your cost.

For an app that people sign in to, GilbPlatform needs no key from you. 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 token, a short-lived pass from their sign-in. A program with its own server can sign in as itself with a registered key; the Developer Guide says its private half stays in the server's secret store. Your app keeps no passwords either: people sign in with GilbPlatform, by a code sent to their e-mail.

Never in your app's code. The files of a web app are sent to every browser that opens it, so anyone could read a key in them. When your app is put live, GilbPlatform checks its files for text that looks like a key, such as a Stripe key or a Google API key, and refuses: "The file '…' looks like it contains … Nothing was published. Remove the secret from the file and publish again." The check finds only text shaped like a key; it does not prove that no key is there.

Never in a vault or a chat. A record can be read by everyone who may read its vault. What you type to your AI goes to your AI company; see Does my AI company see my data?

Where a key belongs. The Developer Guide, GilbPlatform's guide for people who build apps on it, says a private key belongs on a server, in the server's secret store, and that a page in a browser cannot keep one secret. An app put live at https://<name>.pages.dev, a web address of its own, has no server: it is only the files a browser loads, and a folder of server code is refused with a functions folder would run your code on the server. So an app made with these steps has no place for another service's key today. If your app needs a service that gives you a key, write to [email protected] before you sign up for that service.

If a key may have been seen by others, make a new one at the service that gave it and end the old one; that service's own pages say how.

Your app's own key for publishing is not one you handle: for an app, the connector keeps a key on the computer the app was published from, and the platform lets the app sign people in with that key.

This answer is written for a computer screen.

Source: Live help pages, sentences shared: What can I build on GilbPlatform? (There are no API keys and no shared secrets); Can my app have its own users who sign in? (no passwords); Does my AI company see my data?; How do I update my app after it is live? (the connector keeps a key on the computer the app was published from). Developer Guide Dev.Guide.AppAccess (Entry.Server: A page in a browser cannot do this.; EndUsers: Keep the private key in your server's secret store.), Agent.Coder.GilbStack item 14a (A browser-only app cannot do this: the key cannot stay secret there.). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:30-39 (key-shaped texts, among them a Stripe key and a Google API key), :158 (the refusal), :21 and :146 (functions folder refused). Standard RuleDeployPagesDev (a built static folder).

Checked against GilbApp d529620.