What this app is

McLean Scheduler is the tool the unit's scheduling team uses to collect availability, build the staff schedule, and share it. It holds workforce scheduling data only. It is not a medical system and stores no patient information.

What it stores about you

• Your name, work email, clinical role, schedule group and rotation, and whether your account is active.
• The days and blocks you mark as unavailable, any note you attach, and when you submitted them.
• Schedules: draft and published assignments, and the solver runs that produced them. A run keeps a copy of the availability it was built from.
• Requests you make or answer: swaps, time off, open shifts, and the decisions on them.
• A log of what the app sent you and when, and, if you turn notifications on, the push subscription for that device.
• Sign-in records: a hashed password (never the password itself), your sessions including IP address and browser, encrypted two-factor secrets and recovery codes if you set them up, and the public half of any passkey you add.
• An audit log of actions schedulers and admins take, with who did what and when.

Why

To build the schedule and run it: collect availability, generate and publish each month, handle swaps and time off, and tell the right people when something changes. There is no analytics, no advertising, and nothing is sold or shared beyond what this page lists.

Who can see what

Your availability is yours: other staff cannot see it. Everyone on the roster can see the published schedule and the team view, which the unit can limit to your own group. Schedulers and admins see the unit's data, including everyone's availability, because building the schedule requires it.

Where it lives

The app runs on Vercel and the database on Neon, both in the United States. Connections are encrypted in transit and the database is encrypted at rest.

Who else receives data

Resend delivers the app's email, so it processes your email address and the messages sent to you. If you turn on push notifications, they travel through your browser's push service (Apple, Google or Mozilla). Nobody else receives data today. If that changes, this page changes, and the change is noted below.

How long it is kept

Scheduling records are kept while the app is in service, so past schedules stay readable. One-time sign-in links are removed once used. A fixed retention schedule for the rest is being agreed with the unit and will be published here once it is set.

Corrections and deletion

Ask your scheduler first: they can fix roster details and adjust availability on your behalf. An admin can deactivate an account, which signs it out everywhere and stops future scheduling. Shifts already on a published schedule stay in that record, because the unit relies on it being what was actually worked.

Questions

Ask your scheduler. They can reach the people who run the app.

Change notes

• 30 August 2026: first published.