Privacy Notice
Version 1.1 · Effective November 3, 2026
Summary. ShiftMate holds the schedule and contact details the division already has, plus what you choose to add. We use it only to run the division's scheduling, show it only to the people whose role needs it, never sell it, and use no advertising or tracking. Sensitive details are encrypted, records are deleted on a set timetable, and you can see, correct and ask to delete your information. The "In short" lines help you read this notice; the full text controls if the two differ.
1. Who we are and what this notice covers
In short: ShiftMate is a staff-only scheduling tool run by Patrick Donahue as Oxbow; no patient information belongs in it. ShiftMate (the "Service") is a scheduling tool for the members of one emergency medicine division, operated by Patrick Donahue, doing business as Oxbow ("Oxbow", "we", "us"). This notice is published at https://oxbowhq.com/privacy. This notice explains what information the Service holds about the people who use it or appear in the division's schedule, and what we do with it. The Service is used only by people the division invites; it is not offered to the public, except for the Feedback form, which anyone can use without signing in, on the Service and at https://oxbowhq.com. The Service is not used for patient care and is not meant to hold patient information or other protected health information; please do not enter any (Terms of Use, section 5).
2. Information we hold
In short: the division's roster and schedule, what you add, and basic sign-in records. From the division and its official schedule, which the Service reads but does not change:
- your name, preferred name, the name used on the schedule, credentials, title, clinical role, fellowship year and roster year;
- your work email address, cell and pager numbers, and how you prefer to be contacted;
- your birth date, used only where a scheduling rule depends on it;
- your shifts, vacations and other schedule entries, and your identifier in the division's scheduling system.
From you, when you choose to add it:
- times you cannot work ("blocks") and notes on them;
- links to personal calendars you connect, and the events the Service imports from them (titles are kept only if you choose "details"; with "busy" only the times are kept);
- scheduling preferences, saved trade searches, trade requests and your settings;
- feedback you send through the Feedback page;
- a password, if you set one (we keep only a one-way hash of it, never the password itself).
If you use the Feedback form without signing in, we hold the email address you give, your message, the confirmation code we send to that address (as a one-way hash) and, to limit misuse, a scrambled form of your network address that cannot be turned back into the address.
Automatically, when you use the Service:
- sign-in records: your email address, when you signed in and out, whether you chose a private or shared device, and a short device label such as "Chrome on Windows";
- a record of each version of the Terms of Use and of this notice you accepted, and when;
- a coded (keyed hash) form of your network address, kept for about one day to limit repeated sign-in attempts; the address itself is not stored;
- a record of each change made to schedule and personal information, with who made it, kept so the division can see what changed and why;
- performance and error records that hold the page type, the result, the time taken and, for errors, where in the program the error happened, without your name, email address, network address or the values you entered.
3. How we use information
In short: only to run the division's scheduling and keep it secure; never sold, never ads. We use the information above only to:
- show you and the division the schedule and find trades, swaps and pickups that follow the division's rules;
- sign you in, keep accounts secure and limit misuse;
- check that a Feedback message comes from a person and from the email address given, and limit misuse of the form.
- send the emails the Service needs: sign-in codes, invitations, password resets, notices that your email address changed, the results of requests, and digests to those who approve requests;
- keep the division's record of changes;
- fix problems and improve the Service. We do not sell personal information, use it for advertising, or use it to build profiles for anyone outside the division's scheduling.
4. Who can see it and who we share it with
In short: colleagues see what their role needs; Microsoft hosts it in the US; nothing goes elsewhere unless the law requires. Within the division, what a person can see depends on their role: for example, colleagues can see the shared schedule, and schedulers and leaders can see and change more, as the Service explains on each page. Birth dates, cell and pager numbers are shown only to people whose role needs them. Service providers process information for us under their own security and privacy terms and only to run the Service:
- Microsoft Azure hosts the Service and its database, delivers its emails and holds its performance and error records, in the United States (East US region);
- the division's scheduling system provider, from which the Service reads the schedule (the Service sends it no personal information other than the request).
- Cloudflare runs Turnstile, the check on the Feedback form that tells people from automated programs. While the check runs, Cloudflare receives technical details from your browser, such as your network address, browser type and connection details. Cloudflare uses them to detect and block automated programs, not to identify, profile or target you. Cloudflare's own Turnstile privacy terms (https://www.cloudflare.com/turnstile-privacy-policy/) apply to what it receives.
- GitHub (owned by Microsoft) stores the feedback you send, in a private repository, so that it can be worked on; it is encrypted before it leaves the Service, and GitHub cannot read it.
Calendar hosts: when you connect a personal calendar, the Service fetches it from its host, such as Google or Microsoft, which sees a request from the Service. When the law requires it: we may disclose information if a law, court order or other legal process requires it, or to protect someone's safety. If someone else takes over the Service for the division, such as a company Patrick Donahue forms to run it, the information would move to them under this notice.
5. How we protect it
In short: encrypted connections, encrypted storage, extra encryption for sensitive details; no system is perfect. The Service is reached only over encrypted connections (HTTPS), and Microsoft encrypts the database, its backups and storage at rest. In addition, the Service encrypts birth dates, cell and pager numbers, calendar links, imported event titles, block notes and feedback with its own key before storing them. Access depends on each person's role, sign-in uses one-time codes or a password with protections against guessing, and changes are logged. No system is completely secure, and we cannot promise that information will never be accessed without permission. If a breach affects your information, we will tell you and the division as the law requires and as our incident plan sets out.
6. How long we keep it
In short: records are deleted on a set timetable; the schedule history stays as the division's record.
- Sign-in records and device records: deleted 365 days after they end or are last used.
- Coded network addresses: about one day.
- Feedback sent without signing in: kept and deleted like other feedback. An email address that never confirms its code is deleted, with its unsent message, within 24 hours.
- Confirmation codes for the Feedback form: they expire after 10 minutes and are deleted within 24 hours.
- Scrambled network addresses used to limit misuse: deleted within 24 hours.
- Feedback: deleted from the Service 90 days after it is passed on to be worked on; the encrypted copy is deleted when the work on it is finished.
- Records of the Terms and notice versions you accepted: kept while you have an account and for six years after your access ends, as evidence of what was agreed (the Ohio limit for claims on a written contract, Ohio Revised Code 2305.06).
- Imported calendar events and blocks: deleted after the event-history period you choose in your settings.
- When you leave the division: your calendar links are deleted at once, and the rest of your personal information (contact details, preferences, calendars, feedback and sign-in records) is deleted 90 days after you leave; your name stays in the division's schedule history and record of changes.
- The division's schedule history and the record of changes are kept for as long as the division needs them as its scheduling record.
- Backups: Microsoft keeps automatic database backups for 35 days, and an encrypted weekly copy is kept for 8 weeks.
7. Your choices
In short: see, correct and ask to delete your information; we answer within 30 days.
- See and correct: you can see and correct most of your own information on the My Information page; for anything else, ask the division's scheduler or us.
- Delete: you can remove your blocks, notes and calendar links yourself; to ask that other information be deleted, use the Feedback page or ask the division; we will delete what the division does not need to keep as its scheduling record.
- Calendars: you can disconnect a calendar at any time, which deletes its link.
- Emails: the Service sends only the emails listed in section 3, which are needed to use it; it sends no marketing. Neither Ohio nor Kentucky currently has a privacy law that gives rights for information like this, held about staff in their work; we answer these requests anyway. We will answer a request within 30 days.
8. Cookies
In short: only the cookies needed to sign in; no tracking; one check from Cloudflare on the Feedback form. The Service uses only cookies it needs to work: to keep you signed in, to recognise a device you have signed in on, to protect forms against forgery, to remember a private or shared device choice, and to show one-time messages. It uses no advertising, analytics or tracking cookies. The one piece of content it loads from another website is Cloudflare's Turnstile check, and only on the Feedback form. Cloudflare uses what the check needs only to detect automated programs, so there is nothing to opt out of. The Service does not respond to "Do Not Track" signals because it does no tracking.
9. Children
In short: adults only. The Service is for adult members of the division and is not meant for anyone under 18.
10. Changes to this notice
In short: we post each change with its date and show you the new version on your next visit. When we change this notice we will post the new version at https://oxbowhq.com/privacy with a new effective date and a list of what changed. The next time you visit the Service, it shows you the new version and asks you to confirm you have read it, through the same screen as at first sign-in, before you continue. A material change to how we handle information we already hold applies to you only after you confirm it; until then we handle your information under the version you confirmed.
11. Contact
In short: use the Feedback page. Questions or requests about this notice go to Patrick Donahue through the Feedback page in the Service.
12. What changed in version 1.1
In short: anyone may now send feedback without signing in; this notice says what that holds and who checks it.
- Section 1: the Feedback form can be used by anyone without signing in, on the Service and at https://oxbowhq.com.
- Section 2: what we hold when you use the form without signing in: your email address, your message, a one-way hash of the confirmation code and a scrambled form of your network address.
- Section 3: we use it to check that a message comes from a person and from the email address given, and to limit misuse.
- Section 4: Cloudflare runs Turnstile, the check on the form, and receives technical details from your browser while it runs.
- Section 6: how long each of these is kept (24 hours for unconfirmed messages, codes and scrambled network addresses).
- Section 8: the Cloudflare check is the one piece of content loaded from another website, and only on the Feedback form.