Forms and what your site receives
A form is the one place a visitor sends something to your site — and the one place personal data from visitors lands.
Where a submission goes
The submission is stored on the server in an inbox the web server never serves: it cannot be reached by an address, only by a key with the inbox right. It is also forwarded to you by email, with the sender’s address as reply-to, so answering is a normal reply.
A submission has the same structured shape as the site’s content, so a review, registration or suggested event can be promoted to published content rather than retyped.
What protects it
The inbox sits outside the public folder and outside the site’s history: it is not part of the site’s history, because it is personal data. The inbox right is given sparingly, separate from every other right.
The form defends the door itself:
| Defence | What it does |
|---|---|
| Origin check | Accepts a submission only from your own site, not from a copy of the form elsewhere |
| Rate limit | Slows a flood of submissions from one address |
| Hidden field | People never see it; bots fill it in — most spam is caught without a puzzle |
A heavier bot defence at the network edge can be added if a site attracts it.
What is yours to decide
Which questions a form asks is a design decision in your templates — the engine knows no fields, so it collects nothing you did not ask for. How long submissions stay in the inbox is a retention decision only you can make; your privacy statement should mention it. “What do you hold on me” is looking in the inbox; “delete my data” is removing the file. See Privacy and GDPR.