Privacy
Notice of Privacy Practices
How bellwiQ uses and discloses the information it handles, and the rights you have over it.
In short
- We sign a Business Associate Agreement with your practice before any chart is touched.
- The plugin records only between Record and Stop, in an eCW chart you have open.
- Audio and notes are used only to write your notes. They are never sold, never used for advertising, and not used to train any model.
- bellwiQ works through one eCW user with scribe rights only. Every entry it makes is in your eCW audit log under its own name.
- When a practice leaves, its patient data is returned or destroyed.
This Notice of Privacy Practices describes how bellwiQ may use and disclose your information and the rights that you have regarding your health information. We at Bellwiq Health, Inc. (“we”, “us”, “bellwiQ”) value your privacy and are committed to keeping your personal data confidential. We use your data solely in the context of providing the bellwiQ Chrome plugin and the services behind it (the “Platform”) and all of its content and functionality (collectively, the “Services”) for use by physicians and nurse practitioners (“Provider users”) in the care of their patients (“Patients”). You are either a Provider user or a Patient. If you are visiting this website, see Part 05.
Provider users
If you are a provider.
We collect information about you solely to authenticate your access to the Platform and to attach each recording to the right chart: your name, your work email, and the practice and user IDs that eClinicalWorks assigns to you.
We also keep the difference between each draft and the note you sign, so we can show you your edit rate and propose rules for your notes, which you approve. No other information about you is accessed, stored or used for any other purpose.
Your voice is part of the visit recording. The recording is handled as patient information, under Part 03.
Patients
If you are a patient.
Patient information, including the audio of the visit and the chart information bellwiQ reads to write the note, is fully governed by a Business Associate Agreement signed between your provider's practice (“Covered Entity”) and bellwiQ (“Business Associate”), described in full in Part 03.
Your provider's practice controls your record. To see, correct or ask about your information, contact the practice. If a request reaches us, we forward it to them within ten business days.
BAA
The Business Associate Agreement.
The agreement we sign with every practice before any chart is touched.
This BUSINESS ASSOCIATE AGREEMENT (the “BAA”) is made and entered into by Bellwiq Health, Inc., a Texas corporation (“Business Associate”), and the counterparty set forth in the Service Agreement into which this BAA is incorporated by reference (“Covered Entity”), and is effective as of the Service Start Date (the “Effective Date”). In this BAA, Covered Entity and Business Associate are each a “Party” and, collectively, are the “Parties”.
Background
- Covered Entity is either a “covered entity” or “business associate” of a covered entity as each are defined under the Health Insurance Portability and Accountability Act of 1996, Public Law 104-191, as amended by the HITECH Act (as defined below) and the related regulations promulgated by HHS (as defined below) (collectively, “HIPAA”) and, as such, is required to comply with HIPAA's provisions regarding the confidentiality and privacy of Protected Health Information (as defined below);
- The Parties have entered into or will enter into one or more agreements under which Business Associate provides or will provide certain specified services to Covered Entity (collectively, the “Agreement”);
- In providing services pursuant to the Agreement, Business Associate will have access to Protected Health Information;
- By providing the services pursuant to the Agreement, Business Associate will become a “business associate” of the Covered Entity as such term is defined under HIPAA;
- Both Parties are committed to complying with all federal and state laws governing the confidentiality and privacy of health information, including, but not limited to, the Standards for Privacy of Individually Identifiable Health Information found at 45 CFR Part 160 and Part 164, Subparts A and E (collectively, the “Privacy Rule”); and
- Both Parties intend to protect the privacy and provide for the security of Protected Health Information disclosed to Business Associate pursuant to the terms of this Agreement, HIPAA and other applicable laws.
NOW, THEREFORE, in consideration of the mutual covenants and conditions contained herein and the continued provision of PHI by Covered Entity to Business Associate under the Agreement in reliance on this BAA, the Parties agree as follows:
1Definitions
For purposes of this BAA, the Parties give the following meaning to each of the terms in this Section 1 below. Any capitalized term used in this BAA, but not otherwise defined, has the meaning given to that term in the Privacy Rule or pertinent law.
- Affiliate
- means a subsidiary or affiliate of Covered Entity that is, or has been, considered a covered entity, as defined by HIPAA.
- Breach
- means the acquisition, access, use, or disclosure of PHI in a manner not permitted under the Privacy Rule which compromises the security or privacy of the PHI, as defined in 45 CFR §164.402.
- Breach Notification Rule
- means the portion of HIPAA set forth in Subpart D of 45 CFR Part 164.
- Data Aggregation
- means, with respect to PHI created or received by Business Associate in its capacity as the “business associate” under HIPAA of Covered Entity, the combining of such PHI by Business Associate with the PHI received by Business Associate in its capacity as a business associate of one or more other “covered entity” under HIPAA, to permit data analyses that relate to the Health Care Operations (defined below) of the respective covered entities. The meaning of “data aggregation” in this BAA shall be consistent with the meaning given to that term in the Privacy Rule.
- Designated Record Set
- has the meaning given to such term under the Privacy Rule, including 45 CFR §164.501.
- De-Identify
- means to alter the PHI such that the resulting information meets the requirements described in 45 CFR §§164.514(a) and (b).
- Electronic PHI
- means any PHI maintained in or transmitted by electronic media as defined in 45 CFR §160.103.
- Health Care Operations
- has the meaning given to that term in 45 CFR §164.501.
- HHS
- means the U.S. Department of Health and Human Services.
- HITECH Act
- means the Health Information Technology for Economic and Clinical Health Act, enacted as part of the American Recovery and Reinvestment Act of 2009, Public Law 111-005.
- Individual
- has the same meaning given to that term in 45 CFR §§164.501 and 160.103 and includes a person who qualifies as a personal representative in accordance with 45 CFR §164.502(g).
- Privacy Rule
- means that portion of HIPAA set forth in 45 CFR Part 160 and Part 164, Subparts A and E.
- Protected Health Information or PHI
- has the meaning given to the term “protected health information” in 45 CFR §§164.501 and 160.103, limited to the information created or received by Business Associate from or on behalf of Covered Entity, including audio recordings of patient visits.
- Security Incident
- means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.
- Security Rule
- means the Security Standards for the Protection of Electronic Health Information provided in 45 CFR Part 160 and Part 164, Subparts A and C.
- Unsecured Protected Health Information or Unsecured PHI
- means any “protected health information” as defined in 45 CFR §§164.501 and 160.103 that is not rendered unusable, unreadable or indecipherable to unauthorized individuals through the use of a technology or methodology specified by the HHS Secretary in the guidance issued pursuant to the HITECH Act and codified at 42 USC §17932(h).
2Use and Disclosure of PHI
- Except as otherwise provided in this BAA, Business Associate may use or disclose PHI as reasonably necessary to provide the services described in the Agreement to Covered Entity, and to undertake other activities of Business Associate permitted or required of Business Associate by this BAA or as required by law.
- Except as otherwise limited by this BAA or federal or state law, Covered Entity authorizes Business Associate to use the PHI in its possession for the proper management and administration of Business Associate's business and to carry out its legal responsibilities. Business Associate may disclose PHI for its proper management and administration, provided that (i) the disclosures are required by law; or (ii) Business Associate obtains, in writing, prior to making any disclosure to a third party (a) reasonable assurances from this third party that the PHI will be held confidential as provided under this BAA and used or further disclosed only as required by law or for the purpose for which it was disclosed to this third party and (b) an agreement from this third party to notify Business Associate immediately of any breaches of the confidentiality of the PHI, to the extent it has knowledge of the breach.
- Business Associate will not use or disclose PHI in a manner other than as provided in this BAA, as permitted under the Privacy Rule, or as required by law. Business Associate will use or disclose PHI, to the extent practicable, as a limited data set or limited to the minimum necessary amount of PHI to carry out the intended purpose of the use or disclosure, in accordance with Section 13405(b) of the HITECH Act (codified at 42 USC §17935(b)) and any of the act's implementing regulations adopted by HHS, for each use or disclosure of PHI.
- Upon request, Business Associate will make available to Covered Entity any of Covered Entity's PHI that Business Associate or any of its agents or subcontractors have in their possession.
- Business Associate may use PHI to report violations of law to appropriate Federal and State authorities, consistent with 45 CFR §164.502(j)(1).
- Business Associate will not sell PHI, will not use PHI for advertising or marketing, and will not use PHI, including audio recordings of patient visits, to train any machine learning model.
3Safeguards Against Misuse of PHI
Business Associate will use appropriate safeguards to prevent the use or disclosure of PHI other than as provided by the Agreement or this BAA and Business Associate agrees to implement administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity and availability of the Electronic PHI that it creates, receives, maintains or transmits on behalf of Covered Entity. Business Associate agrees to take reasonable steps, including providing adequate training to its employees to ensure compliance with this BAA and to ensure that the actions or omissions of its employees or agents do not cause Business Associate to breach the terms of this BAA.
4Reporting Disclosures of PHI and Security Incidents
Business Associate will report to Covered Entity in writing any use or disclosure of PHI not provided for by this BAA of which it becomes aware and Business Associate agrees to report to Covered Entity any Security Incident affecting Electronic PHI of Covered Entity of which it becomes aware. Business Associate agrees to report any such event within five business days of becoming aware of the event.
5Reporting Breaches of Unsecured PHI
Business Associate will notify Covered Entity in writing promptly upon the discovery of any Breach of Unsecured PHI in accordance with the requirements set forth in 45 CFR §164.410, but in no case later than 30 calendar days after discovery of a Breach. Business Associate will reimburse Covered Entity for any costs incurred by it in complying with the requirements of Subpart D of 45 CFR Part 164 that are imposed on Covered Entity as a result of a Breach committed by Business Associate.
6Mitigation of Disclosures of PHI
Business Associate will take reasonable measures to mitigate, to the extent practicable, any harmful effect that is known to Business Associate of any use or disclosure of PHI by Business Associate or its agents or subcontractors in violation of the requirements of this BAA.
7Agreements with Agents or Subcontractors
Business Associate will ensure that any of its agents or subcontractors that have access to, or to which Business Associate provides, PHI agree in writing to the restrictions and conditions concerning uses and disclosures of PHI contained in this BAA and agree to implement reasonable and appropriate safeguards to protect any Electronic PHI that it creates, receives, maintains or transmits on behalf of Business Associate or, through the Business Associate, Covered Entity. Business Associate shall notify Covered Entity in writing of all subcontracts and agreements relating to the Agreement where the subcontractor or agent receives PHI as described in Section 1 of this BAA, within 30 calendar days of the execution of the subcontract. Business Associate shall ensure that all subcontracts and agreements provide the same level of privacy and security as this BAA.
8Security Documentation
Upon request, Business Associate will provide Covered Entity with a written summary of its most recent security risk analysis under 45 CFR §164.308(a)(1) and of the administrative, physical and technical safeguards it maintains. Covered Entity agrees not to re-disclose that summary.
9Access to PHI by Individuals
- Upon request, Business Associate agrees to furnish Covered Entity with copies of the PHI maintained by Business Associate in a Designated Record Set in the time and manner designated by Covered Entity to enable Covered Entity to respond to an Individual's request for access to PHI under 45 CFR §164.524.
- In the event any Individual or personal representative requests access to the Individual's PHI directly from Business Associate, Business Associate within ten business days, will forward that request to Covered Entity. Any disclosure of, or decision not to disclose, the PHI requested by an Individual or a personal representative and compliance with the requirements applicable to an Individual's right to obtain access to PHI shall be the sole responsibility of Covered Entity.
10Amendment of PHI
- Upon request and instruction from Covered Entity, Business Associate will amend PHI or a record about an Individual in a Designated Record Set that is maintained by, or otherwise within the possession of, Business Associate as directed by Covered Entity in accordance with procedures established by 45 CFR §164.526. Any request by Covered Entity to amend such information will be completed by Business Associate within 15 business days of Covered Entity's request.
- In the event that any Individual requests that Business Associate amend such Individual's PHI or record in a Designated Record Set, Business Associate within ten business days will forward this request to Covered Entity. Any amendment of, or decision not to amend, the PHI or record as requested by an Individual and compliance with the requirements applicable to an Individual's right to request an amendment of PHI will be the sole responsibility of Covered Entity.
11Accounting of Disclosures
- Business Associate will document any disclosures of PHI made by it to account for such disclosures as required by 45 CFR §164.528(a). Business Associate also will make available information related to such disclosures as would be required for Covered Entity to respond to a request for an accounting of disclosures in accordance with 45 CFR §164.528. At a minimum, Business Associate will furnish Covered Entity the following with respect to any covered disclosures by Business Associate: (i) the date of disclosure of PHI; (ii) the name of the entity or person who received PHI, and, if known, the address of such entity or person; (iii) a brief description of the PHI disclosed; and (iv) a brief statement of the purpose of the disclosure which includes the basis for such disclosure.
- Business Associate will furnish to Covered Entity information collected in accordance with this Section 11, within ten business days after written request by Covered Entity, to permit Covered Entity to make an accounting of disclosures as required by 45 CFR §164.528, or in the event that Covered Entity elects to provide an Individual with a list of its business associates, Business Associate will provide an accounting of its disclosures of PHI upon request of the Individual, if and to the extent that such accounting is required under the HITECH Act or under HHS regulations adopted in connection with the HITECH Act.
- In the event an Individual delivers the initial request for an accounting directly to Business Associate, Business Associate will within ten business days forward such request to Covered Entity.
12Availability of Books and Records
Business Associate will make available its internal practices, books, agreements, records, and policies and procedures relating to the use and disclosure of PHI, upon request, to the Secretary of HHS for purposes of determining Covered Entity's and Business Associate's compliance with HIPAA, and this BAA.
13Responsibilities of Covered Entity
With regard to the use and/or disclosure of Protected Health Information by Business Associate, Covered Entity agrees to:
- Notify Business Associate of any limitation(s) in its notice of privacy practices in accordance with 45 CFR §164.520, to the extent that such limitation may affect Business Associate's use or disclosure of PHI.
- Notify Business Associate of any changes in, or revocation of, permission by an Individual to use or disclose Protected Health Information, to the extent that such changes may affect Business Associate's use or disclosure of PHI.
- Notify Business Associate of any restriction to the use or disclosure of PHI that Covered Entity has agreed to in accordance with 45 CFR §164.522, to the extent that such restriction may affect Business Associate's use or disclosure of PHI.
- Except for data aggregation or management and administrative activities of Business Associate, Covered Entity shall not request Business Associate to use or disclose PHI in any manner that would not be permissible under HIPAA if done by Covered Entity.
14Data Ownership
Business Associate's data stewardship does not confer data ownership rights on Business Associate with respect to any data shared with it under the Agreement, including any and all forms thereof.
15Term and Termination
- This BAA will become effective on the Effective Date and will continue in effect until all obligations of the Parties have been met under the Agreement and under this BAA.
- Covered Entity may terminate immediately this BAA, the Agreement, and any other related agreements if Covered Entity makes a determination that Business Associate has breached a material term of this BAA and Business Associate has failed to cure that material breach, to Covered Entity's reasonable satisfaction, within 30 days after written notice from Covered Entity. Covered Entity may report the problem to the Secretary of HHS if termination is not feasible.
- If Business Associate determines that Covered Entity has breached a material term of this BAA, then Business Associate will provide Covered Entity with written notice of the existence of the breach and shall provide Covered Entity with 30 days to cure the breach. Covered Entity's failure to cure the breach within the 30-day period will be grounds for immediate termination of the Agreement and this BAA by Business Associate. Business Associate may report the breach to HHS.
- Upon termination of the Agreement or this BAA for any reason, all PHI maintained by Business Associate will be returned to Covered Entity or destroyed by Business Associate. Business Associate will not retain any copies of such information. This provision will apply to PHI in the possession of Business Associate's agents and subcontractors. If return or destruction of the PHI is not feasible, in Business Associate's reasonable judgment, Business Associate will furnish Covered Entity with notification, in writing, of the conditions that make return or destruction infeasible. Upon mutual agreement of the Parties that return or destruction of the PHI is infeasible, Business Associate will extend the protections of this BAA to such information for as long as Business Associate retains such information and will limit further uses and disclosures to those purposes that make the return or destruction of the information not feasible. The Parties understand that this Section 15.D will survive any termination of this BAA.
16Effect of BAA
- This BAA is a part of and subject to the terms of the Agreement, except that to the extent any terms of this BAA conflict with any term of the Agreement, the terms of this BAA will govern.
- Except as expressly stated in this BAA or as provided by law, this BAA will not create any rights in favor of any third party.
17Regulatory References
A reference in this BAA to a section in HIPAA means the section as in effect or as amended at the time.
18Notices
All notices that either Party may desire or be required to give to the other will be in writing and will be delivered personally, by electronic mail, or nationally recognized overnight courier to the other Party at the address set forth in the Agreement or such other address as a Party may provide. Notice delivered by e-mail will be confirmed by overnight courier or by priority mail.
19Amendments and Waiver
This BAA may not be modified, nor will any provision be waived or amended, except in writing duly signed by authorized representatives of the Parties. A waiver with respect to one event shall not be construed as continuing, or as a bar to or waiver of any right or remedy as to subsequent events.
20HITECH Act Compliance
The Parties acknowledge that the HITECH Act includes significant changes to the Privacy Rule and the Security Rule. The privacy subtitle of the HITECH Act sets forth provisions that significantly change the requirements for business associates and the agreements between business associates and covered entities under HIPAA and these changes may be further clarified in forthcoming regulations and guidance. Each Party agrees to comply with the applicable provisions of the HITECH Act and any HHS regulations issued with respect to the HITECH Act. The Parties also agree to negotiate in good faith to modify this BAA as reasonably necessary to comply with the HITECH Act and its regulations as they become effective but, in the event that the Parties are unable to reach agreement on such a modification, either Party will have the right to terminate this BAA upon 30 days' prior written notice to the other Party.
Chrome plugin
The Chrome plugin.
This part describes how the bellwiQ Chrome plugin (the “Plugin”) collects, uses, handles, stores, shares and transmits user data. The Plugin is provided to practices that have signed a Business Associate Agreement with bellwiQ; the BAA terms governing Protected Health Information are set out in Part 03.
Purpose
The Plugin has a single purpose: to put a Record button in the eClinicalWorks chart a provider has open, and to send the visit recording to bellwiQ so the draft note can be written into that chart. It operates only on the eClinicalWorks domains declared in its manifest and has no function on any other site.
What data the Plugin accesses
The Plugin may access the following, only while a provider is using it in an eClinicalWorks chart:
- The microphone.
- Only between the moment the provider presses Record and the moment they press Stop. The Plugin does not listen at any other time, and it does not record in a tab where no chart is open.
- Active tab context.
- A read-only check of the active tab to see whether it is an eClinicalWorks chart. Tab URLs are not stored, logged, retained or transmitted to any server.
- The open chart and visit.
- The patient and visit identifiers of the chart the provider has open, so the recording belongs to that patient and that visit.
- bellwiQ sign-in.
- Used solely to authenticate the provider with bellwiQ. The provider's eClinicalWorks password is never asked for or collected.
The Plugin does not collect personally identifiable information about the provider beyond what is required to sign in. It does not access browsing history, pages outside eClinicalWorks, financial information, location data, or any data unrelated to its purpose.
bellwiQ reads the chart and writes the draft through the separate eClinicalWorks user that the practice creates for it, with scribe rights only. That user cannot sign or send claims, and every entry it makes is in the practice's eClinicalWorks audit log under its own name.
Signing in
When a provider signs in, the Plugin sends their bellwiQ sign-in details over HTTPS to bellwiQ's authentication service, solely to identify the provider and link them to their bellwiQ account. No patient data, no PHI, no eClinicalWorks password and no browsing information is sent in this step. bellwiQ returns a short-lived session token, which the Plugin uses to authenticate its uploads for the rest of the session.
How data is used
Data accessed by the Plugin is used solely to write the provider's draft note into the chart. It is never used for advertising, profiling, resale, creditworthiness determination, or any purpose unrelated to the Plugin's stated purpose.
How data is transmitted
All communication between the Plugin and bellwiQ is transmitted over HTTPS (TLS 1.2 or higher) to authenticated bellwiQ endpoints. No user data is transmitted over plain HTTP. No user data is encoded in URL query parameters or request headers. The Plugin does not perform outbound logging, and does not transmit data to any third party other than bellwiQ.
How data is stored
The Plugin keeps a recording in the browser only until it has been uploaded, and does not otherwise persist user data in browser storage, local storage, IndexedDB or cookies beyond the session state the active recording needs. Once received, audio and notes are stored on HIPAA-compliant infrastructure under the terms of the BAA between bellwiQ and the practice.
How data is shared
The Plugin does not sell user data. The Plugin does not transfer user data to third parties outside of the approved use cases described in the Chrome Web Store Developer Program Policies. The Plugin does not use or transfer user data for purposes unrelated to its stated purpose. The Plugin does not use or transfer user data to determine creditworthiness or for lending purposes.
Data retention and deletion
Visit audio is kept for 14 days after the draft note is written, then deleted. All other patient data is retained and deleted in accordance with the BAA between bellwiQ and the practice, and applicable HIPAA requirements. Practices may request deletion of their data by writing to privacy@bellwiqhealth.com.
Remote code
The Plugin does not load, execute or eval remote code. All JavaScript and Wasm shipped with the Plugin is included in its package as published to the Chrome Web Store.
Website
This website.
This website does not use cookies, analytics or advertising trackers.
Fonts are loaded from Google Fonts, so your browser sends your IP address to Google when a page loads. The site is served by Cloudflare, which processes standard request data, such as your IP address, to deliver it and protect it from abuse.
If you ask for a demo, we use your name, practice and email only to reply to you and arrange the call. We do not sell them or add them to a mailing list.
Contact
Questions and changes.
Questions about this notice, or a request to access, correct or delete data: privacy@bellwiqhealth.com.
Patients: please contact your provider's practice first. They control your record.
This Notice became effective on October 20, 2026. When it changes, we update this page and the date at the top.