Skip to content
Nicole Kolenda, Voice for Possibility
  • Home
  • About
    • NYU Motor Speech LabOur research and current studies
    • What is DTTC?The treatment we study, explained
  • Speaking
  • Podcast
    • BlogNotes for parents and SLPs
    • VideosQuick tips, with transcripts
    • Documents & toolsFree screeners, charts and guides
  • Connect

Privacy & legal

Connecting the Dots Pro

Business Associate Agreement

Version 2026-11-11 · Effective November 11, 2026

All privacy and legal documents

The short version

  • This is the HIPAA Business Associate Agreement between your practice and us for Connecting the Dots Pro. Your clinic owner accepts it in the app on the practice’s behalf.
  • We use the client information your practice enters only to run the Service for you and as the law requires. We never sell it, use it for marketing or use it to train AI models.
  • We protect it as the HIPAA Security Rule requires. Every user signs in with multi-factor authentication, data is encrypted, access is limited by role, and an audit log records every sign-in and every change.
  • If something goes wrong, we tell you without unreasonable delay and no later than 10 business days after we discover it, with the details you need to notify families.
  • You decide who has access and what is entered. Identify children by initials or a nickname. Never enter full names, Social Security numbers, insurance details or contact details.
  • When your account closes, you have 30 days to export your records. Then we delete them from the live Service, and backup copies expire within 35 days.
  • If this Agreement and our Terms of Service disagree about protected health information, this Agreement controls.
  1. Parties, acceptance and scope
  2. Definitions
  3. Our obligations
  4. How we may use and disclose PHI
  5. The Practice’s obligations
  6. Term and termination
  7. Time limits at a glance
  8. General terms
  9. Acceptance

1. Parties, acceptance and scope

1.1 The parties. This Business Associate Agreement (the “Agreement”) is between:

  • Nicole Kolenda, Voice For Possibility, 92 Carlton Terrace, Stewart Manor, NY 11530, USA (“we”, “us” or “our”), as business associate; and
  • the health care practice whose clinic owner accepts this Agreement in Connecting the Dots Pro on the practice’s behalf (the “Practice” or “you”), as covered entity.

1.2 Why this Agreement exists. When the Practice uses the Service, we create, receive, maintain and transmit protected health information on the Practice’s behalf. That makes us the Practice’s business associate under the HIPAA Rules. This Agreement gives the Practice the written assurances that 45 CFR 164.502(e), 164.504(e), 164.308(b) and 164.314(a) require.

1.3 Acceptance. The Practice’s clinic owner accepts this Agreement electronically inside the Service. The owner enters the Practice’s legal name and their own name and title, confirms that they are authorized to bind the Practice, and clicks Accept. Section 9 describes what we record. The acceptance is the Practice’s signature (Section 8.11).

1.4 Effective date. This Agreement takes effect for the Practice at the moment its clinic owner accepts it. The Service does not let a clinic add a child until this Agreement has been accepted.

1.5 Scope. This Agreement applies to all PHI that we create, receive, maintain or transmit on behalf of the Practice through the Service, wherever we hold it, including in backups and the audit log. We treat all client information in the Service as PHI, even though the Service identifies children only by initials or a nickname.

1.6 If the Practice is itself a business associate. If the Practice uses the Service to serve another covered entity as that entity’s business associate, this Agreement also serves as the subcontractor agreement required by 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2), and we act as the Practice’s subcontractor. If the Practice is not subject to HIPAA, we will still keep every commitment in this Agreement as a contractual promise.

2. Definitions

2.1 Terms defined in the HIPAA Rules. The capitalized terms below have the meanings given to them in the HIPAA Rules (45 CFR Parts 160 and 164). In this Agreement, “PHI” means only PHI that we create, receive, maintain or transmit on behalf of the Practice.

