Can Cyphorm read my form submissions?

No. Your private key never leaves your browser. We store only ciphertext—there is no key on our servers that can decrypt your respondents' answers.

What if I lose my private key?

Encrypted responses cannot be recovered without your key. Cyphorm supports printable QR backups and password-manager export so you can keep redundant copies safely offline.

Is Cyphorm HIPAA compliant?

Cyphorm is designed so we cannot access submission contents, which supports many compliance goals. HIPAA compliance for your organization still depends on your configuration, agreements, and processes—we do not claim a one-size-fits-all HIPAA certification.

How is this different from password-based encrypted forms?

When a provider encrypts with a shared password they choose or derive, their software can often decrypt submissions because the secret is not exclusively yours. Cyphorm uses an RSA keypair generated in your browser; we never receive the private key.

Not even we can read your submissions.

Cyphorm™ is the world's most secure form builder. Every submission is end-to-end encrypted in the browser using the Web Crypto API. We store ciphertext only. You hold the only key.

Try Cyphorm™ How it works

Why Client-Side Crypto Matters

Other secure form builders manage your encryption keys for you. This means they can read your data if subpoenaed or hacked. We can't.

1. Local Generation

When you create an account, your browser generates a 4096-bit RSA keypair. The private key never leaves your device.

2. E2E Encryption

When a respondent submits a form, the data is encrypted using your public key before it hits the network.

3. Zero Knowledge

Cyphorm™'s database receives mathematical garbage. Only you can decrypt it on your dashboard.

See It In Action

Here's exactly what happens when someone fills out a Cyphorm™ form.

① What the respondent sees

Job Application

Full Name *

Email *

Cover Letter

I am excited to apply for this role...

🔒 End-to-End Encrypted by Cyphorm™

Before the data leaves the browser, JavaScript encrypts it using the form owner's public key. The plaintext never touches the network.

② What Cyphorm™'s database stores

-- encrypted_responses table

encrypted_payload:
7GpLmX3kR9wQzN1vBs8TdYeKfJhCnOuA4iW6xP2yVqEaImZ0bHlcDgRtMFsUjp+kL9XnQ3YwCzA1vBe8TdKfJhOpNm7GsLrX4iW2xPqEaZ0bHlcVgRtM...

encrypted_key:
X9mKpL3rQzN7vBs1TdYeGfJhCnOuA4iW6xP2yVqEaImZ0bHlcDg...

iv:
aBcDeFgHiJkL==

submitted_at:
2026-03-22 15:04:12

This is the literal content of the database row. There is no name, no email, no cover letter — only ciphertext that is mathematically meaningless without the private key.

③ Why we can't read it — ever

Your password

Stored as a one-way bcrypt hash. We cannot reverse it. Even if we wanted to, we don't know what you typed.

Your private key

Never sent to our servers. It lives only in your browser's storage, wrapped with a key derived from your password.

The encrypted data

Decryptable only with the private key, which only you have. A court order against us yields nothing readable.

The chain of custody

Password → derives key → unlocks private key → decrypts data. We are not in this chain at any step.

This isn't a privacy policy promise. It's a mathematical guarantee enforced by your browser.

View Features & Pricing

Who Uses Cyphorm?

Teams that need real confidentiality—not just a lock icon in the browser bar.

Law Firms Healthcare Whistleblowers HR Teams Client Intake

Learn more about zero-knowledge forms or see a private alternative to Google Forms.