What we do, and what we do not.

Accounts are issued by Haven. There is no public sign-up. Every request is authenticated against our identity provider on the server, not trusted from the browser, and a deactivated account stops working on its next request rather than at the end of its session.

Access is granted by role and by division, checked on the server. Staff see the divisions they are assigned to. Call recordings and transcripts are further restricted: you can hear a call if it was yours, or if your role is one of the small set cleared to hear all of them. A deny-by-default authorization layer covering every route is written and currently running in report-only mode while we confirm it against real traffic before it starts refusing requests.

All traffic to our sites and to the portal is served over TLS. Our managed database and our identity provider both encrypt data at rest. Payment card numbers never reach Haven systems; card data is handled by Stripe.

Privileged actions are recorded with the account that performed them, their role, the record affected, the time, the source address and the browser agent. Application errors are logged with a reference code that we can trace, and the code is all the caller is shown, so internal detail is not returned to the browser.

An automated monitor checks the gateway, the portal, the API and the running processes every five minutes and alerts on a change of state. Scheduled jobs write a positive record of every run, so a job that fails to start raises an alarm instead of passing unnoticed.

Secrets live in the server environment, never in application code. Session credentials are never placed in a URL. Where a browser feature cannot send a normal authorization header, we issue a single-use ticket valid for sixty seconds instead.

The database is hosted on a managed platform with automated daily backups. We have not yet completed and timed a full restore drill, so we do not publish a recovery time objective. That drill is scheduled. We would rather tell you that than quote a number we have not proven.

Haven is not SOC 2 certified. SOC 2 readiness work is in progress. We are happy to complete a security questionnaire and to talk through any control on this page in detail.

Ask us for a copy of what we hold about you, or ask us to delete it, and we will. Records we are required to retain under FAA Part 145 maintenance rules are kept for the period the regulation requires, and we will tell you which those are.

Email security@havenasg.com. Tell us what you found and how to reproduce it. We will confirm receipt, and we will not pursue anyone who reports in good faith and does not access or alter data that is not theirs.