lightsyncpro

tagteamdesign

<p>WordPress stores API keys in your database in plain text by default. If your database is compromised through SQL injection, a backup leak, or a vulnerable plugin, every API key is exposed. WordPress 7.0’s new Connectors API stores AI provider keys the same way (core ticket #64789).</p>
<p><strong>Syncific Vault fixes this.</strong> Your API keys are moved to an encrypted vault hosted off-site. Your WordPress database stores only a reference — the real key is injected at request time and never persists locally.</p>
<p><strong>One vault for all your AI plugins.</strong> Store your API keys in Syncific Vault — not in your database. Paste the secure placeholder into AI Engine, ClassifAI, Elementor AI, or any plugin that needs it. When you rotate a key with your provider, update it once in Syncific Vault — every plugin gets the new key instantly.</p>
<h4>How it works</h4>
<ol>
<li>Paste your API key in the Syncific Vault settings page</li>
<li>The key is encrypted and sent to the Syncific Vault (AES-256, never in your database)</li>
<li>A secure placeholder key is generated — paste it into your other plugins’ settings</li>
<li>When any plugin makes an API call, Syncific Vault intercepts it and injects the real key</li>
<li>Other plugins work normally — they don’t know the key was swapped</li>
<li>If your database is dumped or compromised, no API keys are exposed</li>
</ol>
<h4>Supports any AI API key</h4>
<ul>
<li><strong>AI providers:</strong> OpenAI, Anthropic, Google AI, OpenRouter</li>
<li><strong>Any API</strong> that uses header-based authentication (custom domain support included)</li>
</ul>
<h4>Security</h4>
<ul>
<li>Keys encrypted with AES-256 in an isolated vault file — not a database</li>
<li>Vault file stored outside the web root with strict file permissions</li>
<li>Patent-pending broker architecture (US App. No. 19/440,404)</li>
<li>Keys never stored in wp_options, wp_postmeta, or any WordPress table</li>
<li>In-memory key retrieval only — credentials are not persisted in any WordPress storage layer (database, transients, or options)</li>
<li>One-click key rotation — update a key once, every plugin gets the new key instantly</li>
<li>Rate-limited vault access (60 requests/minute per site)</li>
<li>Fails open by design — vault outages never break your WordPress site, though AI features dependent on protected keys will fail authentication until the vault is reachable again</li>
</ul>
<h4>Protects against</h4>
<ul>
<li>Database dumps and backup file exposure</li>
<li>SQL injection attacks</li>
<li>Compromised plugins that read wp_options</li>
<li>Unauthorized phpMyAdmin or database client access</li>
<li>Hosting provider data breaches</li>
</ul>
<h4>External Service</h4>
<p>This plugin relies on the <strong>Syncific Vault API</strong>, an external broker service operated by <a href="https://syncific.com" rel="nofollow ugc">Syncific</a>, to store and retrieve encrypted API keys. All requests are sent to the broker endpoint at <code>https://lightsyncpro.com/wp-json/lsp-broker/v1/</code> — the broker host that Syncific operates for this service.</p>
<p><strong>What the service does:</strong> Syncific Vault provides encrypted off-site storage for API keys. Keys are encrypted with AES-256 and stored in an isolated vault file on the Syncific broker server (<code>lightsyncpro.com</code>) — not in your WordPress database.</p>
<p><strong>What data is sent and when:</strong></p>
<ul>
<li><strong>When you store a key:</strong> Your site URL, a hash of your site URL, a per-site authentication token, a single-use verification nonce, the API domain, the API key, a label, and the authentication header name are sent to the broker (<code>lightsyncpro.com</code>) via HTTPS. The broker then calls your site back once at <code>/wp-json/svault/v1/verify</code> to confirm site ownership before binding the key.</li>
<li><strong>When a plugin makes an API call to a protected domain:</strong> Your site URL hash, per-site token, and the API domain are sent to the broker (<code>lightsyncpro.com</code>) to retrieve the real key. The key is held in PHP memory only for the duration of the request and is never written to your database.</li>
<li><strong>When you remove a key (or uninstall the plugin):</strong> Your site URL hash, per-site token, and the API domain are sent to the broker (<code>lightsyncpro.com</code>) to remove the key from the vault.</li>
</ul>
<p>No other user data, site content, or visitor information is ever transmitted.</p>
<p><strong>Service links:</strong></p>
<ul>
<li><a href="https://syncific.com/terms.html" rel="nofollow ugc">Syncific Terms of Service</a></li>
<li><a href="https://syncific.com/privacy.html" rel="nofollow ugc">Syncific Privacy Policy</a></li>
</ul>
<h4>Supported AI Providers</h4>
<p>Syncific Vault includes preset support for the following AI provider APIs. <strong>This plugin does not connect to these services directly.</strong> They are the destination domains whose API keys are protected by Vault. When another plugin on your site makes a request to one of these domains, Syncific Vault intercepts the request and injects the protected key. The traffic to these providers originates from your other plugins (such as AI Engine, ClassifAI, or any plugin you’ve configured), not from Syncific Vault itself.</p>
<ul>
<li><strong>OpenAI</strong> (api.openai.com) — <a href="https://openai.com/policies/terms-of-use" rel="nofollow ugc">Terms of Use</a> | <a href="https://openai.com/policies/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
<li><strong>Anthropic</strong> (api.anthropic.com) — <a href="https://www.anthropic.com/legal/consumer-terms" rel="nofollow ugc">Consumer Terms</a> | <a href="https://www.anthropic.com/legal/privacy" rel="nofollow ugc">Privacy Policy</a></li>
<li><strong>Google AI / Gemini</strong> (generativelanguage.googleapis.com) — <a href="https://ai.google.dev/gemini-api/terms" rel="nofollow ugc">API Terms</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
<li><strong>OpenRouter</strong> (openrouter.ai) — <a href="https://openrouter.ai/terms" rel="nofollow ugc">Terms</a> | <a href="https://openrouter.ai/privacy" rel="nofollow ugc">Privacy</a></li>
</ul>
<p>You may also add any other domain through the “Add Custom Domain” option in the plugin settings. Whatever domain you add becomes a protected destination — your other plugins continue to send requests to that domain as they normally would, and Syncific Vault transparently provides the credentials.</p>
<h4>Free and open source</h4>
<p>Syncific Vault is completely free. No limits on the number of keys you can protect.</p>
<h4>Made by Syncific</h4>
<p>Syncific Vault is built by the team behind <a href="https://syncific.com" rel="nofollow ugc">Syncific</a> — the creative asset sync platform. The same patent-pending broker architecture that protects OAuth credentials for Lightroom, Figma, Canva, and Dropbox now protects your API keys.</p>


Syncific Vault — API Key Protection & Security

Encrypt your AI API keys and keep them out of the WordPress database — one secure vault for WordPress 7.0 Connectors and every AI plugin.

miya

<p>Kagivault is an encrypted vault for the <strong>WordPress 7.0 AI Connectors API</strong>. Out of the box, WordPress stores the API keys you configure on <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Connectors</strong> (OpenAI, Anthropic, Google, OpenRouter, and any other AI provider registered with the AI Client) as plaintext rows in the <code>wp_options</code> table. Anyone with database access — backups, leaked dumps, host migration files — can read them.</p>
<p>Kagivault wraps each AI Connectors key with <strong>XChaCha20-Poly1305 (authenticated encryption)</strong> and protects the data-encryption key with a <strong>vault password derived through Argon2id</strong>. The vault password is never persisted, and the vault automatically re-locks after a short, configurable idle timeout. Unlock from the admin UI, and the WordPress AI client transparently sees the decrypted keys — no other plugin changes required.</p>
<h4>Highlights</h4>
<ul>
<li>Drop-in encryption for every AI Connectors provider (<code>connectors_ai_*_api_key</code> rows)</li>
<li>Vault password unlock with idle-timeout auto-lock</li>
<li>Recovery key as a parallel unlock path</li>
<li>Optional: link a WordPress login password so signing in automatically unlocks the vault</li>
<li>Easy-mode initialization — no separate vault password to remember if you just want one-click setup</li>
<li>Transparent for the core WP AI client and the Connectors admin page</li>
<li>Versioned blob format for future cipher upgrades</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 7.0 or newer (uses the Connectors API introduced in 7.0)</li>
<li>PHP 8.3 or newer</li>
<li>PHP sodium extension with <strong>XChaCha20-Poly1305 AEAD</strong> (<code>sodium_crypto_aead_xchacha20poly1305_ietf_encrypt</code>)</li>
<li>PHP sodium extension with <strong>Argon2id</strong> (<code>SODIUM_CRYPTO_PWHASH_ALG_ARGON2ID13</code>, requires libsodium 1.0.13+)</li>
</ul>
<p>The bundled sodium extension shipped with PHP 8.3+ on most platforms (Debian/Ubuntu <code>php-sodium</code>, RHEL <code>php-sodium</code>, Alpine <code>php-sodium</code>, Windows official builds) includes both capabilities. The plugin refuses to activate and surfaces a clear admin notice if either is unavailable.</p>
<h3>Privacy Policy</h3>
<p>Kagivault does NOT:</p>
<ul>
<li>Send any data to external servers</li>
<li>Track users</li>
<li>Use cookies for tracking</li>
<li>Share data with third parties</li>
</ul>
<p>Kagivault DOES:</p>
<ul>
<li>Process and store encrypted API keys locally on your server (<code>wp_options</code>)</li>
<li>Keep the data-encryption key only in a short-lived transient that expires after the configured idle timeout</li>
</ul>
<h3>Support</h3>
<p>For support, bug reports, or feature requests:</p>
<ul>
<li>Website: https://github.com/benridane/kagivault</li>
</ul>
<h3>Development</h3>
<p>Development happens on GitHub. Pull requests welcome!</p>
<ul>
<li>Follow WordPress coding standards</li>
<li>All code must pass <code>wp plugin check kagivault</code></li>
</ul>


Kagivault

Encrypts WordPress AI Connectors API keys (OpenAI, Anthropic, Google, OpenRouter) at rest with XChaCha20-Poly1305 + Argon2id.

Syncific Vault — API Key Protection & Security vs Kagivault