Business continuity policy
How OBMr keeps serving customers when something disrupts Quateria Inc.'s people, suppliers or systems.
What matters most
- Customers can sign in and reach their records.
- Customer data stays safe and correct.
- Customers can reach us.
Planning for disruption
| Disruption | Response |
|---|---|
| The hosting provider has an outage | The provider's own redundancy applies. We tell customers, follow the provider's status, and keep the static pages and status updates available. |
| The database provider has an outage | Follow the disaster recovery policy. |
| A key person is unavailable | At least two named people hold production access, the ability to deploy, and access to the domain, email and billing accounts. Credentials are kept in a shared password manager with two-step sign-in. second named person. |
| A supplier ends service or fails | The code runs on any Node.js host and any PostgreSQL database, so we can move. Data can be exported from the database at any time. |
| Our domain or email fails | Domain auto-renewal is on, with two people able to manage it. Customers have a second contact route: backup contact method. |
| Cyber attack | Follow the incident response policy. |
Keeping it current
This policy is reviewed every year, after any real disruption, and whenever a key supplier or person changes. The people named here confirm each year that their access still works.
