Is my content private?

Yes. The platform your engine is hosted on is designed around one principle: the operator can run your engine without being able to read its contents.

This isn't just a policy promise — it's built into how the system works.

How operations stay out of your data

Keeping a hosted engine healthy means doing things like applying updates, restarting services, checking that it's up, and taking backups. On this platform, all of that runs through a restricted account that can only execute a fixed list of infrastructure commands — and none of those commands can open your database or read your files.

So the routine machinery of hosting — the part that runs every day — has no path to your content.

Backups are sealed before they leave

Your engine's backups are encrypted on your server, with your engine's own key, before they're sent anywhere. What the operator forwards to storage is a locked blob they can't open. (More in Backups & recovery.)

What about emergencies?

Occasionally a serious technical problem can only be fixed from inside the engine. For those cases there's a deliberate break-glass process — and it's the exception, not the norm: it has to be explicitly authorized, it's time-limited, the session is recorded, and access is automatically removed afterward. It can't happen silently or by default.

In plain terms

• Day-to-day operations cannot read your content.
• Backups are encrypted before they leave your server.
• Any rare, deeper access is authorized, logged, and temporary.

If you have specific compliance needs, your hosting partner can walk you through these guarantees in more detail.