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
- app.dearbh.io, the Dearbh app and its APIs, where appeal cases are built. This is the only part of Dearbh that holds health information.
- Amazon Web Services (AWS), where the app runs and where cases are stored.
- The public-source pipeline, which copies published law, rules and coverage policies into Dearbh so letters can quote them.
- FHIR files from a health plan. A member can upload a FHIR file their plan gave them. It is part of their case and is handled as health information. If we later connect to a plan’s FHIR service directly, that data will be handled the same way.
- dearbh.io, our public website. It holds no health records. Its waiting list is covered by our privacy notice.
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
- Protected health information (PHI). Case records: denial letters, medical records, plan documents and FHIR files a person adds to a case, and the letters built from them. These are stored only in our AWS account, in the US East (N. Virginia) region, us-east-1. Our AWS Business Associate Addendum is active in that account (in force since 27 July 2026).
- Case activity records. Our signed audit record (section 10) holds ids, hashes and who did what. It does not hold case text. It is stored with the cases in AWS.
- Public reference data. Published law, regulations, Medicare coverage policies and similar public documents. These are kept in the app’s own image in AWS, and some public files are staged in Cloudflare R2 storage before AWS copies them in. Cloudflare R2 holds public data only.
- Website and waiting-list data. Names and email addresses from the dearbh.io waiting list, held by our website host, Railway, in the United States. No health records are collected there.
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
- One account per person. Each person in an organisation has their own seat, tied to their own email address. There are no shared logins.
- Roles. Some actions are limited to an organisation’s administrators: adding, changing and removing seats, renaming the organisation, rotating its key, setting the organisation’s verification checks, making, rotating and revoking agent credentials, resuming paused agent intake, and (for people) sending documents to intake.
- Seat changes need a signed-in administrator. Only an administrator, signed in with their own email link, can add a seat, change a seat’s role or remove a seat. The organisation key, agent credentials and members are refused. A role is either administrator or member, nothing else. The last administrator cannot be removed or made a member. Every seat change is recorded on the organisation’s audit trail.
- Organisation settings need a signed-in administrator. Only an administrator, signed in with their own email link, can rename the organisation or rotate its key. The organisation key cannot rename the organisation or rotate itself, and agent credentials and members are refused. Every change is recorded on the organisation’s audit trail. Rotating with no grace period stops the old key at once.
- Agents get their own credentials. Each software agent an organisation connects gets its own credential, made by an administrator. We store only a hash of it. A credential can be rotated or revoked at any time, and it only reaches document intake. Repeated failed agent sign-ins from one address lock that address out for an hour.
- Organisations are kept apart. Each organisation’s cases sit in their own storage area, are opened by their own case process, and are encrypted under their own key (section 6).
- Our own access to AWS. The only person with access to our AWS account is the founder. Other AWS identities are for machines, and each is limited to one job, such as sending email or deploying the app. The app runs under its own AWS roles, and each encryption key’s policy lets the app take only the exact actions it needs.
5. Signing in
- People sign in to app.dearbh.io with a link sent to their email. Each link works once and expires after 15 minutes. Sign-in requests are rate limited by address and by email. The reply does not say whether an email has an account.
- After sign-in the session is held in a secure, HttpOnly cookie that expires after 12 hours.
- Multi-factor sign-in (MFA) is turned on for the main (root) user of our AWS account. MFA for every other administrator sign-in is on the Roadmap.
6. Encryption
- In transit. app.dearbh.io accepts only HTTPS, using TLS 1.2 or TLS 1.3 (AWS load balancer policy ELBSecurityPolicy-TLS13-1-2-2021-06). Plain HTTP is redirected to HTTPS. Traffic between the app and its file storage is encrypted too.
- At rest, each case. Every case file is encrypted with AES-256-GCM under its own key. That key is locked by a key that belongs to the organisation, and the organisation’s key is locked by a master key held in AWS Key Management Service (KMS). The master key never leaves KMS, and AWS rotates it every year. Backups of the storage hold only the encrypted form.
- At rest, storage. The file system that holds cases (Amazon EFS) is encrypted at rest with a KMS key.
7. How AI is used, and its limits
- No outside AI calls in production today. The live app is set to run on Dearbh’s own rules only (DEARBH_GOVERNANCE_PROVIDER=dearbh). In that mode it makes no calls to any outside AI model, and it refuses such a request in plain words.
- If outside AI calls are turned on later, the text is de-identified before it is sent. Names and other identifiers are swapped for placeholders, the model sees one page at a time, and its answer is mapped back and checked against the original page. Any answer that cannot be mapped back exactly is thrown away.
- Every quote is checked character for character against the source document. A quote that does not match exactly is removed.
- Eleven checks before sign-off. A final audit runs eleven checks on each appeal before it can be signed off. If any check fails, the appeal is blocked and the failed check is shown.
- A person signs every letter. A letter cannot be produced until a named person has signed it off. A sign-off goes stale if the case changes.
- Agents cannot decide. Software agents cannot accept findings or sign off a letter. The app refuses those actions from an agent and records the refusal.
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:
- Amazon Web Services, us-east-1: hosting, storage, encryption keys, backups and logs. Covered by our AWS Business Associate Addendum.
- Amazon SES (part of AWS), us-east-1: sends app email, such as sign-in links.
- Cloudflare: DNS for our domains, the network in front of the public website, and R2 storage for public reference files. Never PHI.
- Railway, United States (US West): hosts the public website and its waiting list. Never PHI.
- Google: our [email protected] mailbox, website analytics and fonts on the public website, as our privacy notice explains. Never used to store case records.
- GitHub: holds our source code. Not used to store case records.
We use no outside AI model provider in production today (section 7).
9. How the app is built to stay locked down
- Only the load balancer accepts connections from the internet. The app accepts connections only from the load balancer, and the case storage accepts connections only from the app and the weekly public-source copy.
- The app runs as a non-root user on a read-only file system, and it can reach only its own folder on the case storage.
- App images are scanned for known weaknesses when they are stored, and a stored image can never be changed after the fact.
- Passwords and keys the app needs are kept in AWS Secrets Manager and given to the app when it starts.
10. Logging and monitoring
- App logs go to Amazon CloudWatch and are kept for 90 days.
- AWS account activity is recorded by AWS CloudTrail in every region, with log file checking turned on, into a private, encrypted storage bucket.
- Alarms email the owner if the app fails its health check, or if the weekly public-source copy fails or goes stale.
- Signed audit record. Each sign-off, finding decision and governed action is written to an append-only record for that organisation. Each entry is linked to the one before it by a hash and signed with a key that never leaves AWS KMS, so a changed or missing entry shows up when the record is checked.
11. Secure development and changes
- Every change to the main code branch goes through a pull request. Direct pushes and force pushes to that branch are blocked, for administrators too.
- When a pull request for the app is marked ready, and again after it is merged, the full automatic test suite runs: the build, the unit tests, a full case walk-through with every check, and a check that the audit record reads back as valid.
- Dependencies are installed from a locked list of exact versions.
- The app image is built and deployed to AWS by GitHub through a short-lived role. No long-lived AWS keys are stored in GitHub for this.
- Dearbh has one engineer, the founder. Changes are checked by the automatic tests, not yet by a second person. A second reviewer is on the Roadmap.
12. Backup and recovery
- The case storage is backed up every day by AWS Backup, and each backup is kept for 35 days. Backups hold the encrypted form of each case.
- We have a written restore drill that restores the newest backup to a separate file system and checks it, without touching the live app.
- A stop switch, controlled by the owner, can pause the app if something goes wrong.
13. Security incidents and breach notification
If we find, or are told about, a possible security incident, the owner will:
- contain it first, for example by pausing the app or revoking a credential;
- find out what happened, what data was involved and whose it was, using the logs and the audit record;
- fix the cause and keep a written record of the incident and what we did.
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
- A person can download a full copy of a case at any time. The copy is decrypted for them when they download it.
- When an organisation leaves, each of its cases is exported first, then its access is turned off.
- To have case data deleted, email [email protected]. A self-service delete and a written retention schedule are on the Roadmap.
- App logs are deleted after 90 days and backups after 35 days.
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.
- MFA on every administrator sign-in: AWS users other than the root user, GitHub, Cloudflare and Google.
- Daily work in AWS through named, limited roles, with the root user kept for emergencies.
- Automatic threat detection in AWS (for example Amazon GuardDuty).
- Automatic checks for known weaknesses in our code dependencies on every change.
- A second person to review code changes, and passing tests made a hard requirement before any merge.
- A restore test run on a set schedule, with the results recorded.
- A self-service way to delete a case, and a written retention schedule.
- A formal written risk assessment, repeated each year.
- Regular access reviews.
- Security and HIPAA training before anyone else gets access to health information.
- An outside penetration test.
- An independent security audit.
Who we are
Dearbh is run by Dearbh Corporation. For anything about this policy, email [email protected].