Documentation
Run encrypted Cornerstone Forms without changing the form builder.
These notes explain what the plugin protects, how to install it, how the license/update flow works, and what data never leaves the WordPress site.
Field-level encryption guide
What it means for Cornerstone Forms, when to use it, and what it does not replace.
Installation guide
Requirements, keys, activation, and first protected submission.
Buyer FAQ
Short answers on fit, licensing, updates, security boundaries, billing, tax, and support.
Trust center
Buyer review hub for product proof, data boundary, release notes, billing readiness, and support links.
Billing, VAT, and invoices
Stripe Checkout, tax ID collection, invoices, annual renewal, cancellation, and launch gates.
After checkout and updates
License key delivery, WordPress activation, private updates, expired-license behavior, and support recovery.
Staging rollout checklist
Field inventory, backups, key handling, batch encryption, rollback, and production acceptance checks.
Use cases
Where field-level encryption makes the strongest practical difference.
Compare approaches
Do nothing, hosting controls, hosted forms, custom code, or this plugin.
Security model
Encryption boundaries, license API data, backups, and limitations.
Data processing
Store data categories, subprocessors, DPA notes, and plugin data boundaries.
Changelog
Release 1.0.7, ZIP checksum, release verification, and update-channel behavior.
Compatibility
Supported WordPress, PHP, OpenSSL, Cornerstone controls, release artifact, and staging expectations.
Support
What to include in a support request without sending sensitive data.
EU withdrawal readiness
Prelaunch cancellation, refund, immediate digital access, and electronic withdrawal-flow status.
Buyer trust pack
The policy and proof pages live here, not on the sales page.
Use these pages when a buyer, agency client, accountant, or security reviewer needs the longer answer before checkout.
Use the docs before buying or deploying.
Start with the installation guide and security model. Then choose the plan that matches the number of production sites you will activate.