Casebook Privacy Policy
Last updated: September 22, 2026
Developer: Sansar Gupta. Contact: sansargupta10@gmail.com.
Information processed by Casebook
Casebook is a personal case tracker for dentists and dental students. It processes the information you enter or import to organize treatment progress and outcomes. It does not replace the official patient chart or practice-management system.
Your workspace can include patient names or aliases, optional surnames and chart/reference numbers, treatment plans, dates, appointments, tasks, notes, custom fields, milestones, complications, implant and restoration details, outcomes, photographs, and photo captions. Templates, saved outcome views, and preferences are also stored locally. Built-in example patients are fictional.
Casebook does not require an account or send your workspace or photos to the developer. It has no advertising, tracking, third-party analytics SDK, developer-operated patient-data server, automatic cloud synchronization, or team-sharing service. We do not sell your app data or use it for advertising.
Storage and device access
Saved workspace records, photo attachments, and thumbnails are encrypted locally using AES-GCM. Their key is stored in the device's Keychain and does not synchronize to iCloud Keychain. The app marks its protected storage as excluded from operating-system backups. Other preferences, exported files, and copies made outside this storage follow your device, backup, and file-provider settings. A device-only encryption key may be unavailable on another device; use the explicit backup tools for transfers.
Casebook asks the operating system to authenticate you using Face ID, Touch ID, or a device credential. The app does not receive your biometric templates or device passcode. Inactive windows are covered, and locking follows your chosen delay and system events. Unsaved drafts may remain in memory while the app continues running. Local protection does not control screenshots, screen sharing, or access to an unlocked device.
Photos and permissions
Casebook imports only the photos you select through Photos or Files. The system photo picker provides access to your selected images without requiring full photo-library access. Imported photos are converted to reference copies with source filenames and embedded image metadata removed. Visible faces, anatomy, captions, and other image content may still identify a person. Metadata removal is not full de-identification.
Saving an image to Photos is an explicit export and requests add-only Photos permission. Photos, Files, and any cloud provider you use handle selected originals and exported copies under their own settings. You can revoke Photos permission in system settings.
Reminders
If you enable local reminders and permit notifications, Casebook schedules task and appointment alerts through the operating system. Alerts use generic counts and timing, without patient names or notes. They may appear on the Lock Screen under your system settings. Disable local reminders in Casebook Settings or revoke notification permission in system settings.
Backups, exports, and sharing
An encrypted .casebook archive can contain the complete workspace, attached photos, and patients in Recently Deleted. You choose a passphrase and destination. The developer does not receive or recover that passphrase. Temporary archive files are encrypted; the app attempts to remove them when they are released.
CSV backups and analysis exports are unencrypted. A CSV backup includes patient identity and text records, but not photo bytes. Analysis exports can omit designated identity fields; this does not remove identifying free text, captions, or other details. Image exports and copies shared to other apps leave Casebook's encrypted storage. Review every export and destination before sharing.
Files saved to iCloud Drive, Photos, or another service may upload or synchronize according to that service's settings. The recipients and services you choose control their copies. Casebook does not automatically send exports to the developer.
Retention and deletion
Records remain until you change or delete them. Deleting a patient moves that patient and attached photos to Recently Deleted, where they remain until you restore or permanently delete them. Use Settings → Recently Deleted → Delete permanently to remove that patient from the saved workspace. The app attempts to remove associated encrypted photo files; failed file cleanup can leave encrypted files in local app storage. Undo and unsaved drafts may retain a previous edit during the current app session.
Deleting data in Casebook does not erase original photos, previously exported archives or CSVs, copies in Photos or Files, backups, or information you shared. Remove those separately. Removing the app executable on a Mac does not necessarily remove its local storage. The developer has no remote copy of your workspace and cannot restore lost records or encryption keys.
Apple diagnostics
Apple may share diagnostics and usage statistics according to your sharing settings. Any reports we receive are used to improve reliability. See Apple's App Analytics & Privacy notice (https://www.apple.com/legal/privacy/data/en/app-analytics/).
Support and privacy requests
Contact Sansar Gupta at sansargupta10@gmail.com. If you email us, we receive your email address, message, and any attachments you choose to send; your email provider also handles that correspondence. We use it to respond and investigate the issue, and retain it only as long as needed for those purposes or applicable legal obligations. You may contact the same address to request access, correction, or deletion of correspondence we hold.
Do not send patient identifiers, identifiable clinical screenshots, scans, photographs, or medical records through ordinary support email or public GitHub issues. We cannot retrieve or remotely delete app data stored only on your device.
Visiting this policy online
This policy page contains no advertising, analytics scripts, or cookies added by the developer. When hosted on GitHub Pages, GitHub logs visitors' IP addresses for security. See GitHub's privacy statement (https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement).
Changes to this policy
We will update this policy and its date when our data practices change. The current policy will be available with the app and on its published privacy page.