Running now. Nothing here is a plan.
No patient, ever
Adelo holds schedules, hours, credentials, training, messages and the unit's own counts. It never holds a patient: no names, no record numbers, no clinical detail. Where it touches patient flow (census, capacity, the OR list) it takes counts only.
Every row belongs to a unit
Row level security on every table. A person signed in to one unit cannot read another unit's rows, even with a direct database call.
Access by role
Staff see the schedule and their own record; charge nurses what a shift needs; managers the unit. Pay, health, HR and leave records are own row or manager only, written only through checked functions.
Hidden at the column
PINs, personal emails and setup codes are hidden at the database column, so even a signed in user's direct read does not return them.
Sign in
Email and password through a managed authentication service, with password reset and session handling. SAML 2.0 single sign on for a health system, set up with its IT team on request.
Signed integrations
Timekeeping and incentive sheets, the HA's morning snapshot and the admissions list reach Adelo through signed posts: a secret per unit, a timestamp, an HMAC signature, five minute window. Counts cross; patient detail does not.
A boxed assistant
Ask Adelo reads through an explicit table and column list that leaves out pay, health, HR, PINs and emails. Its only write is a proposal the manager confirms.
Hosting
Vercel and Supabase, in the United States, encrypted in transit and at rest. Secrets live only in the hosting providers' settings; the browser receives public keys only.
A record of access
A manager reading a career record, a transcript or a termination is written to an access log with who, what and when.
Closed by default
Every database function is closed to anonymous callers unless a signed out page needs it (the careers board, the join screen, an offer link). The list is short and reviewed; the hosting provider's security advisor was clean of warnings on 25 October 2026.
Ask us for any of these.
The written security summary and the review behind it, with what each item verified.
The table and column list the assistant is limited to.
The list of functions open to anonymous callers and why each is.
The access log for your unit.
The single sign on steps for your identity provider.
On the roadmap.
Availability and backup commitments
Documented backup and availability targets.
Vulnerability management
A written program with a scanning cadence and remediation windows.
Independent assessment
An outside security review, ahead of any certification work.
Adelo is scoped to keep patient information out.
This is a workforce product. It holds schedules, hours, attendance, credentials, messages between staff and recognition. It does not hold clinical data. Patient information should never be entered or uploaded, and the workflows give no reason to. No Business Associate Agreement is required for the services described here.
That scope is the reason a unit can be live in days. Most of what makes healthcare software slow to approve is the patient data it touches. Adelo touches none.
Found a problem? Tell us.
Email security@getadelo.com and we will answer promptly. Reviewing Adelo for your IT or security team? There is a page written for you.