Term Where it is defined
Breach45 CFR 164.402
Data Aggregation45 CFR 164.501
Designated Record Set45 CFR 164.501
Disclosure45 CFR 160.103
Electronic Protected Health Information (electronic PHI)45 CFR 160.103
Health Care Operations45 CFR 164.501
Individual45 CFR 160.103 (including a person who qualifies as a personal representative under 45 CFR 164.502(g), such as a child’s parent)
Marketing45 CFR 164.501
Minimum Necessary45 CFR 164.502(b) and 164.514(d)
Notice of Privacy Practices45 CFR 164.520
Protected Health Information (PHI)45 CFR 160.103
Required by Law45 CFR 164.103
Secretary45 CFR 160.103 (the Secretary of the U.S. Department of Health and Human Services or a delegate)
Security Incident45 CFR 164.304
Subcontractor45 CFR 160.103
Unsecured Protected Health Information (Unsecured PHI)45 CFR 164.402
Use45 CFR 160.103

2.2 Other terms.

  • “Agreement” means this Business Associate Agreement, version 2026-11-11, as accepted by the Practice, together with any later version the Practice accepts under Section 8.2.
  • “HIPAA Rules” means the Privacy, Security, Breach Notification and Enforcement Rules at 45 CFR Part 160 and Part 164.
  • “Privacy Rule” means Subpart E of 45 CFR Part 164, and “Security Rule” means Subpart C of 45 CFR Part 164.
  • “Service” means Connecting the Dots Pro, at app.nicolekolenda.com with sign-in at login.nicolekolenda.com, in which clinicians plan motor-speech treatment for a child, log session trials, and keep plan versions and comments. It includes the systems, backups and logs we use to run it.
  • “Clinic owner” means the person who holds the owner role for the Practice’s clinic in the Service. We create each clinic, and the clinic owner invites the Practice’s staff.
  • “Business day” means Monday through Friday, excluding U.S. federal holidays.
  • “Terms of Service” means the Connecting the Dots Pro Terms of Service, and “Privacy Policy” means the Connecting the Dots Pro Privacy Policy.

3. Our obligations

3.1 Use and disclosure. We will not use or disclose PHI other than as permitted or required by this Agreement or as Required by Law.

3.2 Safeguards. We will use appropriate administrative, physical and technical safeguards, and comply with the Security Rule with respect to electronic PHI, to prevent use or disclosure of PHI other than as provided for by this Agreement.

3.3 Safeguards in place today. The table below describes the main safeguards in place on the date of this version. We may change specific measures over time, but only to measures that give at least the same level of protection.

Area What we do
HostingAmazon Web Services (AWS) in the United States (us-east-1, Northern Virginia), using HIPAA-eligible services covered by AWS’s business associate agreement, in a separate production account.
Sign-inMulti-factor authentication for every user, with a code from an authenticator app.
Access controlEnforced on the server, by role: the clinic owner, the child’s clinician and the child’s mentors.
EncryptionIn transit with TLS. At rest with AES-256, using a customer-managed key.
BackupsPoint-in-time recovery backups, kept for up to 35 days.
Audit logAn append-only log of every sign-in and every change: who, what, when and a random record number, with no client names. Each export is logged. The log is kept for at least six years.
Session time-outAutomatic sign-out after 45 minutes of inactivity.
System logsNever contain request contents or names.
EmailInvitation and password emails contain no client information.
PDFsCreated in the user’s own browser, on the user’s device.

3.4 What we report. We will report to the Practice:

  1. any use or disclosure of PHI not provided for by this Agreement of which we become aware;
  2. any Breach of Unsecured PHI, as required by 45 CFR 164.410; and
  3. any Security Incident of which we become aware, subject to Section 3.7.

3.5 When we report. We will make each report without unreasonable delay and no later than 10 business days after discovery. A Breach is treated as discovered on the first day it is known to us, or, by exercising reasonable diligence, would have been known to us or to any of our workforce members or agents other than the person who committed it (45 CFR 164.410(a)(2)). In no case will we report later than the 60-calendar-day maximum in 45 CFR 164.410(b). If a state law requires us to notify the Practice sooner, we will do so within the time that law requires. If we do not yet have all the information listed in Section 3.6, we will send what we have and follow up as we learn more. If a law enforcement official tells us that a notice would impede a criminal investigation or damage national security, we may delay as 45 CFR 164.412 allows, and we will tell the Practice as soon as we are permitted to.

