1. Introduction
This Privacy Policy describes how FollowUp handles information. FollowUp is a supplementary clinical organization and patient follow-up tool for healthcare professionals. It is designed around local storage on the user’s device and does not require an online account.
FollowUp is not a replacement for the healthcare facility’s official medical record and is not designed to disclose, publish, or share a patient’s private or medical information.
2. Information Entered by the User
Users may voluntarily enter limited patient identifiers and follow-up information, including names, file numbers, dates of birth, gender, nationality or country, phone numbers, insurance information, diagnoses, Treatment Plans, Follow-Up Schedules and reasons, Event notes, Additional Notes, and other information. This information may be sensitive health-related or personally identifiable information.
3. Local Storage
Patient information and app settings entered into FollowUp are stored locally on the device used to run the app. The developer does not operate a developer-controlled patient-record server and cannot remotely access information stored locally inside the app. Local storage reduces certain types of data transmission but does not remove all technical or operational risk.
4. Accounts and Registration
FollowUp does not require account creation, registration, or sign-in.
5. Smart Libraries and Existing App Data
Build Libraries from Existing Data reviews information already stored within the user’s app data to identify possible reusable diagnoses, Treatment Plans, insurance companies, and Follow-Up Reasons. The review is performed locally using information already stored in the app and does not send that information to the developer. Detected entries are shown for user review and nothing is added to a Library without the user’s approval.
6. Backups and File Export
Local JSON backups are created only when initiated by the user and may contain information stored inside the app. FollowUp exports the backup using Apple’s standard share sheet. The user decides where the file is stored or shared, and the developer does not control third-party destinations selected by the user. Users must protect exported backup files from unauthorized access.
7. Backup Import and Restore
Users may select a previously exported backup file to restore data. Users should verify that they are selecting a trusted, valid FollowUp backup and understand that restoring data may change the records currently stored inside the app.
8. Notifications
FollowUp may use local notifications for follow-up reminders. Reminder text is designed not to include patient names, diagnoses, file numbers, phone numbers, or other identifiable clinical information. Notification delivery is managed through Apple system services and the device permissions selected by the user.
9. Completion Messages and Facility Information
FollowUp can prepare multilingual Completion Messages and text-based Facility Information messages using details and reusable variables selected or configured by the user. These may include the patient’s first name, Sender Name, Current Facility, contact phone, and clinic hours.
FollowUp does not automatically send messages. The healthcare professional initiates the communication, reviews and may edit the prepared text, chooses an external communication app such as Messages or WhatsApp, and completes the sending action.
10. Facility of Practice
Users may configure Facility Names, translated Facility Names, country, contact phone, website or public page, multiline clinic hours, Facility Logo, and Additional Practice Locations. This information is stored locally and may be reused in user-initiated patient communication. When available, the Facility Name matching the selected message language may be used automatically in the prepared text.
11. Patient Share Cards and Sharing Passcode
When professional handover is appropriate, FollowUp can create a Patient Share Card containing selected follow-up information and Current Facility branding. The user chooses what to include and deliberately initiates the sharing action.
Patient Share Card PDFs can be protected using the user-defined Sharing Passcode. The Sharing Passcode is stored securely on the device. Users are responsible for communicating the passcode safely and only to an appropriate recipient.
12. External Communication and Sharing Services
FollowUp does not automatically transmit patient information to the developer. Information may leave the device only when the user deliberately initiates an action such as sending a message, sharing a Patient Share Card, exporting a backup, choosing an external storage destination, or sending an email.
When information is sent or shared through another service, it becomes subject to that service’s own privacy and security practices. No electronic communication or sharing method can be guaranteed to be completely secure.
13. Optional Images
The user may select an optional home avatar or Facility Logo from the device photo library. Selected images are stored locally. FollowUp does not upload these images to a developer-controlled server.
14. Contacting the Developer
The Contact Developer feature opens the user’s email application. Users must not include patient-identifiable information, clinical details, medical documents, or screenshots containing patient information. Email communication is handled by the user’s email provider and the recipient email service.
15. Analytics, Advertising, and Tracking
FollowUp does not display third-party advertisements, sell personal information, use patient information for advertising, include third-party advertising trackers, or create advertising profiles from patient information.
16. Data Deletion
Users can delete individual patient records or use the protected Erase All Data option. Deleting the app may remove locally stored data. Copies previously exported by the user are not automatically deleted and must be removed separately from every location where they were stored.
17. Data Security and Application Access
FollowUp uses privacy-conscious design choices, but no device, storage method, software, or electronic communication system can be guaranteed to be completely secure.
FollowUp includes an optional App Lock that may use Face ID, Touch ID, or device authentication. Authentication is handled using Apple’s system authentication services.
Users should use a device passcode, keep iOS updated, limit access to the device, protect Sharing Passcodes and exported files, and follow workplace data-security policies.
18. Healthcare Professional Responsibilities
Healthcare professionals remain responsible for confidentiality, appropriate use, recipient selection, and compliance with applicable privacy and data-protection laws, medical confidentiality rules, employer and facility policies, professional and regulatory requirements, and consent and record-keeping obligations. FollowUp is not a substitute for an approved institutional medical record system where such a system is required.
19. Children
FollowUp is intended for use by healthcare professionals and is not directed toward children as end users. Healthcare professionals may nevertheless choose to enter information relating to pediatric patients and remain responsible for handling that information lawfully and appropriately.
20. International Use, Changes, and Contact
Privacy, confidentiality, healthcare, and data-protection obligations differ by country. Users are responsible for determining whether their use of FollowUp complies with applicable local requirements.
This Privacy Policy may be updated when the app’s features or data practices change. The “Last updated” date on this page will be revised when changes are published.
Ahmad Al-Sabbagh
followup.app.help@gmail.com
