My Clinical Shifts

Privacy policy

How information is used for staff scheduling and access.

Last updated November 18, 2026

Information we handle

My Clinical Shifts is a staff scheduling tool used by more than one facility. Each facility has its own schedule, staff list, and history. Its protected scheduler stores the facility you belong to, your name, personal email address, verified sign-in identifier, discipline, employment type, access role, approval status, and account status.

It also stores work dates and hours, shift requests and their comments, manager-recorded time off and its status, monthly scheduling requirements, changes and approvals in the activity log, notification preferences, and notification delivery records. Historical display names or usernames may remain in existing records.

If you report a problem, the scheduler stores your report, the optional screenshot you attach, and manager replies or status updates. A copy of the report’s text, with your name, facility, and email address but without the screenshot, is emailed to the site’s support mailbox so it can be answered quickly. Do not include patient information, passwords, verification codes, or medical details in a report or comment.

How information is used and shared within the team

Information is used to verify sign-in, manage staff access, coordinate shifts and coverage, review changes and time off, send supported notifications, troubleshoot problems, and maintain a record of scheduling decisions.

Information is shared only within your own facility. Approved active staff can see their facility’s team scheduling information, including staff names, disciplines, scheduled work, and recorded time-off status. Managers can review their facility’s staff profiles and email addresses, manage access and scheduling, inspect the activity log, and review team bug reports. Staff can read their own requests and bug reports. Staff and managers at one facility cannot see another facility’s schedule, staff, or history.

If you request a new facility, the name, facility name, location, and note you enter, along with your sign-in email, are shown to the site owner who reviews the request. The site owner can see each facility’s name, subscription status, and its counts of active staff, managers, and pending accounts. To provide support, the site owner can also open a facility’s schedule, staff list, and activity log in a read-only view; each time this happens it is recorded in that facility’s activity log, where its managers can see it.

A facility may be part of a health system that the site owner sets up for an organization with several facilities. When a facility joins a health system, that system’s administrators can see aggregate figures for the facility: counts of active staff by discipline and employment type, required and scheduled coverage hours and days short, unfilled open signup hours, the number of requests awaiting a manager, how many PRN staff are meeting their monthly minimum, the subscription status, the schedule lock and the time zone. They do not see staff names, email addresses, individual shifts, time-off reasons, request comments or the activity log, and they cannot change the schedule. Joining or leaving a health system, and each change to who administers it, is recorded in the facility’s activity log, where its managers can see it.

Signing in does not automatically approve an account or place it in a facility. You join a facility with the code its manager shares, and scheduler permissions come from that facility’s current staff roster and manager-assigned role.

Services that help the scheduler work

Hosting and account security

Cloudflare hosts the site and scheduler and stores scheduler records in D1. Cloudflare may process technical connection information as part of delivering and protecting the service. The scheduler uses sign-in cookies and account security records to check access.

If you set up an authenticator, the scheduler stores an encrypted authenticator setup secret, hashed recovery codes, and records used to prevent code reuse and limit sign-in attempts. Session tokens are stored as hashes. The scheduler checks authenticator or recovery codes you submit; it does not ask for your email account password. Keep your authenticator setup key and recovery codes private.

Google sign-in, when available

If you choose Google, Google verifies your identity and provides the scheduler with basic sign-in information, such as your name, verified email address, and Google account identifier. The scheduler links that identity to your staff account. This sign-in integration does not request access to your Gmail messages, Google Drive files, contacts, or Google Calendar.

Microsoft sign-in, where a facility uses it

If your facility offers Microsoft sign-in and you choose it, Microsoft verifies your work account and provides the scheduler with basic sign-in information: your organization’s tenant identifier, your account’s object identifier, your name, and your email address. The scheduler stores the tenant and object identifiers to link that work account to your staff account, along with the name and email address so you and your managers can recognize it. Your Microsoft password is never sent to the scheduler, and the integration does not request access to your mailbox, files, calendar, contacts, or organization directory. A facility can require Microsoft sign-in for its schedule.

Subscription payments

A facility’s manager pays for its subscription through Stripe. The card number and billing details are entered on Stripe’s pages and are not stored by the scheduler. The scheduler stores the facility’s subscription status, trial and renewal dates, its license key, and Stripe’s customer and subscription identifiers. Stripe receives the manager’s email address and the facility’s identifier to manage the subscription. Staff who are not managers are never asked for payment details.

Email notifications

Resend sends upcoming-shift reminders and PTO approval notifications to eligible staff using their personal email. Managers can also receive emails about shift requests, pending PTO, and new staff awaiting approval. Delivery uses the recipient address and relevant scheduling or approval information, such as the staff name, date, hours, and discipline. Private request comments are not included in these emails. Delivery status and provider message identifiers are retained for troubleshooting.

Phone notifications, where available

If you turn on phone notifications, the scheduler stores a push subscription for each device you enable: your browser’s push address and encryption keys, a general device label such as “Safari on iPhone”, and when notifications last succeeded or failed. Notifications are encrypted and sent through your browser’s push service (for example Apple, Google, Microsoft, or Mozilla) and show a short title and summary of the same updates you receive by email. You can turn them off for a device at any time; devices are removed automatically when access ends.

Optional urgent-shift text messages

If your facility turns on text alerts, you may add a US mobile number in your staff profile and choose to receive texts about urgent open shifts. Your number is stored only for those alerts, together with the date and wording of your consent, and is used only after you opt in. Twilio delivers the texts and receives your number and the message, which names the facility, discipline, date and hours needed with a link to the scheduler. Managers see only the last four digits. Mobile numbers and text-message consent are never sold or shared with third parties for marketing. Reply STOP to any text to opt out, START to opt back in, or HELP for help; you can also turn texts off or remove your number in your profile at any time. Message and data rates from your carrier may apply. Sent-message records, including segment counts used for the facility’s charges, are retained.

Providers operate under their own terms and privacy policies: Cloudflare, Google, Microsoft, Resend, Stripe, and Twilio.

Retention and your choices

Scheduling history, account and approval records, audit history, delivery records, and bug reports are retained to support scheduling, troubleshooting, and recovery. Moving a staff member to Trash is recoverable: previous days and coverage remain, and a recovery snapshot is saved. Managers can permanently delete a trashed account’s profile, sign-in credentials, and recovery snapshot. Historical scheduling and audit records may retain a minimal identity so previous coverage remains understandable. There is no automatic deletion period or staff self-service permanent-delete feature.

You can turn upcoming-shift reminder emails on or off from notification settings. Managers have separate switches for shift requests, pending PTO, and new-staff approval emails. These preferences start enabled when no preference has been saved. PTO approval emails remain enabled independently of these switches. Screenshot attachments are optional.

For corrections, access changes, or a request about your information, contact your scheduling manager through your facility’s usual channel. A request may require review of retained history and recovery records; this policy does not promise immediate deletion from all systems or provider backups.

Public information pages

These public pages contain information about My Clinical Shifts. They have no forms, advertising scripts, analytics scripts, or embedded scheduler data. Opening the staff schedule takes you to the separately protected application. Cloudflare still handles the connection needed to serve these pages.

Questions or concerns

Contact your scheduling manager through your facility’s usual channel for privacy, access, or scheduling questions. Approved staff can use Help → Report a problem for technical issues. For questions about the service itself, write to support@mytherapyshifts.com. This policy may be updated as the service changes; the date above identifies the current version.