Your responses are encrypted before submission.

Cyphorm is a zero-knowledge encrypted form builder. Response contents are encrypted in the respondent's browser before submission; the service stores ciphertext and form metadata.

The owner's private key is not sent to the server through the intended application flow. This protects stored responses from passive database access; it does not protect against browser code that has been compromised or deliberately changed.

Explore encrypted forms · Understand the zero-knowledge model

Cyphorm encrypted form builder — ciphertext-only storage visualization

How Response Encryption Works

TLS and encryption at rest protect important parts of an online service. Client-side encryption adds a different property: the form provider does not receive the private key needed to decrypt stored response contents.

1. Local Generation

Your browser generates an RSA keypair. The private key is protected in browser storage and is not sent to Cyphorm through the intended application flow.

2. E2E Encryption

When a respondent submits a form, the browser encrypts the response with your public key before the response contents leave the browser.

3. Zero Knowledge

The server stores encrypted response fields and operational metadata. Stored response data alone cannot be decrypted by the server. The browser must still trust the application code served by this site.

Interactive, client-side demo

See How Encryption Works

Type harmless sample values. Your browser encrypts them locally with Cyphorm’s response encryption function.

Do not enter real personal or confidential information. This demonstration uses a temporary key generated in this tab, not your account key.

1 · Plaintext in this browser

The sample stays in this page. There is no submit button or server request.

2 · Encrypted locally

Enter a sample value to create an encrypted payload in your browser.

The encrypted payload will appear here.

3 · What the response sends

The normal encrypted response contains an AES-GCM ciphertext, an RSA-wrapped AES key, and an initialization vector. The form service also handles the form schema and operational metadata such as timestamps and counters where applicable.

This demo uses the production CyphormCrypto.encryptResponse function but does not transmit or store its result. The temporary private key is not saved or sent, and it is unrelated to your account key.

Who Uses Cyphorm?

For teams evaluating confidentiality in client, healthcare, employee, and reporting workflows.

Learn more about zero-knowledge forms or compare Google Forms' encryption properties.