Privacy policy

Privacy Policy for Scrubook

Last Updated: October 21, 2025

This Privacy Policy explains how Scrubook (the "App"), developed by Avneet Sandhu, handles your information.

1. Data Collection and Storage

Scrubook is a privacy-first, "local-first" application. This means:

• No Personal Data Collection by the Developer: The App does not collect, transmit, or store any personally identifiable information (PII) or health-related data on servers controlled by the Developer.

• Local Storage: All user-generated data, including surgical logs, hospital names, procedure lists, and profile information (Surgeon's Name, Specialization), is stored directly on your mobile device (iPhone/iPad).

2. User-Controlled Cloud Synchronization (iCloud)

The App uses Apple's native technologies for data persistence and optional synchronization:

• Core Data and CloudKit: The App utilizes NSPersistentCloudKitContainer to store and sync your logbook records (including SurgeryLogCD, HospitalCD, SurgeryProcedureCD, and SurgeonProfileCD entities) to your personal, private iCloud account.

• Encryption: Data stored and synchronized via iCloud is subject to Apple's security and privacy policies, which include end-to-end encryption.

• User Control: Synchronization is tied to your Apple ID and is controlled entirely by you. The Developer has no access to the encryption keys or the content of your iCloud data.

3. Types of User-Generated Data Stored Locally

The App stores the following non-identifiable and professional data for the user’s reference:

• Profile Data: Surgeon's Name and Specialization.

• Logbook Data: Date, Hospital Name, Procedure Name, Charges, Amount Paid, Payment Status.

• Optional Patient Reference Data: Patient Name, Patient Age, Diagnosis, and Procedure Notes (entered as free text or numerical data).

  • Note on PII: Users are advised not to enter any information in the optional fields that could be used to personally identify a patient (e.g., specific dates of birth, social security numbers, medical record numbers). The App is intended for professional logging and is not a secure Electronic Medical Record (EMR) system.

• Image Data: Binary data (Data?) for Pre-Op and Post-Op images, which are stored securely on the device or in your private iCloud.

4. Data Usage

Your data is used solely for the following purposes within the App:

• Functionality: To display your logbook, calculate financial summaries (e.g., Total Unpaid), and provide quick-entry options (e.g., Hospital and Procedure lists).

• Reporting: To generate and export reports (CSV and PDF) based on the criteria you select.

• Synchronization: To ensure your data is consistently backed up and accessible across your devices through your private iCloud account.

5. Data Deletion and Retention

• User Control: You retain full control over your data. You can delete individual log entries, hospitals, or procedures at any time within the App.

• App Deletion: Deleting the App from your device will remove all locally stored data. Data synchronized to iCloud will remain in your iCloud account until you manually delete it or disable iCloud for the App.

• Data Cleanup: The CoreDataStack includes a function to deleteAllData() from the App's persistent container on the device.

6. Third-Party Access

The Developer does not share any of your logbook data with third parties. The only "third party" involved in data storage and synchronization is:

• Apple iCloud/CloudKit: Used for private, user-controlled data synchronization and backup.

7. Changes to this Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy within the App. You are advised to review this Privacy Policy periodically for any changes.

8. Contact Information

If you have any questions or concerns about this Privacy Policy or the App's data practices, please contact the Developer:

Avneet Sandhu - avneetsandhu1992@gmail.com