3.6 What a Breach report contains. A report of a Breach of Unsecured PHI will include, to the extent the information is available to us:

  1. the identification of each Individual whose Unsecured PHI has been, or is reasonably believed by us to have been, accessed, acquired, used or disclosed during the Breach. Because the Service identifies children by initials or a nickname, we will identify each child by the details stored in the Service, and the Practice will match those details to the children it serves;
  2. a brief description of what happened, including the date of the Breach and the date of discovery, if known;
  3. a description of the types of PHI involved;
  4. what we are doing to investigate the Breach, to mitigate harm and to protect against further Breaches;
  5. any steps we suggest Individuals take to protect themselves;
  6. a person the Practice can contact for more information; and
  7. any other information the Practice needs to include in its notice to Individuals under 45 CFR 164.404(c).

Information that is not available at the time of the report will be provided promptly as it becomes available (45 CFR 164.410(c)).

3.7 Unsuccessful Security Incidents. The parties agree that this section is notice, and that no further report is required, of the ongoing existence and occurrence of attempted but unsuccessful Security Incidents. These include pings and other broadcast attacks on our firewall, port scans, unsuccessful log-in attempts, and similar events, or any combination of them, as long as none of them results in unauthorized access to, or use, disclosure, modification or destruction of, PHI, or interference with the operation of the Service’s information systems.

3.8 Notifying Individuals, the Secretary and the media. As the covered entity, the Practice decides whether notification is required and gives any notices to affected Individuals, the Secretary and, where required, the media under 45 CFR 164.404 to 164.408. We will not give those notices about the Practice’s PHI ourselves unless the Practice asks us to in writing and we agree, or the law requires us to. We will cooperate with the Practice’s investigation and give it the information it reasonably needs.

3.9 Mitigation. We will mitigate, to the extent practicable, any harmful effect known to us of a use or disclosure of PHI by us or our Subcontractors in violation of this Agreement.

3.10 Subcontractors. In accordance with 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2), we will ensure that any Subcontractor that creates, receives, maintains or transmits PHI on our behalf agrees in writing to the same restrictions, conditions and requirements that apply to us under this Agreement with respect to that PHI, including compliance with the Security Rule (45 CFR 164.314(a)). Our only Subcontractor today is Amazon Web Services, with which we have a business associate agreement. Cloudflare provides domain name (DNS) service only. It does not carry the Service’s traffic or data, so it is not a Subcontractor. Before any new Subcontractor handles PHI, we will have a written agreement with it that meets this section, and we will tell the Practice under Section 8.7.

3.11 Access. The Practice can provide access under 45 CFR 164.524 itself: the clinic owner can create a record export of everything the Service stores about a child. If the Practice needs our help to respond to a request for access, we will make the PHI in a Designated Record Set available to the Practice within 15 days of its written request, in a form that allows the Practice to meet its obligations under 45 CFR 164.524.

3.12 Amendment. The Practice’s users can correct and add to a child’s records directly in the Service. If the Practice needs our help to make an amendment under 45 CFR 164.526, we will make it, or help the Practice make it, within 15 days of its written request.

3.13 Accounting of disclosures. We will document each disclosure of PHI we make that the Practice would need to include in an accounting under 45 CFR 164.528 (for example, a disclosure Required by Law). Within 15 days of the Practice’s written request, we will give it the information it needs for the accounting: the date of the disclosure, the name of the recipient and their address if known, a brief description of the PHI disclosed, and a brief statement of the purpose. We will keep this information for six years from the date of each disclosure.

3.14 Requests sent to us directly. If an Individual, or a parent or other representative, asks us directly for access, amendment or an accounting, we will forward the request to the Practice promptly. We will not respond to the request ourselves unless the Practice directs us to or the law requires us to.

3.15 Carrying out the Practice’s obligations. To the extent we carry out any of the Practice’s obligations under the Privacy Rule, we will comply with the requirements of the Privacy Rule that apply to the Practice in the performance of that obligation.

