Data Privacy and Security for Online Forms: A Practical Checklist

A secure online form collects only the data it needs, sends it over HTTPS, keeps it out of URLs, and stores it where only the right people can see it, for no longer than necessary. Most form data problems don't come from hackers breaking encryption. They come from asking for too much, sharing responses too widely (a public spreadsheet, a busy Slack channel, a forwarded email), and keeping everything forever. This checklist covers both sides: choosing a secure form builder and running your forms safely day to day.
Step 1: Decide how sensitive your data is
Start by sorting what you plan to collect. The level of protection you need, and the kind of tool you should use, follows from this.
| Sensitivity | Examples | What it usually needs |
|---|---|---|
| Low | Event RSVPs, product feedback without names, poll votes | HTTPS, sensible sharing of results |
| Medium | Names, emails, phone numbers, addresses, job applications, client intake details | Everything above, plus access control, a privacy notice, consent where needed, a retention plan |
| High | Health information, government ID numbers, bank or card details, passwords, information about children, legal or HR investigations | Everything above, plus a vendor that meets the specific legal requirements (for example, a signed BAA for US health data) and stronger controls. Often a specialist tool. |
If something on your form sits in the "high" row, ask first whether the form needs it at all. Often the answer is no: you can collect a phone number and handle the sensitive part on a call, or link to a dedicated secure portal.
Step 2: Collect less
The data you never collect can't leak. Data minimisation is also a legal principle in many privacy laws; the GDPR, for example, requires personal data to be "adequate, relevant and limited to what is necessary" for its purpose.
- Remove fields "we might use later". Every field should have a clear use.
- Prefer ranges to exact values (age band rather than date of birth, budget range rather than income).
- Make sensitive questions optional and add "Prefer not to say".
- Don't ask for anything in free text that you wouldn't ask for in a dedicated field. If people might type sensitive details into a comments box, add a note asking them not to.
- For feedback that doesn't need follow-up, skip names and emails entirely. See how to create an anonymous survey.
Step 3: Build the form securely
Serve everything over HTTPS. The form itself and the page it's embedded on should both use HTTPS. Browsers warn visitors on non-secure pages, and data sent over plain HTTP can be read in transit.
Keep personal data out of URLs. Pre-filling a form through link parameters such as ?email=jane@example.com is convenient, but URLs end up in browser history, server logs, analytics tools and referrer headers. OWASP lists this as a known information exposure risk. Use URL parameters for non-personal values like a campaign name, or an opaque ID that means nothing on its own.
Never collect passwords or full card numbers in a form. Card data belongs with a payment processor that is built for it. Send people to the processor's payment page instead.
Be careful with file uploads. IDs, medical records and bank statements are easy to request and hard to protect. Ask for uploads only when you need them, say which files you accept, and delete them once they've served their purpose.
Write a clear privacy notice. On the form, say what you collect, why, who will see it, how long you'll keep it and how to ask for deletion. Link your full privacy policy.
Ask for consent properly. Use an unticked option or a yes/no question for marketing consent, separate from agreeing to terms.
Close forms you no longer need. An old form that is still open keeps collecting data nobody is watching. Set a close date or a response limit when you publish.
Protect against spam and abuse. Check what bot and spam protection your form builder provides, and keep an eye on unusual spikes in submissions.
Step 4: Protect responses after they arrive
This is where most real-world exposure happens.
Secure the accounts. Everyone with access to your form builder should use a strong, unique password and a password manager, plus two-factor authentication wherever the tool and the connected accounts (Google, Slack, email) offer it.
Limit who can see responses. Only add teammates who need the data. Remove people when they change roles or leave.
Treat every integration as a copy of the data. Each one creates another place your data lives, with its own access rules:
- Spreadsheets: check the sharing settings of any connected Google Sheet. "Anyone with the link" on a sheet of client details is a common leak.
- Chat: posting each response to a channel shows it to everyone in that channel, including future members. Use a private channel for anything personal, or post a short alert without the full response.
- Email notifications: responses in email get forwarded, synced to phones and kept for years. Avoid emailing sensitive submissions in full.
- Webhooks: make sure the receiving URL uses HTTPS and that the endpoint checks requests come from where it expects, for example with a secret token, so nobody else can post fake data to it.
- Automation tools: in Zapier, Make, n8n and similar tools, check who on your team can see run history, since it often contains full response data.
Watch your exports. CSV files on laptops and in download folders are easy to lose. Export only when you need to, store files in a controlled location and delete local copies.
Set a retention period and stick to it. Decide how long each form's responses are needed (for example, delete unsuccessful job applications after a set number of months) and delete on schedule. The GDPR calls this storage limitation.
Have a plan for requests and incidents. Know how you'd find and delete one person's data if they ask, and who you'd notify if responses were exposed.
Is it safe to embed a third-party form on your website?
Generally yes, if the form provider is reputable and both pages use HTTPS. When you embed a form with an iframe, respondents' answers go straight to the form provider, not through your web server. That has two consequences:
- The provider becomes a processor of your visitors' data, so its security matters as much as yours. Use the vendor questions below.
- Your privacy policy should say that you use a third-party form service to collect this data.
Questions to ask any form builder about security
A secure online form builder should be able to answer these clearly, ideally on a public security or trust page.
| Question | Why it matters |
|---|---|
| Is all traffic encrypted with HTTPS/TLS? | Protects data in transit; this should be a baseline |
| Is stored data encrypted at rest? | Limits damage if storage is accessed improperly |
| Where is the data hosted, and can I choose a region? | Some organizations or laws require data to stay in a certain country |
| Which independent audits or certifications do you have (for example SOC 2, ISO 27001)? | Shows controls have been checked by a third party |
| Will you sign a data processing agreement (DPA)? | Often needed under the GDPR when a vendor processes personal data for you |
| Will you sign a business associate agreement (BAA)? | Required for US healthcare providers handling protected health information |
| Who are your subprocessors? | Your data may also pass through hosting, email and analytics providers |
| Can I delete individual responses and whole forms? | Needed for deletion requests and retention |
| How are team access and roles managed? | Determines who can see what |
| Do you support two-factor sign-in? | Protects against stolen passwords |
| How and when do you notify customers of a breach? | Affects your own obligations |
Be wary of vague claims ("bank-level security", "fully compliant") with no specifics behind them.
Regulated data: health, financial and children's data
Health data in the US. If you are a HIPAA covered entity, or work for one, the vendor that stores your forms' protected health information must sign a business associate agreement. The US Department of Health and Human Services explains that covered entities need satisfactory written assurances from business associates before sharing that data. Choose a form tool that offers a BAA for patient intake and medical history forms. FlowyForm does not offer HIPAA compliance or a BAA, so it isn't the right tool for collecting protected health information.
Financial details. Loan applications, credit checks and account openings often involve government ID numbers, income documents and bank details. Use a platform built for regulated financial onboarding, or collect only basic contact and inquiry details in a general form and move the sensitive steps to a secure portal or a call.
Payments. Don't collect card numbers in form fields. Use a payment processor's hosted checkout, and send people there after the form if needed.
Children's data. Forms aimed at children, or collecting data about them (camps, schools, sports clubs), are subject to extra rules in many countries. Collect the minimum, address the form to a parent or guardian, and check local requirements.
None of this is legal advice. If you're unsure what applies to you, ask a privacy professional.
Privacy by design for forms
Privacy by Design is a framework developed by Ann Cavoukian, former Information and Privacy Commissioner of Ontario, built on seven foundational principles. The GDPR includes a related requirement for data protection by design and by default. Applied to forms, the principles become practical habits:
| Principle | What it means for a form |
|---|---|
| Proactive, not reactive | Review each new form for privacy before it goes live, not after a complaint |
| Privacy as the default | Optional fields, unticked consent and no hidden tracking unless the person opts in |
| Privacy embedded into design | Minimal fields and sensible retention are part of the form template, not an afterthought |
| Full functionality | You can still personalize and segment, using what people choose to tell you |
| End-to-end security | Protect data from submission through every integration to deletion |
| Visibility and transparency | Tell people on the form what you collect and why |
| Respect for user privacy | Make it easy to say no, to stay anonymous where possible and to ask for deletion |
For marketers, this pushes toward collecting what people knowingly tell you (their interests, needs and preferences, sometimes called zero-party data) instead of inferring it from tracking. Ask for consent at the moment it's relevant rather than in one large wall of terms, and show people the benefit of sharing: if you ask about their goals, use the answer to tailor what they see next. A short quiz or preference question that leads to a useful recommendation is a fair exchange that people understand.
What FlowyForm does and doesn't do
To be specific about our own product:
- Forms and responses are hosted by FlowyForm, and data is sent over HTTPS.
- You decide exactly which questions to ask, and you can delete responses.
- You can close a form manually, at a set date and time, or after a number of responses.
- Google Sheets, Slack and webhook integrations only send responses where you connect them, so you control every copy.
- On Premium, workspaces let you share forms with up to 10 members per workspace, so you can separate teams and keep access limited.
- You can serve forms on your own domain on Premium.
FlowyForm does not offer HIPAA compliance or a BAA, and we don't claim SOC 2 certification, end-to-end encryption or a choice of data region. If your project requires any of those, choose a vendor that provides them in writing.
Good fits for FlowyForm are forms with low or medium sensitivity: feedback, registrations, lead capture, applications and intake forms that don't involve regulated data. Useful starting points are the consent form template, the client intake form template and the job application form template. For webhook setup, see how to use webhooks in FlowyForm, and for collecting less from the start, our guide to data capture forms.
Quick checklist
- Every field has a clear purpose; nothing "just in case"
- Sensitive questions are optional or removed
- No personal data in form URLs or hidden fields
- Form and host page use HTTPS
- Privacy notice on the form; consent unticked and separate
- No card numbers or passwords collected
- Form closes on a date or response limit
- Accounts use strong unique passwords and two-factor where available
- Only people who need responses can see them
- Connected sheets, channels and inboxes checked for who can see them
- Webhook endpoints use HTTPS and verify requests
- Retention period set and old responses deleted
- Vendor checked against your sensitivity level (DPA, BAA, certifications as needed)
FAQ
Are online forms secure?
They can be. A form served over HTTPS protects data in transit, and a reputable form builder protects stored data. Most risk comes from what you collect and how widely you share responses afterward, so minimizing fields and controlling access matter as much as the tool.
What makes a form builder secure?
HTTPS everywhere, encrypted storage, clear access controls, the ability to delete data, two-factor sign-in and, for regulated data, the right agreements and audits (such as a DPA, a BAA or SOC 2). A good vendor documents these publicly.
Is FlowyForm HIPAA compliant?
No. FlowyForm doesn't offer HIPAA compliance or sign business associate agreements, so don't use it to collect protected health information. Use a vendor that will sign a BAA for that.
Can I collect credit card details in an online form?
You shouldn't type card numbers into regular form fields. Use a payment processor's checkout. In FlowyForm, Premium ending redirects can send people to a payment link after they finish the form.
How long should I keep form responses?
Only as long as you need them for the purpose you collected them for, plus any legal retention period that applies. Set a period for each form and delete responses on schedule.
Do I need a privacy policy for my forms?
If you collect personal data, you almost always need to tell people how you use it. Put a short notice on the form and link to your full privacy policy.
What is the safest way to collect sensitive information?
Collect as little as possible, use a tool designed and certified for that type of data, limit access to a small group, avoid copying it into email and chat, and delete it when you're done.