ScrubGrid

Security and privacy

What ScrubGrid holds, how each organization's information is kept apart, and who can see what. Written for the people who review software before a hospital uses it.

Patient information

None. ScrubGrid has no field for a patient's name, record number, date of birth or diagnosis, and its terms ask that none is ever typed into it.

A text message reply that looks as if it carries patient information is refused without being read.

What ScrubGrid does hold

The names and work contact details of providers and staff, a mobile number if a person opts in to text alerts, shifts and who holds them, rules, time off, requests and their decisions, and a record of changes.

Keeping organizations apart

Every row belongs to one organization, and the database enforces it (PostgreSQL row-level security). A request made for one organization cannot return another's rows, even if the application's own code were wrong.

An automatic test of this separation runs on every change to the application. A change that fails it cannot be released.

Signing in

There is no public sign-up. An administrator creates each account, and an email address that has no account is refused.

A person signs in with a one-time code sent to their email address. ScrubGrid keeps no passwords. A session ends after 30 minutes without activity, and always 12 hours after signing in.

Who can see what

Access is by role, and a role is given at one place in the organization and applies only there and beneath it. A provider sees their own schedule. A scheduler runs one group's schedule and cannot give anyone access. An executive reads published schedules and changes nothing. See all eight roles.

The organization's owner can review every account and what it reaches.

A record of changes

Every change to an organization's setup is listed, newest first, with who made it. Each schedule keeps its own history, and every earlier version of a published schedule can be opened to read, with the changed shifts marked.

Hosting and backups

The application runs on Amazon Web Services in the United States. Every connection is encrypted. The database is encrypted where it is stored and is backed up automatically every day, with backups kept for 35 days.

Email and text messages

Messages carry schedule facts only: a shift, a date, a provider's code. Text alerts are optional. Only the person can turn them on for their own number, the number is proved with a one-time code, and replying STOP ends them.

The full terms are public: SMS program terms, privacy policy and the opt-in workflow.

The drafting assistant

Optional, and it can be left switched off. When it is on, an administrator may describe a shift or a rule in their own words. Those words, with the group's roster of names and codes so that a named person can be matched, are sent to an AI model (Claude, from Anthropic), which returns a filled-in form.

The assistant returns settings to read, never a change to a schedule, and nothing is saved until a person applies it. The box it reads says: never include patient information.

Companies that process data for us

Amazon Web Services (hosting and the database), WorkOS (sign-in), Resend (email), Twilio (text messages, only for people who opt in) and Anthropic (the drafting assistant, only where it is switched on). This website is served by Cloudflare and collects nothing.

We do not sell information, and we do not use it for advertising.

Outside audits and certifications

None yet. ScrubGrid has not completed an independent audit such as SOC 2, and we would rather say so here than have you discover it.

If your organization has a security questionnaire, send it to support@scrubgrid.ai and we will answer it in full.

A question this page does not answer?

Write to us. Please do not include patient information in an email.