# Can my website have a contact form?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Only in an app, not a website: a signed-in person you gave "Append" or "Write + Read" can leave a message; strangers cannot.

## Deeper

A contact form is a few boxes on a page, such as name, e-mail and message, and a button that sends them to you.

What GilbPlatform does today. GilbPlatform, the service that keeps your vaults, has no ready-made contact form. GilbPlatform sends its own e-mails, such as the sign-in code, but it has no part your app can use to send e-mails or text messages. An app built on GilbPlatform saves what people type as records in vaults. A vault is the place where a person or a group keeps their records; a record is one piece of data with its own address.

What is blocked today. When your app goes live, it is put on the internet at https://&lt;name\>.pages.dev, a web address of its own, as only the files a browser loads: no code of your app runs on a server there; a server is a computer on the internet that runs a program's code for it. GilbPlatform sets the rules that address serves your app with, and you cannot change them: the app's pages may fetch data only from the app's own address and from GilbPlatform's own addresses, such as id.gilb.com or a vault's address. Pictures may also come from those two places; scripts, videos, sounds and everything else come only from the app's own files. The same rules stop it showing another site inside its pages, and a form in it can send only to its own address. So a form that sends to an outside form service or e-mail service does not work in your published app today. If you need this, write to support@gilb.com.

What your AI coder can build. Agent.Coder, the agent that writes your app's code, can build a form that saves each message as a record. Saving needs a signed-in person who may write in that vault: people sign in to your app with GilbPlatform by a code sent to their e-mail. Each person sees only what they may reach: their own vault, and what others have shared with them. So a message reaches a vault of yours only from [people you gave access to](http://support.gilb.com/help/how-do-i-share-a-vault-with-a-person). "Append" lets a person add to the vault only, not read or change what is there. "Make public" lets anyone read a vault, signed in or not, but nobody can be given writing that way. So "Append" suits a form for people you know, such as a club's members; they cannot read that vault, not even what they wrote themselves. A stranger cannot leave a message in your vault unless they hold "Append" or "Write + Read" there; anyone holding "Control" on the vault can give that access, including to themselves. Ask Kai-Zen, the planning agent, how your plan gives people access; whether you want it is your choice. This works only in a published app that people sign in to: a published website that signs no one in cannot read or write in vaults, because GilbPlatform answers the pages of an app, not of a website.

Reading the messages. You see them in GilbApp: press "Main menu", the button at the top left that shows the name of the section you are in, choose "Records", and search and select a message; the answer [How do I find a record?](http://support.gilb.com/help/how-do-i-find-a-record) shows how. You can also ask Jackfruit, the vault agent in GilbApp's chat, to list them; the answer [How do I work with Jackfruit?](http://support.gilb.com/help/how-do-i-work-with-jackfruit) shows how. Nothing tells you when a new message arrives: GilbPlatform sends no e-mail or notice; see [Can I be told when someone signs up or orders?](http://support.gilb.com/help/can-i-be-told-when-someone-signs-up-or-orders)

What still works. A plain e-mail link, which needs no sign-in. MDN, the web's reference for people who make web pages, says such links "open in the user's email program to let them send a new message" \(https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/a, read 13 November 2026\). Your e-mail address is then shown on your page, for anyone to read. The security rules for published sites do not block a plain link that opens another site. The same holds for a link to a form service's own page; the form then runs on that service's page, under your own account with it, its terms and its costs.

What people write, such as their name and e-mail address, is personal data about them; rules such as GDPR, the European Union's law on personal data, may apply. This help gives no legal advice; see [Do I have to follow rules such as GDPR or app store rules from the start?](http://support.gilb.com/help/do-i-have-to-follow-rules-such-as-gdpr-or-app-store-rules-from-the-start) The answer [Do I need a privacy page and a cookie banner?](http://support.gilb.com/help/do-i-need-a-privacy-page-and-a-cookie-banner) says more.

The answer [Can my app send e-mails, such as a welcome e-mail or an order confirmation?](http://support.gilb.com/help/can-my-app-send-emails-such-as-a-welcome-email-or-an-order-confirmation) says more about e-mail.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 \(https://id.gilb.com/version, read 13 November 2026\): workers/publish-ingest/src/checks.ts:21 and :146 \(a functions folder refused: "a functions folder would run your code on the server"\), :165-172 \(the headers every published site gets: Content-Security-Policy default-src 'self'; script-src 'self'; img-src 'self' data: blob: https://\*.gilb.com; connect-src 'self' https://\*.gilb.com; form-action 'self'; Permissions-Policy camera=\(\), microphone=\(\), geolocation=\(\)\). MDN, frame-src \(falls back to child-src, then default-src\), https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/frame-src, read 13 November 2026. GilbPlatform 0fc5a548: no e-mail-sending or timed-job route for apps in src/routes \(e-mail is sent only for sign-in codes, src/auth/send-otc-email.ts, and the owner's monitor alerts\). GilbPlatform 0fc5a548: no contact-form route. MDN, &lt;a\>: The Anchor element \(mailto: links\), https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/a, read 13 November 2026. Live help pages: Can people upload files, pictures and their own text in my app?; Can my app have its own users who sign in? \(each person sees only what they may reach\); How do I keep my app safe from spam and fake sign-ups? \("Append"; "Make public": nobody can be given writing that way\); Who can give access, and to whom?; How do I find a record?; How do I work with Jackfruit?; Will I be told when something is ready for me to look at? \(GilbPlatform sends no e-mail or notice\); Can my app connect to other services, such as weather, shipping, maps or calendars? \(plain link\); Can my app send a reminder before a booking? \(no e-mail part for apps\).
