Ally

iPhone app privacy

Effective October 16, 2026 · App version 1.1

This policy covers the Ally iPhone app and its clinic service, operated by Jason Lu (Ally). The app is for authorized doctors and staff at participating clinics. The clinic service provides sign-in, the clinic’s appointment schedule, visit recording with everyone’s agreement, transcription, draft treatment plans and visit notes for the doctor to review and approve, and clinical photos. Text messages to patients are not enabled on the clinic service. Designated Ally developer accounts can also use a separate service that holds only fictional data.

Information and its use

  • Account information: your name, email address, user ID, clinic, role, sign-in requests and session information. We use these to verify sign-in, restrict access to your clinic and operate your account. Sign-in uses an emailed code. The server stores hashes of codes and session tokens; the phone keeps its session token in the iOS Keychain.
  • Clinic records: patient names and identifiers, birth dates when available, appointment dates and times, providers, appointment types and visit status supplied by the clinic’s schedule integration. We use these to display the clinic’s day and match records to the correct patient and encounter.
  • Visit recordings and what is drafted from them: a visit is recorded only after everyone in the room agrees. Its audio, the transcript made from it, anything typed about the visit, and spoken or typed changes are used to draft each patient’s plan (what to use and how often) and the visit note, which the doctor reviews, changes and approves. Approved plans and notes become part of the clinic’s records.
  • Clinical photos: photos taken during a visit are filed into one PDF per patient and visit for the clinic’s records; their body sites are kept with them in Ally. The camera does not save them to your photo library.
  • Operational information: request times, IP addresses, response and error information, and an audit trail of sign-ins and record actions. We use these for access control, service operation, support and security.
  • Diagnostics: if the app crashes, freezes or receives an answer it can’t read, it sends a report: the app’s own call stack from iOS, the app and iOS versions, the device model, and for an unreadable answer the request’s route pattern and field names, never their values. Reports contain no patient details and are not linked to your account. We use them to find and fix problems.

The app has no advertising and does no cross-app tracking.

Device permissions and local storage

Face ID or the device passcode protects access to a saved session. Apple performs that check on the device; Ally does not receive Face ID templates, biometric data or your passcode. The microphone is used only to record a visit after everyone agrees, or a change you speak; the camera only for clinical photos. You can revoke either permission in iOS Settings.

Session tokens remain in the device’s Keychain and do not sync through iCloud Keychain. Preferences remain in the app’s own storage. Recordings and photos waiting to upload remain in the app’s protected local storage, separate for each server; each piece of a recording is removed from the phone once it is sent. Exporting a document through the share sheet sends it to the destination you choose, whose own privacy practices apply.

Recipients and service providers

Clinic records are available to authorized members of that clinic according to their role: only the doctor approves new or changed plans, and notes. Jason Lu may access information when needed to provide support, maintain the service, investigate a security incident or fulfill an authorized clinic request.

Amazon Web Services hosts the service, its encrypted storage and backups in the United States. AWS Simple Email Service delivers sign-in emails; your email provider receives those emails too. Sign-in emails contain no patient schedule or clinical information.

Deepgram processes visit audio and spoken changes to transcribe them, and Anthropic processes transcripts, typed information and requested changes to draft plans and notes. They process this information on Ally’s behalf to provide these functions only. Text messages to patients are not enabled on the clinic service.

We do not sell data or use it for advertising, data brokerage, creditworthiness or lending decisions, and we do not use it to train AI models. Service information is used to provide and protect Ally’s stated functions. We may disclose information when legally required or when necessary to address fraud or a security incident.

Retention, deletion and your choices

A visit’s audio is deleted from the service once its plans are approved or discarded, and after 7 days at most. A transcript is deleted 30 days after its visit once no draft remains. Approved plans, notes and photo PDFs remain part of the clinic’s records.

Signing out removes the phone’s saved session for that server and ends that session on the service. Uninstalling the app removes its ordinary local files; it does not delete the clinic’s records or necessarily erase Keychain items. Clinic records remain available to the clinic until an authorized deletion is performed, subject to applicable record-retention requirements. Backups expire according to their retention schedule, so deletion from the active service does not immediately erase every older backup.

Ask your clinic or contact jasonlu.software@gmail.com to request access, correction, export, account closure or deletion. We verify your authority and coordinate requests for clinical records with the clinic. If a retention requirement prevents deletion, we explain that requirement. Avoid patient details in ordinary support email.

Contact and changes

For privacy questions, contact Jason Lu at jasonlu.software@gmail.com. This policy is available without sign-in, from the app’s sign-in screen and from the Today menu. Material changes appear in an updated policy and, when required, in a disclosure before the changed handling begins.