Your form data, handled properly.
Form submissions are other people's personal data in your care. Here's exactly how FormWire stores, protects, and hands back every byte of it.
Six commitments you can hold us to.
Encrypted in transit
Every submission travels over HTTPS/TLS. The endpoint doesn't accept plaintext connections.
Encrypted at rest
Stored submissions are encrypted by our infrastructure providers before they touch disk.
Verified recipients only
The public access key in your HTML can only deliver to inboxes you've confirmed, so it can't be abused as an open relay.
Spam quarantined, not delivered
Honeypot and rate-limit catches are stored in a separate tab, never emailed, never counted against you.
Export or delete, any time
CSV export on every tier and the JSON read API on Pro; deletion is permanent and honored on request, per GDPR and CCPA.
Never sold, never shared
Submission data isn't sold, rented, or shared. It exists to reach your inbox and your dashboard — nothing else.
Security questions
The ones that come up in vendor reviews and DPA conversations.
No. It's public by design. The key is an alias for delivery to your verified inboxes only. It can't read data, change settings, or send mail anywhere else.
30 days of history on the free tier, 1 year on Pro. You can delete submissions or your whole account at any time, which removes the data permanently.
FormWire honors GDPR and CCPA rights: access, export, and erasure. Submission data is processed only to deliver and store your form submissions. Details are in the privacy policy.
Privacy policy →Yes. Pro plans add per-form domain rules, so submissions are only accepted from origins you allow, alongside reCAPTCHA and Turnstile.
Email support@formwire.com with the details. Reports go straight to the engineer who built the system, and good-faith research is always welcome.
Talk to the person who built it.
Security reviews, DPA questions, or anything this page didn't answer. Replies come from the engineer.