3.16 Books and records. We will make our internal practices, books and records relating to the use and disclosure of PHI available to the Secretary for purposes of determining compliance with the HIPAA Rules. Unless the law forbids it, we will tell the Practice when we receive such a request.

3.17 Our staff. Our staff do not look at client information except to support the Practice at its request, to keep the Service secure, or as Required by Law. When they do, they look at only the minimum necessary.

3.18 State laws. State data-breach and data-security laws, such as New York’s SHIELD Act (General Business Law §899-aa on breach notification and §899-bb on data security), may also apply to an incident involving the Practice’s information. We will give the Practice the information it reasonably needs to meet its obligations under those laws.

4. How we may use and disclose PHI

4.1 Providing the Service. We may use and disclose PHI to provide the Service to the Practice, as the Practice directs through its users’ actions in the Service and as described in this Agreement and the Terms of Service. This includes storing, displaying and backing up PHI, enforcing access by role, keeping the audit log, supporting record exports and deletions, and supporting the Practice when it asks for help.

4.2 Required by Law. We may use or disclose PHI as Required by Law. If we receive a subpoena, court order or other legal demand for PHI, we will tell the Practice before we respond, unless the law forbids it, so the Practice can seek a protective order or other remedy. We will disclose only the PHI the demand requires.

4.3 Minimum necessary. We will limit our uses and disclosures of PHI, and our requests for PHI, to the minimum necessary to accomplish the intended purpose, consistent with the Practice’s minimum necessary policies and procedures that it shares with us.

4.4 No use the Privacy Rule would not allow. We will not use or disclose PHI in any manner that would violate the Privacy Rule if done by the Practice, except for the specific uses and disclosures set out in Sections 4.5 and 4.6.

4.5 Our management and administration. We may use PHI for our proper management and administration or to carry out our legal responsibilities.

4.6 Disclosures for management and administration. We may disclose PHI for our proper management and administration or to carry out our legal responsibilities only if:

  1. the disclosure is Required by Law; or
  2. we obtain reasonable assurances from the person to whom the PHI is disclosed that it will be held confidentially and used or further disclosed only as Required by Law or for the purpose for which it was disclosed to that person, and that the person will notify us of any instance of which it is aware in which the confidentiality of the PHI has been breached.

4.7 No data aggregation. We do not provide Data Aggregation services. We will not combine the Practice’s PHI with PHI we hold for any other covered entity to produce data analyses.

4.8 No de-identification for our own purposes. We will not de-identify PHI for our own purposes.

4.9 No sale, marketing or AI training. We will not:

  • sell PHI or receive any payment, direct or indirect, in exchange for it;
  • use or disclose PHI for Marketing; or
  • use PHI, or information derived from it, to train artificial intelligence or machine-learning models.

5. The Practice’s obligations

5.1 Notice of Privacy Practices. The Practice will tell us of any limitation in its Notice of Privacy Practices under 45 CFR 164.520, to the extent the limitation may affect our use or disclosure of PHI.

5.2 Changes in permission. The Practice will tell us of any change in, or revocation of, an Individual’s permission to use or disclose their PHI, to the extent the change may affect our use or disclosure of PHI.

5.3 Restrictions. The Practice will tell us of any restriction on the use or disclosure of PHI that it has agreed to or must comply with under 45 CFR 164.522, to the extent the restriction may affect our use or disclosure of PHI.

The Practice will usually carry out these limits itself in the Service, for example by changing who is assigned to a child or by deleting a child’s records. It needs to tell us only when a limit affects something we do.

5.4 Permissible requests. The Practice will not ask us to use or disclose PHI in any manner that would not be permissible under the Privacy Rule if done by the Practice, except as allowed by Sections 4.5 and 4.6.

