Privacy Policy
Last updated: 2026-10-30
This Privacy Policy explains how Menelabs O.E. ("BootForm", "we", "us") collects, uses, and protects information in connection with the BootForm service (bootform.com, app.bootform.com, api.bootform.com, and related subdomains).
Two kinds of data this policy covers
BootForm is a form-backend service: developers ("Customers", "you") point an HTML <form> at a BootForm endpoint, and BootForm accepts, stores, and delivers whatever the Customer's own form collects from their own site's visitors ("End Users"). This creates two distinct roles that matter for how each category of data is handled:
- Customer data - your account: email, name, authentication method, billing details, workspace and form configuration. Here, BootForm is the data controller - we decide why and how this data is processed, and this policy governs it directly.
- Form submission data - whatever an End User submits through a Customer's form. Here, the Customer is the data controller (they decide what their form asks for and what they do with the answers) and BootForm acts as a data processor, storing and delivering that data on the Customer's behalf and instructions. If you submitted a form built on BootForm and have a question about how your information is used, the right place to start is the website or organization whose form you filled in - they control that data, not us.
Information we collect
Account data (Customers)
- Identity: email address, optional display name.
- Authentication: a bcrypt password hash (never your plaintext password), or, if you sign in via GitHub/Google/Microsoft, the profile information that provider shares (email, name, avatar URL) with your authorization.
- Billing: plan tier, billing cycle, and usage - actual payment card details are handled entirely by our payment processor (Paddle, see below); we never see or store your card number.
- Configuration: forms, workspaces, notification destinations, API keys (stored hashed), team members you invite, and the settings you configure for each.
- Security/audit data: sign-in timestamps and IP addresses, for fraud prevention and account security (e.g. detecting suspicious login activity).
- Activity records: a log of actions taken on your account, such as creating or deleting a form, creating or revoking an API key, inviting a teammate, or changing your plan or password, with the time and the email of whoever did it ("BootForm system" or "BootForm support" for actions we or our staff take). Never submission content, and never a secret such as an API key or password.
Form submission data (on behalf of Customers)
- Whatever fields a Customer's form collects - entirely defined by the Customer, not BootForm.
- The submitting visitor's IP address, used for spam/abuse prevention and rate limiting.
- On a Customer's public feed, the IP address of a visitor who reacts to an item, kept for up to 90 days so the same visitor can't vote twice on it.
- Any file attachment a Customer's form is configured to accept.
What we don't collect
BootForm's own applications (the marketing site, dashboard, and admin panel) use no advertising trackers and no tracking cookies. The dashboard and admin panel use no analytics at all. The marketing site (bootform.com) counts page views with Umami, open-source analytics that we run on our own server, and, until we finish switching over, also with Cloudflare Web Analytics. Neither uses cookies or stores anything in your browser, and neither follows you across other websites. They tell us which pages are read and where visitors came from, not who you are: Umami doesn't store your IP address, and counts a visit by a one-way hash that changes every day. The dashboard stores your session token in your browser's local storage, not a cookie. We don't buy, sell, or rent personal data to anyone.
How we use information
To provide the service: accept submissions, apply your spam-protection settings, and deliver submissions to the destinations you've configured (email via our transactional email provider, and/or Discord, Slack, Telegram, or a webhook URL you've set up).
To operate your account: authentication, billing, plan enforcement, quota notifications.
To communicate with you, in two kinds of email:
- Service emails, which always go out because the service doesn't work properly without them: sign-in links, password resets, email verification, team invites, security notices, billing and quota warnings, delivery failures, and spam alerts about your forms.
- Onboarding emails: a short series in a new account's first two weeks that helps you get your first form working (a welcome, a reminder to verify your email, and a nudge when a step seems stuck). At most one a day, and each stops once you've done the step it's about. We send these to account holders on the basis of our legitimate interest in helping you use a product you signed up for. Every one of them has a link that turns them all off with one click, without signing in; you can also turn them off, or back on, on the Account page in the dashboard. If your mail app offers an "Unsubscribe" option that writes to us by email, that message reaches our support mailbox (the address under Contact) and a person turns them off for you.
We don't send newsletters, and we don't send marketing on behalf of anyone else.
To secure the service: detect and prevent abuse, fraud, and spam.
To provide support when you contact us.
Who we share data with
We use a small number of subprocessors to run BootForm. None of them are permitted to use your data for their own purposes.
| Subprocessor | Purpose | Data involved |
|---|---|---|
| Microsoft Azure | Hosting - database, file storage, message queues, compute (currently in the United States, East US region) | Account data, form submission data |
| Twilio SendGrid | Email delivery: service emails, onboarding emails, and submission notifications | Email address, email content, and whether an email was delivered, bounced, or reported as spam |
| Paddle.com Market Limited | Payment processing and billing (Merchant of Record) | Billing/plan data; card details are handled entirely by Paddle |
| GitHub / Google / Microsoft | OAuth sign-in, only if you choose to use it | Email, name, avatar (only what that provider shares with your authorization) |
| Discord / Slack / Telegram / a webhook URL you configure | Delivering form submissions where a Customer has chosen to send them | Form submission data, per the Customer's own configuration |
| Cloudflare | DNS for bootform.com; network proxy and TLS for BootForm's service subdomains (the form endpoint f.bootform.com, api., mcp., app. and the admin panel), with protection against abuse; page-view counts on the marketing site (bootform.com, Web Analytics) | Everything sent to those subdomains passes through it in transit, including form submissions and account data; for Web Analytics: page address, referring site, browser and device type, and approximate country, with no cookies |
Because Menelabs O.E. is based in the EU and our infrastructure provider (Microsoft Azure) is currently US-based, personal data may be transferred outside the EU/EEA. Microsoft is certified under, and BootForm relies on, the safeguards Microsoft provides for such transfers (including Standard Contractual Clauses). We do not currently offer EU-region-only data residency - if that matters for your use case, contact us before relying on BootForm for regulated data.
Data retention
Form submissions are retained according to the Customer's plan, in two stages: a full access window where a submission behaves normally, followed by a longer kept window where it remains in the account but is inaccessible unless the plan is upgraded, before being automatically and permanently deleted. See Submission retention for the full explanation of how the two stages work.
| Plan | Full access | Kept, then deleted |
|---|---|---|
| Free | 30 days | 6 months |
| Starter | 6 months | 1 year |
| Pro | 5 years | 7 years |
| Business | Unlimited | Never deleted |
Account data is retained for as long as the account is active. Activity records are kept for 12 months from the action, then deleted automatically.
If you delete your account from the dashboard, it is closed at once: you are signed out, your forms stop accepting submissions, nothing more is delivered or emailed to you (apart from one goodbye email), and your API keys stop working. Your account data, forms and submissions are kept, so that signing in again restores everything; submissions still expire on your plan's schedule above. They are erased for good only when you ask us to, as described under Your rights.
A submissions export file (CSV or JSON) can be downloaded for 7 days and is deleted a day after its link expires, so no export file is kept longer than 8 days.
When a form is deleted it disappears immediately, and its submissions, uploaded files and export files are removed in the background shortly afterwards. We keep only the form's ID, the ID of the account that owned it (cleared if that account is later deleted) and the date it was deleted, so that the ID can never be reused or claimed by someone else. This record holds no name, settings or submission content.
Your rights
Depending on your jurisdiction, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing.
- Individual submissions: delete any submission directly from the BootForm dashboard at any time.
- An entire form (and every submission it holds): delete the form directly from the dashboard; this removes all of its submissions, uploaded files and export files too, in the background shortly after the form disappears.
- Export: download your form's submissions as CSV or JSON directly from the dashboard.
- Your account: close it yourself from the Account page in the dashboard (see Deleting your account). To have your account data and everything in it erased for good, reply to the goodbye email you receive, or write to us through our contact form. We'll confirm once it's done.
- An End User's data: if you submitted a form built on BootForm and want that data deleted or corrected, contact the website/organization that owns the form - they're the data controller and can act on the request directly (including via the dashboard tools above). If you're unable to reach them, contact us and we'll assist where we reasonably can.
Cookies
BootForm's marketing site, dashboard, and admin panel do not use tracking or advertising cookies. The marketing site's page-view counting (Umami and Cloudflare Web Analytics) sets no cookies. The dashboard and admin apps authenticate using a token stored in your browser's local storage, not a cookie.
Children's privacy
BootForm is not directed at children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, contact us and we'll delete it.
Security
We use industry-standard practices to protect data in transit (TLS) and at rest, including hashed passwords (bcrypt) and hashed API keys/webhook secrets. No method of transmission or storage is 100% secure, and we can't guarantee absolute security.
Changes to this policy
We may update this policy as the service changes. Material changes will be reflected by updating the "Last updated" date above; continued use of BootForm after a change means you accept the updated policy.
Contact
Questions about this policy, or a request relating to your data: write to us through our contact form, or by email at 
.
Menelabs O.E.