Trust

Security

A widget lives on your website, so its security is your security. Here is what we do about it.

Last updated September 19, 2026

Widgets can never run code on your site

Every widget renders inside an isolated frame with its own origin. It cannot read your page, your cookies or your visitors' sessions. The widget itself is built only from a fixed set of approved components; there is no way for generated content to include scripts. Nothing you or a visitor types is ever executed.

Your data is yours

  • Responses are stored per account with database-level access rules, so one customer can never read another's data.
  • Data is encrypted in transit (TLS) and at rest.
  • You can export or delete responses at any time. Deleting a widget deletes its responses after a 30-day recovery window.

Responses are checked before they reach you

Every submission is filtered for spam and abuse before it appears in your inbox or is sent to your tools. Submissions are size-limited and rate-limited to protect against flooding.

Automations are sandboxed

Rules can only do what you configured: add a tag or send a copy of the response to a webhook you provided. A rule can never delete, edit, or send anything you did not set up, no matter what a visitor writes in the form.

Operations

  • Hosted on major cloud providers with independent security certifications.
  • Secrets are stored in the hosting platform's secret manager, never in code.
  • Background processing is durable: a failure retries rather than losing a response.
  • Error monitoring with sensitive fields scrubbed.
  • Least-privilege access for the team, with two-factor authentication.

Reporting a vulnerability

If you find a security issue, email security@widgev.com. We respond within two business days, will not take legal action against good-faith research, and credit reporters who want it. Please do not test against other customers' widgets or data.