Security overview
The short version of how your engine and your data are kept safe.
Here's the security picture for your hosted Context Engine, in plain terms.
Isolation
Your engine runs in its own isolated container with its own database. It's single-tenant — yours alone — and can't be seen by any other engine that might share the same server.
Encryption
- Your engine is reached over HTTPS, so traffic between you and it is encrypted.
- Your backups are encrypted with your engine's own key before they leave the server, so stored backups can't be read by the storage provider or the operator.
Operators can't read your content
The platform that hosts your engine is built so that routine operations can't access your data. Updates, restarts, health checks and backups all run through a restricted account limited to infrastructure commands that can't open your database or files. (See Is my content private? for the detail.)
Exceptional access is controlled
If a serious problem ever requires getting inside your engine, that access must be authorized in advance, is time-limited, is recorded, and is automatically revoked when done. It's auditable and rare — never silent or automatic.
Kept healthy and recoverable
Your engine is monitored for problems and backed up automatically, so issues get caught early and your data can be recovered if something fails.
Your part
The platform handles the heavy lifting, but you help by keeping your own account secure: use a strong, unique password, and if you were given a recovery key, store it somewhere safe.
Questions about any of this? Your hosting partner can give you specifics for your setup.