Security model

Encryption is local. Licensing is remote.

Data that stays on WordPress

• Form submissions and encrypted field values.
• Uploaded files and encrypted upload payloads.
• Encryption keys and search keys.
• Audit logs and decrypt activity records.
• WordPress user passwords, cookies, and private customer documents.

Data sent to the license API

• License key during activation/checks.
• Normalized site URL/domain and hashed site identifier.
• Plugin version, WordPress version, PHP version, and product slug.
• Plan/status data needed to gate updates and private ZIP downloads.

What the plugin helps with

It reduces the blast radius of stored form data by encrypting selected fields at rest and limiting who can read them in wp-admin. It also helps prevent accidental exposure of sensitive uploads through ordinary media URLs.

What it does not replace

It is not a full compliance program, hosting hardening, access-control policy, backup policy, legal review, or incident-response plan. Your site still needs least-privilege admin access, protected backups, patched plugins/themes, HTTPS, and operational controls.