| 开发者 |
lightsyncpro
tagteamdesign |
|---|---|
| 更新时间 | 2026年6月2日 00:08 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
https://lightsyncpro.com/wp-json/lsp-broker/v1/ — the broker host that Syncific operates for this service.
What the service does: 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 (lightsyncpro.com) — not in your WordPress database.
What data is sent and when:
lightsyncpro.com) via HTTPS. The broker then calls your site back once at /wp-json/svault/v1/verify to confirm site ownership before binding the key.lightsyncpro.com) 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.lightsyncpro.com) to remove the key from the vault.syncific-vault folder to /wp-content/plugins/Your keys are encrypted with AES-256 and stored in an isolated vault file on the Syncific broker server. The vault file is not a database — it's an encrypted file on disk with strict permissions (0600). The encryption key is separate from the vault file. Your WordPress database never contains your real API keys.
Encryption-in-database plugins still leave the encrypted keys and the encryption key on your WordPress server. If an attacker gains access through SQL injection, a backup leak, or a vulnerable plugin, they can extract both the encrypted keys and the means to decrypt them. Syncific Vault is architecturally different: the keys aren't on your WordPress server at all. There's nothing to decrypt because there's nothing there.
Yes. Syncific Vault uses WordPress's http_request_args filter to intercept outgoing API calls and inject the real key before the request is sent. The calling plugin (AI Engine, ClassifAI, Elementor AI, WooCommerce, etc.) works exactly as before — it doesn't know the key was swapped.
Click "Rotate Key" next to any protected key in the Syncific Vault settings page, paste your new key, and you're done. Every plugin on your site that uses that key gets the new one instantly — no need to update settings in each individual plugin.
The plugin fails open — it never blocks your WordPress site from loading. During a Syncific Vault outage, API calls from your other plugins will proceed with the placeholder key and fail authentication at the provider (OpenAI, Anthropic, etc.). Your site remains fully functional; only the AI features dependent on protected keys are temporarily affected. Once the broker is reachable, key injection resumes automatically.
Yes. Syncific Vault intercepts the HTTP requests that the Connectors API makes to AI providers, injecting the real key from the vault instead of the one stored in the WordPress database.
Each site in a multisite network gets its own vault entry (keyed by site URL hash). Sites cannot access each other's keys.
Yes. Syncific Vault includes a built-in database scanner that checks wp_options for common AI API key patterns (OpenAI, Anthropic, Google AI, OpenRouter). Run it anytime from the settings page to confirm no keys are exposed.
Keys remain in the vault until you remove them. You can remove any key from the Syncific Vault settings page at any time. On plugin uninstall, local references are cleaned up. To remove keys from the vault itself, use the Remove button before uninstalling.
No. Syncific Vault doesn't replace your provider relationship — OpenAI, Anthropic, Google AI, and OpenRouter all let you retrieve or regenerate keys from your provider dashboard at any time. We recommend keeping an off-vault backup of any business-critical API key. The plugin is designed so you can leave at any time: deactivate Syncific Vault, paste your original keys directly into your plugins, and continue normally. Your provider accounts and keys are always yours.