CF Cornerstone Forms Encryption Buy License

Use cases

Protect the forms where plaintext storage creates the most risk.

The plugin is intentionally narrow: Cornerstone Forms, selected fields, local encryption, private updates. Use it where the value is in reducing exposure of stored submissions without rebuilding the form workflow.

Client intake Names, contact details, private notes, attached documents, and case context that should not sit readable in post meta.
Legal requests Pre-consultation forms, sensitive descriptions, supporting files, and internal access review through audit logs.
HR applications Candidate details, screening answers, private attachments, and limited decrypt access for the hiring team.
Support cases Customer messages that include account details, private documents, or operational notes that only a smaller team should read.
Member or client portals User-owned mode can narrow access so users see only submissions associated with them.
Private uploads Uploads referenced by protected fields can be encrypted and served through permission-checked download URLs.

What to encrypt first

Start with fields that create the highest exposure if a database export, admin account, backup, or support copy is mishandled. Typical first choices are private notes, detailed descriptions, ID/reference numbers, attached documents, and contact details that do not need to feed a reporting dashboard.

Encrypt private messages, case descriptions, internal notes, sensitive identifiers, and uploaded documents tied to those fields.
Leave plain when needed routing fields, public preferences, consent flags, and operational values that integrations must read immediately.
Use delayed encryption when a payment, CRM, or email feed needs plaintext briefly before the value is protected at rest.
Use blind search when staff must find exact matches without storing a searchable plaintext copy of the field value.

Good buyer fit

  • You already use Cornerstone Forms and want to keep that builder.
  • You need selected stored values protected, not every field encrypted.
  • You want encryption to happen inside WordPress instead of sending forms to another intake platform.
  • You can manage and back up a site-level encryption key responsibly.
  • You understand that license expiry should stop updates, not break installed encryption.

When not to use it

Do not use field encryption as a substitute for access control, backups, patching, consent notices, or a full compliance program. It is a focused storage-protection layer for selected fields, not a replacement for site governance.

Ready to map your forms?

Review the installation guide, compare the alternatives, then choose the license tier that matches the number of sites you maintain.

See pricing Installation guide Compare approaches