
Effective 19 October 2026 · Last updated 19 October 2026
ECA Communications is a tool for clinical staff. It is not a patient-facing application and there is nothing in it for a patient to sign up for. It shows a doctor or nurse the messages that patients left for them by phone, and it records who opened what.
We do not sell information, we do not advertise, and we do not track anyone across other apps or websites. Notifications never contain patient information.
The ECA Communications application is operated by ECA Communications LLC for the medical practices that use it. This policy explains how the application handles two different kinds of information: information about you, the member of clinical staff who signs in, and the patient information that the application displays to you.
Under the U.S. Health Insurance Portability and Accountability Act (HIPAA), the medical practice is the covered entity and ECA Communications acts as its business associate. The practice decides what patient information is collected, who may see it, and how long it is kept. We process that information on the practice's instructions and under a Business Associate Agreement with it.
This policy does not describe your rights over your own medical information, and we are not the right people to ask. Your rights under HIPAA — to see your records, to ask for a correction, to know who your information was disclosed to — are exercised through the medical practice that treats you. Please contact the practice directly. Its Notice of Privacy Practices governs your information.
Your account is created for you by an administrator at the practice. You cannot register yourself, and the application has no public sign-up.
| What | Why |
|---|---|
| First and last name | To show who wrote a note in a team chat and who opened a message |
| Work e-mail address | Your sign-in identity, and where access and recovery mail is sent |
| Phone number (optional) | So colleagues can reach you. You can leave it blank or remove it |
| Password and second factor | Held by Amazon Cognito, not by us. We never see or store your password |
| Session records | When you signed in, from what kind of device, when you were last active — so you and your administrator can end a session you no longer recognise |
| Push notification token | An anonymous identifier your phone's operating system issues, so an alert can reach that device. It is tied to one session and removed when the session ends |
| Access records | Every patient message you open and every search you run. Required by HIPAA, and explained in section 6 |
When a patient calls the practice, an automated voice agent handles the call and the conversation is transcribed. From that transcript, the system works out what the call was about and who it should reach, and creates a message.
A message can contain the patient's name, their date of birth, a callback number, what they were calling about, and the details the call provided — for example a medication and pharmacy for a refill request. The application shows this to the staff who are assigned to the chat the message was published to.
The patient's identity is unverified. Names and dates of birth come from what was said out loud on a phone call, not from the practice's medical record. The application labels them as such.
Only the transcript is used. The system deliberately ignores the structured fields the voice platform produces, because they proved unreliable. Nothing in the application depends on them.
When a new message is waiting, the application can send a notification to your phone. That notification never contains patient information. It carries the name of the chat and a count, and nothing else:
Dr. Gupta
2 new messages
This is deliberate. A push notification travels through Apple's and Google's notification services, and those services do not sign Business Associate Agreements for this purpose. Because the notification carries no patient information, nothing protected passes through them. The detail is read inside the application, behind your sign-in, and that access is recorded.
You can turn notifications off at any time in your device settings or from the account screen in the application. Doing so does not stop messages from arriving in your chats; it only stops the alert.
All information is held on Amazon Web Services in the United States, in a cloud account that belongs to this service and is covered by a Business Associate Agreement with AWS.
A session ends after 72 hours without use, and in any case after 14 days. On a phone, the application also locks behind Face ID, Touch ID or your device biometric when you reopen it or return to it, and it hides its contents in the app switcher. You or an administrator can end any session immediately, which also stops notifications to that device.
Access is not granted by job title. It is granted by membership of a specific chat: you see the messages published to the chats you belong to, and no others. The database itself enforces this, not only the application.
Every time a patient message is opened, and every time a search is run against patient information, the system writes a record of it. That record holds who did it, what action it was, which message or chat it concerned, the search criterion when there was one, and when it happened. These records cannot be edited or deleted by anyone, including the database owner.
Administrative staff who review how calls were classified work from a screen that shows the call type, the confidence score and the call identifier. That screen does not read patient information at all.
| What | How long |
|---|---|
| Patient information in a message | The period the medical practice sets. It is then purged |
| The operational record of a message | Kept after the patient information is purged, with no patient data in it, so historical reporting stays intact |
| Raw call data received from the voice platform | 30 days, encrypted |
| Call data that could not be interpreted | 90 days, encrypted, so a person can look at it |
| Access and audit records | Six years, as HIPAA requires |
| Your sessions | 14 days at most; sooner if idle or ended |
| Your account | Until the practice closes it. Closing it ends access immediately and keeps the audit trail |
We do not sell information and we do not share it for advertising. The only parties that handle information at all are these:
We may also disclose information when the law requires it, or to protect the safety of a person. If we are ever required to hand over patient information, we tell the medical practice unless the law forbids it.
ECA Communications is a workplace tool for clinical staff. It is not directed to children, and we do not knowingly create accounts for anyone under 18. Patient information shown in the application may of course concern a patient of any age; that information is governed by the medical practice's own privacy notice.
If this policy changes in a way that affects how information is handled, we will update the date at the top and, where the change is significant, tell users inside the application before it takes effect.
For questions about this policy or about how the application handles information, write to privacy@ecaconnect.com.
If you are a patient asking about your own medical information, please contact the medical practice that treats you. We cannot act on your records without them.