Your data, your systems, your control.
Three things a customer asks before anything else: will it keep working when something fails, will our information stay ours, and what does it know about our people. This page and the film answer them from how EOS is built, and say plainly where a capability is specified and not yet built.
Read this first. It is not a security certification, and no figure on this page or in the film is a service level. The hosted service runs on managed cloud infrastructure in one United States region. A packaged install that could run disconnected is not built yet.
The film, two minutes
Reads, never writes. One organization never sees another. Nothing crosses a boundary without a grant. A failure is shown and never dressed as success. A name on every consequential step. Privacy at the door, and a way out.
Resilience
| Question | How EOS answers it |
|---|---|
| What if EOS is wrong or down? | EOS holds no write credential to your systems of record, so there is nothing of ours to unwind in them. Your systems keep running as they were. |
| What if the data is missing, stale or in conflict? | The gap, the age or both values are shown, with the rule applied. A disagreement is preserved, never silently overwritten. |
| What if the SI is unsure? | Every material claim carries a label: observed, derived, inferred, assumed, scenario, recommendation, decision, action or outcome. A guess may not be promoted to a fact. |
| What if a change goes wrong? | A change is made only by your own executor, on a named person's approval, under a signed single-use authorization. Changes are reversible and need two people above a threshold, and every write is chained. |
Confidentiality
| Question | How EOS answers it |
|---|---|
| Can another customer see our data? | No. Organizations are isolated: users, records, decisions and audit log. |
| What can leave? | Only what your organization registers. Events go to destinations you register, signed. Between two organizations, Fides decides what may cross, at which level and under whose grant, and names every refusal. |
| Who can act on it? | Roles and permissions are checked on the server on every request. An agent never decides; only a named owner, admin or controller does. |
Privacy
| Question | How EOS answers it |
|---|---|
| Who can come in? | One door. Every person signs in, accepts the Participant Terms and passes a United States identification check before anything signed-in answers. |
| Where is the data processed? | In the hosted service in one United States cloud region, for your organization only, by the providers on the published sub-processor list. |
| Can we leave, and take it with us? | Sealed registers export today, with a seal you can recompute offline. A full export is assembled on request within five business days at no charge, export stays available for 90 days after termination, and deletion is certified within 30 days of your written instruction. Offline-verifiable evidence packs are specified, not built. |
What is not claimed
No uptime or recovery figure, no third-party certification, no multi-region failover and no disconnected install is claimed here. Source escrow is not claimed. Where the Trust Center states a maturity, that statement governs.