Last updated: 30 August 2026
1. Information processed
The Service may process account details, role and membership data, unit/station information, roster duties, requests, daily assignments, timestamps, subscription status, and technical/security data needed to operate the Service.
2. Providers
The Service uses Firebase / Google Cloud for authentication, hosting, database services, and analytics; Cloudflare for the billing backend; Paddle for payment/subscription processing; and Google AdSense for manually placed responsive advertising. Advertising may appear on public information pages and at the bottom of the authenticated Assignment Board and Monthly Duty Roster. It is excluded from digital-form execution, approvals, administrative workflows, legal pages, and printed/PDF output. Google advertising technologies may use cookies, IP addresses, or other identifiers as described by Google and subject to applicable consent choices.
3. Payment data
Full card details are entered into Paddle's checkout and are not stored in the Duty Roster application. The Service stores limited entitlement metadata such as provider IDs, subscription status, plan, and billing period.
4. Free-trial data
To enforce the one-time 24-hour free trial per unit, the Service stores a permanent flag indicating that the trial was used, together with its activation and expiry times.
5. Sensitive information
Users should avoid entering unnecessary patient-identifying or other sensitive information. Organizations remain responsible for their own legal and regulatory obligations.
6. Contact
Privacy questions: mahmod.hamoda@gmail.com.
Push notifications
If you enable push notifications, the app stores a Firebase Cloud Messaging registration identifier for each enabled device. It is used to deliver Duty Roster releases, station assignments, and trial-request status updates, including while the supported browser/PWA is in the background.