5.5 Managing users and access. Through its clinic owner, the Practice is responsible for:

  1. inviting only staff who need access, and making sure each user has only the access their role requires;
  2. removing users promptly when they leave the Practice or no longer need access;
  3. making sure users protect their sign-in details and authenticator devices, never share accounts, and report a lost device or a possibly compromised account right away; and
  4. making sure users follow the Practice’s own HIPAA policies when they use the Service.

The Practice will tell us promptly if it believes someone has used the Service to access PHI without authorization.

5.6 Entering only what is needed. The Practice will enter only the minimum necessary PHI. In particular, it will identify each child by initials or a nickname, not a full name. It will not enter Social Security numbers, health insurance information, or contact details (such as addresses, phone numbers or email addresses) for children or their families. This applies to every field, including session notes and comments.

5.7 Copies outside the Service. PDFs are created in the user’s browser, and record exports are made available to the clinic owner. Once a user saves, prints or shares a PDF or record export outside the Service, that copy is under the Practice’s control, and protecting it is the Practice’s responsibility.

5.8 Contact details. The Practice will keep the clinic owner’s email address in the Service up to date, because we send notices there (Section 8.7).

6. Term and termination

6.1 Term. This Agreement takes effect when the Practice’s clinic owner accepts it. It ends when the Practice’s account for the Service is closed, or earlier if it is terminated under Section 6.2. Sections 6.4 to 6.9 then apply.

6.2 Termination for cause. If either party breaches a material term of this Agreement, the other party may give written notice describing the breach. If the breach is not cured within 30 days after the notice, the other party may terminate this Agreement. If cure is not possible, the other party may terminate this Agreement immediately by written notice.

6.3 Effect on the Service. We cannot hold PHI for the Practice without this Agreement. When this Agreement ends for any reason, we will stop creating, receiving, maintaining or transmitting PHI for the Practice, except as needed to carry out Sections 6.4 to 6.8.

6.4 Export period. For 30 days after this Agreement ends, the Practice may export its records, including a record export of everything the Service stores about each child. The parties agree that making the record export available is how we return PHI to the Practice.

6.5 Deletion from the live Service. After the 30-day export period, we will delete the Practice’s PHI from the live Service. On written request, we will confirm in writing when the deletion is complete.

6.6 Backups. Copies of deleted PHI in point-in-time recovery backups are not removed one by one. They expire within 35 days after deletion from the live Service. The same applies when a clinic owner deletes a child’s records while the Agreement is in effect: the records are removed from the live database immediately, and backup copies expire within 35 days. We will use backups only to recover the Service from data loss or failure, and we will not use them to bring back PHI that has been deleted.

6.7 Where return or destruction is not feasible. Returning or destroying PHI is not feasible for:

  1. backups, until they expire under Section 6.6; and
  2. the audit log, which we keep for at least six years to meet HIPAA’s documentation requirements. The audit log holds user names and random record numbers, not client names.

For any PHI we keep for these reasons, we will extend the protections of this Agreement to it, continue to comply with the Security Rule, and limit further uses and disclosures to the purposes that make return or destruction infeasible, for as long as we keep it. When the retention period ends, we will destroy it.

6.8 Subcontractors. Sections 6.4 to 6.7 apply equally to PHI that our Subcontractors hold on our behalf.

6.9 Survival. This Section 6, and Sections 3, 4 and 8 as they apply to any PHI we still hold, survive the end of this Agreement until that PHI has been destroyed.

7. Time limits at a glance

This table summarizes the time limits in this Agreement. If it differs from the section it refers to, the section controls.

What Time limit Section
Report a non-permitted use or disclosure, a Breach of Unsecured PHI or a Security IncidentWithout unreasonable delay, and no later than 10 business days after discovery (never later than the 60-day maximum in 45 CFR 164.410)3.5
Help with access, amendment or an accounting of disclosuresWithin 15 days of the Practice’s written request3.11 to 3.13
Cure a material breach of this Agreement30 days after written notice (immediate termination if cure is not possible)6.2
Export records after this Agreement ends30 days6.4
Backup copies expire after deletionWithin 35 days6.6
Audit log keptAt least six years6.7

8. General terms

