Dearbh

Information security policy

Version 1.2. Effective 15 November 2026. Policy owner: Thomas McShane, Founder, Dearbh Corporation. Reviewed at least once a year, and sooner if our systems change.

This policy says how Dearbh protects the information it holds, most of all the health information in appeal cases. It is written to be read by the people whose cases we hold, by the organisations who use Dearbh, and by health plans and others who need to check how we work.

How to read this page. Everything under a normal heading is in place and working today. Things we have decided to do but have not finished are listed only under Roadmap at the end. We do not hold SOC 2, HITRUST, or any other security certification, and our controls have not been checked by an outside auditor.

1. What this policy covers

2. Who is responsible

Dearbh is a single-founder company. Thomas McShane, Founder, is the policy owner, the security official and the privacy official. He approves this policy and any exception to it. Contact: [email protected].

3. The kinds of data we hold, and where each one lives

Cloudflare never receives PHI. app.dearbh.io is set as “DNS only” in Cloudflare, so traffic to the app goes straight to AWS and does not pass through Cloudflare. Our automatic test suite checks this setting on every change.

4. Access control

5. Signing in

6. Encryption

7. How AI is used, and its limits

8. Where data is stored and processed

Health information is stored and processed only in the United States, in our AWS account in us-east-1. The companies we use:

We use no outside AI model provider in production today (section 7).

9. How the app is built to stay locked down

10. Logging and monitoring

11. Secure development and changes

12. Backup and recovery

13. Security incidents and breach notification

If we find, or are told about, a possible security incident, the owner will:

If health information was breached, we will give the notices the law requires, without unreasonable delay. That includes the HIPAA Breach Notification Rule: no later than 60 days after we find the breach, to the people affected or, where we act for a health plan or provider, to that plan or provider, and to the U.S. Department of Health and Human Services and the media where the rule requires it. It also includes Florida law (section 501.171, Florida Statutes): notice to affected Florida residents no later than 30 days after we find the breach, and to the Florida Department of Legal Affairs when 500 or more Florida residents are affected. Where other state laws or a contract set a shorter deadline, we meet the shorter one.

To report a security concern, email [email protected].

14. Keeping and deleting data

15. Companies we work with

The companies we use are listed in section 8. Health information goes only to AWS, under our AWS Business Associate Addendum. Before any other company could receive health information, we would need a signed business associate agreement with it, and we would update this page first.

16. Physical security

Dearbh has no servers of its own. The app and its data run in AWS data centers, and the public website runs on Railway. Physical security of those buildings is provided by those companies.

17. People

Dearbh has one person today, the founder, who has access to production. Formal security and HIPAA training, and a written process for giving and removing access as people join, are on the Roadmap and will be in place before anyone else is given access to health information.

18. Exceptions and changes

Any exception to this policy must be approved by the owner in writing, with a reason and an end date. When this policy changes, we update this page, its version and its date.

Roadmap: being put in place

These are not in place yet. We list them so no one mistakes them for current practice.

Who we are

Dearbh is run by Dearbh Corporation. For anything about this policy, email [email protected].