How your data is protected
How SEObolt stores your password, your Google connection and the keys you add, and how API keys are kept.
Your password
Your SEObolt password is stored as a one-way hash, never as the password itself. Nobody at SEObolt can read it.
Your Google connection
The tokens that let SEObolt read your Google data are encrypted (AES-256-GCM) before they're saved. They're only used to fetch the data you've authorized. Disconnect in Settings β Integrations deletes them; see Your Google data.
Keys and secrets you add
These are encrypted the same way before they're saved:
- AI provider keys you add in Settings β API Keys (for example OpenAI, Anthropic, Perplexity, Gemini and DeepSeek).
- Your SerpAPI, PageSpeed and YouTube keys.
- The connection key and webhook secret for each connected WordPress site.
- Your email provider's settings, if you send reports through your own provider.
- Your license key.
SEObolt API keys
When an owner or admin creates an API key, SEObolt shows it once and then keeps only a fingerprint (a SHA-256 hash) of it. The key itself can't be shown again, even by SEObolt. If it's lost, revoke it and create a new one.
API keys can only read data, never change it. A key can be limited to some sites, and the plan is checked on every request. See The SEObolt API.
Signing in
- Sign-in uses a secure, HTTP-only session cookie that lasts up to 7 days.
- Sign-in attempts and new accounts are rate limited; see Rate limits.
- Only owners and admins can invite or remove team members and manage API keys. Only the owner can change a member's role.
In transit
The app is served over HTTPS. Its pages can't be embedded in other sites, which protects against clickjacking.
Last updated 2026-10-28