Control

Security & Encryption

AES-256-CBC + HMAC-SHA256 at rest Free & Pro

Security & Encryption: what it does

Most SMTP plugins store API keys and OAuth tokens in wp_options — readable by any plugin, any admin, any SQL dump. NimblyMail applies authenticated encryption (AES-256-CBC with HMAC-SHA256, Encrypt-then-MAC) to every credential, derives encryption keys from your WordPress salts, and lets you override any setting via PHP constants for true 12-factor deploys.

Security & EncryptionActive · configured via setup wizard
Enabled
Deliverability auditVerifies configuration weekly
Passing
Why it matters

What you get with Security & Encryption

Authenticated encryption

Encrypt-then-MAC on every API key and OAuth token — tampering is detected, not just hidden.

Salt-derived keys

Encryption keys derive from your WordPress salts; nothing secret ships in the plugin.

PHP-constant overrides

Define credentials in wp-config.php and keep secrets out of the database entirely.

Safe by default

Tokens never appear in logs, exports, or admin screens — the SMTP transcript redacts auth commands.

How it works

Three steps, zero babysitting

Enter credentials once

In wp-admin or as PHP constants — either way they're encrypted or never stored at all.

NimblyMail encrypts at rest

AES-256-CBC + HMAC-SHA256 with salt-derived keys, transparently.

Deploy with confidence

Database dumps, backups, and staging copies never expose usable credentials.

FAQ

Security & Encryption questions, answered

No. Every credential is encrypted with AES-256-CBC and authenticated with HMAC-SHA256 before it touches wp_options. For maximum hygiene, define credentials as PHP constants and they're never stored at all.