← RHOMA home

App Privacy Policy

RHOMA helps residency teams view schedules, teaching sessions, and learner assignments. This policy describes information handled by the RHOMA mobile app, maintained by Brett Magner, MD. It does not describe all features of the separate Didactics Builder or other websites.

Information RHOMA handles

Program schedules. Program administrators provide names, professional roles, training levels, scheduled dates and times, assignments, work locations, supervising clinicians, and teaching-session details. This information is displayed to people using the program’s schedule. A scheduled work location is not your device’s GPS location.

Program access. When you enter a program access code, RHOMA sends it to its server to verify access. The app then saves a randomly generated access token in your device’s secure storage so you do not have to enter the code every time. The server keeps a hashed version of that token, its creation date, and access-version information. This token is not an advertising identifier. The mobile app does not require a personal email account or individual password.

Device preferences. Preferences such as your selected person and onboarding status are stored locally on your device.

Technical information. Requests to RHOMA’s hosting services include network information such as an IP address. Hosting services may maintain operational and security logs to deliver the service, investigate errors, and protect against misuse.

Support requests. If you email us, we receive your email address and the information you choose to include. Please do not send patient information.

How information is used

Information is used to display program schedules, remember approved access and preferences, maintain the service, protect against misuse, and respond to support or privacy requests.

The current app has no advertising or analytics SDKs. It does not request access to your contacts, photos, microphone, camera, precise location, or Apple Health data. RHOMA is a scheduling tool, not a patient-record system.

Sharing and service providers

Program information is shared through the program’s schedule features. Program administrators are responsible for deciding what information to include and whom to provide access to. Do not share a program access code or schedule link beyond its intended audience.

RHOMA uses Supabase for its database and access services. Infrastructure providers process information needed to operate and secure these services. If you contact us by email, our email provider processes that correspondence. Information may also be disclosed when required by law or necessary to address fraud, abuse, or security incidents.

RHOMA does not sell personal information, use it for targeted advertising, or track your activity across other companies’ apps or websites.

Storage and retention

Program schedules and roster records remain in the program’s database until administrators update or remove them; the end of a scheduled rotation does not automatically delete its records. Saved access records have no automatic expiration and remain until removed. An access reset can invalidate a record without deleting it. Removing the app does not automatically remove server-side information, and secure device storage may persist after an app is removed.

Our current Supabase Free plan provides one day of API and database log history. Service-provider security records may follow separate retention rules. Backup copies, where maintained, may retain deleted records until those copies are replaced or removed. Support correspondence is retained as needed to respond to requests and maintain relevant records.

Your choices and requests

Contact your program administrator to correct schedule information. To ask about information RHOMA holds about you, request correction or deletion, or request help removing saved access, email magnerbrett@gmail.com. Include your name, program, and the nature of your request, but do not email your access code. We may need to verify your identity and coordinate with your program before acting. Some records may need to be retained for legitimate program administration or legal obligations; we will explain any applicable limitation.

Security

RHOMA uses encrypted network connections and secure device storage for its access token. No electronic system is completely secure. A shared program code does not identify an individual user, so please keep it within your program’s intended audience.

Children

RHOMA is intended for residency teams and their learners, not children under 13. If you believe a child under 13 has provided personal information, please contact us so we can investigate and address it.

Changes and contact

Updates to this policy will be posted on this page with a revised date.

Brett Magner, MD — RHOMA
magnerbrett@gmail.com