8.1 Regulatory references. A reference in this Agreement to a section of the HIPAA Rules means that section as in effect or as amended.

8.2 Amendment. The parties will take whatever action is necessary to amend this Agreement from time to time to comply with the HIPAA Rules and other applicable law. We may update this Agreement to keep it compliant with the law. When we do, we will notify the clinic owner and ask them to accept the new version in the Service. The version the Practice last accepted stays in effect until then, except where the law requires otherwise.

8.3 Interpretation. Any ambiguity in this Agreement will be resolved in favor of a meaning that permits compliance with the HIPAA Rules.

8.4 Relationship to the Terms of Service. This Agreement supplements the Terms of Service. If this Agreement conflicts with the Terms of Service or the Privacy Policy on anything concerning PHI, this Agreement controls. On everything else, the Terms of Service continue to apply.

8.5 No third-party beneficiaries. Nothing in this Agreement gives any right or remedy to anyone other than the Practice and us.

8.6 Independent parties. We act as an independent contractor. Nothing in this Agreement makes either party the agent, employee, partner or joint venturer of the other.

8.7 Notices. Notices under this Agreement must be in writing, and email counts as writing.

  • To us: [email protected], or by mail to Nicole Kolenda, Voice For Possibility, 92 Carlton Terrace, Stewart Manor, NY 11530, USA.
  • To the Practice: by email to the clinic owner’s email address in the Service. We may also show notices in the Service.

Questions about this Agreement can be sent to the same address.

8.8 Governing law. This Agreement is governed by the HIPAA Rules and other applicable federal law and, to the extent not preempted by federal law, by the laws of the State of New York, without regard to its conflict-of-law rules.

8.9 Severability. If any provision of this Agreement is held invalid or unenforceable, the rest of the Agreement stays in effect, and that provision will be applied to the fullest extent permitted, consistent with the HIPAA Rules.

8.10 Entire agreement on this subject. This Agreement is the entire agreement between the parties about PHI, and it replaces any earlier agreement or understanding between them on that subject.

8.11 Electronic signature and records. The parties agree to enter into this Agreement electronically. The clinic owner’s electronic acceptance is the Practice’s signature and has the same effect as a handwritten signature under the Electronic Signatures in Global and National Commerce Act (15 U.S.C. §7001 et seq.) and New York’s Electronic Signatures and Records Act (State Technology Law §§301–309). This Agreement and the acceptance record are kept as electronic records.

8.12 Related documents. Terms of Service, Privacy Policy and our Connecting the Dots Pro documents page.

9. Acceptance

9.1 How the Practice accepts. In the Service, the clinic owner:

  1. enters the Practice’s legal name;
  2. enters their own name and title;
  3. confirms that they are authorized to bind the Practice to this Agreement; and
  4. clicks Accept.

By clicking Accept, the clinic owner agrees to this Agreement on the Practice’s behalf.

9.2 What we record. When the clinic owner accepts, the Service records:

  • the Practice’s legal name, as entered;
  • the name and title of the person accepting, as entered, and their confirmation of authority;
  • who accepted (the user account that clicked Accept);
  • when they accepted (date and time);
  • the version of this Agreement accepted;
  • the IP address used; and
  • the browser used.

9.3 Use of the acceptance record. We use the acceptance record only to show that, when and by whom this Agreement was accepted. We keep it for at least six years after this Agreement ends. On request, we will send the Practice a copy.

Version 2026-11-11

Questions about this page? Email [email protected].

Nicole Kolenda, Voice for Possibility

Pediatric speech-language pathologist and motor speech specialist. Helping children with childhood apraxia of speech find their voice.

Explore

  • Home
  • About
  • Connect
  • What is DTTC?
  • Videos
  • Documents & tools

More

  • NYU Lab
  • Speaking
  • Podcast
  • Blog

© 2026 Nicole Kolenda. All writing, videos and transcripts on this site were created by Nicole Kolenda, M.S., CCC-SLP. You're welcome to quote and share them with credit and a link.

Privacy Policy · Terms of Use · Privacy and legal documents · For AI and search crawlers