Guidely
PrivacyTermsDPABAA

Business Associate Agreement

Version 2026-10-29, effective October 29, 2026

This Business Associate Agreement ("BAA") is between Megurp Inc ("Guidely", "we", "us") and the customer that has agreed to our Terms of Service and accepted this BAA for one of its workspaces ("Customer", "you"). It sets out how we protect protected health information that you send to a workspace with HIPAA mode turned on, as the HIPAA Rules require of a business associate. A workspace owner accepts it in the Service when turning on HIPAA mode (section 16).

You are a covered entity, or a business associate of one. If you are a business associate, we are your subcontractor, and this BAA gives you the assurances that 45 CFR 164.502(e)(1)(ii) and 164.504(e)(5) ask you to get from us.

This BAA forms part of the Terms. Section 15 explains how it fits with the Terms and our Data Processing Agreement.

1. Definitions

Capitalised terms used in this BAA but not defined here, such as Breach, Business Associate, Covered Entity, Designated Record Set, Disclosure, Health Care Operations, Individual, Minimum Necessary, Notice of Privacy Practices, Required by Law, Secretary, Security Incident, Subcontractor, Unsecured Protected Health Information and Use, have the meanings given in the HIPAA Rules.

  • HIPAA Rules: the Privacy, Security, Breach Notification and Enforcement Rules at 45 CFR Part 160 and Part 164, issued under the Health Insurance Portability and Accountability Act of 1996 and amended by the HITECH Act.
  • PHI: protected health information, as defined in 45 CFR 160.103, that we create, receive, maintain or transmit for you in a HIPAA Workspace. It includes electronic PHI.
  • HIPAA mode: the workspace setting of that name in the Service, which applies the safeguards in section 5 to everything in the workspace.
  • HIPAA Workspace: a workspace in which HIPAA mode is on, from the moment it was turned on. All projects and environments in that workspace are included.
  • Discovery: the first day on which a Breach is known to us or, by exercising reasonable diligence, would have been known to us, as set out in 45 CFR 164.410(a)(2).
  • Customer-Connected Service: a third-party service that you, rather than we, choose and connect to a workspace, such as Slack, Linear, Jira, Confluence, Intercom, Zendesk, Salesforce, HubSpot, a webhook endpoint, a data warehouse, your own storage bucket, an AI assistant connected through our MCP server, or Anthropic using your own API key.
  • Service, Terms, Workspace, Customer Content, Customer Data and End Users: as defined in the Terms of Service.

2. Scope

This BAA covers PHI in HIPAA Workspaces, and only there. It doesn't cover:

  • data in any workspace that doesn't have HIPAA mode on, or data sent to a workspace before HIPAA mode was turned on in it;
  • the things section 10 lists as outside this BAA.

The Terms don't allow you to send PHI anywhere in the Service except a HIPAA Workspace. If PHI reaches us in some other way, tell us at legal@guidelytech.com and we'll help you delete it. We won't knowingly use or disclose it except as this BAA allows.

3. How we may use and disclose PHI

We will use and disclose PHI only as this BAA permits or requires, or as Required by Law. We may:

  1. Provide the Service to you. Use and disclose PHI to provide, secure and support the Service for you under the Terms, this BAA and your settings in the Service. That includes collecting, storing, organising, analysing, displaying, exporting and deleting it, showing in-app guides, and sending data to the Customer-Connected Services you set up.
  2. Run our business. Use PHI for our proper management and administration, or to carry out our legal responsibilities. We may disclose PHI for these purposes only if the disclosure is Required by Law, or if we first get reasonable written assurances from the recipient that it will keep the PHI confidential, use or further disclose it only as Required by Law or for the purpose we disclosed it for, and tell us of any instance it becomes aware of in which the confidentiality of the PHI has been breached.
  3. Report violations of law. Use PHI to report violations of law to the appropriate federal and state authorities, as 45 CFR 164.502(j)(1) allows.
  4. De-identify it, only to serve you. Create de-identified information under 45 CFR 164.514(a) to (c) only to provide the Service to you, for example the aggregated charts you see in your own workspace. We won't create de-identified data from PHI for our own purposes.

We will make reasonable efforts to limit the PHI we use, disclose and request to the minimum necessary to do these things, in line with 45 CFR 164.502(b) and 164.514(d). What reaches us in the first place is decided by how you configure the Service (section 11).

We won't use or disclose PHI in a way that would break Subpart E of 45 CFR Part 164 if you did it, except as points 2 and 3 allow. We don't provide data aggregation services: we don't combine your PHI with another customer's.

4. What we won't do

We will not:

  • sell PHI, or receive anything of value in exchange for it, as 45 CFR 164.502(a)(5)(ii) describes;
  • use or disclose PHI for marketing, as defined in 45 CFR 164.501, or for advertising;
  • use PHI to train, fine-tune or improve any machine-learning or AI model, ours or anyone else's. Features that work only inside your own project, such as Scout's learned answers, are part of providing the Service to you, not model training;
  • combine PHI with data we receive from anyone else, except as needed to provide the Service to you.

5. Safeguards

We use appropriate administrative, physical and technical safeguards, and comply with Subpart C of 45 CFR Part 164 (the Security Rule) for electronic PHI, to prevent any use or disclosure of PHI other than as this BAA allows. That includes a security official responsible for our safeguards, risk analysis and risk management, workforce training and sanctions, access controls, audit controls, integrity controls, person or entity authentication and transmission security.

The measures in our Data Processing Agreement (Annex II) and on our security page apply to HIPAA Workspaces. While HIPAA mode is on, the Service also:

  • requires two-step verification for password sign-in, and the requirement can't be turned off (GitHub, Google and SAML single sign-on rely on those providers' own verification);
  • asks members to sign in again after the workspace's idle timeout, 15 minutes by default and between 5 and 30 minutes as an owner chooses, and ends every sign-in to the workspace after 12 hours;
  • masks all text and inputs and blocks images in web and mobile session recordings, whatever a project's own replay settings say;
  • keeps Guidely-provided AI features off unless the conditions in section 10 are met;
  • keeps email to your End Users off, and sends notification emails that contain only a short notice and a link into the dashboard, never message text, End User names, email addresses, traits, page addresses or attachments;
  • records in the audit log when a member views a session recording, an End User's profile, a conversation or a complaint, and when data is exported, using record ids rather than PHI, and keeps the audit log for six years.

We may change these measures as technology, threats and the Service change, but we won't reduce the overall protection they give PHI, and we'll keep meeting the Security Rule.

6. Reporting

Breaches of Unsecured PHI. We will notify you of a Breach of Unsecured PHI without unreasonable delay, and in any event no later than 30 calendar days after its Discovery, unless a law enforcement official asks us to delay notice under 45 CFR 164.412. To the extent we know them, the notice will include:

  • each Individual whose Unsecured PHI has been, or is reasonably believed to have been, accessed, acquired, used or disclosed;
  • what happened, the date of the Breach and the date of its Discovery;
  • the types of PHI involved;
  • steps Individuals should take to protect themselves;
  • what we are doing to investigate the Breach, limit harm and prevent it happening again;
  • who to contact at Guidely for more information.

We'll add information as we learn it, including any other information you reasonably need to notify Individuals, the Secretary and, where needed, the media under 45 CFR 164.404 to 164.408. You, or the covered entity you serve, decide on and make those notifications, unless we agree in writing that we will.

Other uses and disclosures. We will report to you any use or disclosure of PHI not provided for by this BAA that we become aware of, including one that is not a Breach, without unreasonable delay and no later than 30 calendar days after we become aware of it.

Security Incidents. We will report to you any Security Incident affecting PHI that we become aware of, without unreasonable delay and no later than 30 calendar days after we become aware of it. If it is also a Breach, the Breach notice is the report.

Unsuccessful attempts. This paragraph is notice, given now, of the ongoing unsuccessful attempts at unauthorised access, use, disclosure, modification or destruction of information, or interference with systems, that every service on the internet sees. Examples are pings and other broadcast attacks on our firewalls, port scans, unsuccessful sign-in attempts, denial-of-service attacks and blocked malware, as long as none of them results in unauthorised access to, or use or disclosure of, PHI. We won't report these individually.

How we notify you. We send notices by email to the owners of the HIPAA Workspace, so keep their addresses current. Mitigating harm: we will mitigate, as far as practicable, any harmful effect known to us of a use or disclosure of PHI by us or our Subcontractors in breach of this BAA. Giving a notice under this section isn't an admission of fault or liability.

7. Subcontractors

We make sure that any Subcontractor that creates, receives, maintains or transmits PHI for us agrees in writing to the same restrictions, conditions and requirements that apply to us under this BAA, as 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2) require. We remain responsible to you for their performance of those obligations.

Our Subcontractors for PHI are:

SubcontractorWhat it doesWhen it receives PHI
Amazon Web ServicesHosting, database, file storage and content delivery, in the United StatesAlways. We have a business associate addendum with AWS.
AnthropicAI replies for Scout and AI-assisted toolsOnly while we have a business associate agreement with Anthropic covering those features, under which it doesn't retain the data. Until then, Guidely-provided AI features stay off in HIPAA Workspaces (section 10).

Our other subprocessors, listed at guidelytech.com/security, don't receive PHI. Twilio SendGrid sends only the email described in section 5, and Stripe handles billing only. The table shows our Subcontractors on this version's date. Before a new Subcontractor starts receiving PHI, we'll add it to that list and email the owners of HIPAA Workspaces at least 30 days in advance, as the DPA describes for new subprocessors.

8. Individuals' rights

Access. To the extent we maintain PHI in a Designated Record Set for you, we will, within 15 business days of your request, make it available to you, in the electronic form you reasonably ask for where we can, so that you can meet your obligations under 45 CFR 164.524. You can also export an End User's data yourself from the dashboard or API at any time.

Amendment. To the extent we maintain PHI in a Designated Record Set for you, we will, within 15 business days of your request, make the amendments you direct or agree to under 45 CFR 164.526, or give you the means to make them yourself in the Service.

Accounting of disclosures. We will keep the information about our disclosures of PHI that you need to give an accounting under 45 CFR 164.528, and give it to you within 15 business days of your request.

Requests made to us. If an Individual asks us directly for access to, amendment of or an accounting of their PHI, we'll pass the request to you within 10 business days and won't answer it ourselves unless you ask us to. Responding to Individuals is your responsibility.

9. Your obligations we carry out, and the Secretary

To the extent we carry out any of your obligations under Subpart E of 45 CFR Part 164, we will comply with the requirements of Subpart E that apply to you in carrying them out.

We will make our internal practices, books and records relating to the use and disclosure of PHI available to the Secretary for the purpose of determining compliance with the HIPAA Rules. Unless the law forbids it, we'll tell you when the Secretary asks.

10. What this BAA doesn't cover

Customer-Connected Services. You choose these services, and they act on your instructions under your own agreements with them; they aren't our Subcontractors. When you connect one to a HIPAA Workspace, we send it the data you set up, protected in transit, and this BAA covers the PHI until we deliver it. What happens to it after that is governed by your agreement with that service, and you need your own business associate agreement with it before you send it PHI. The Service shows a reminder when you connect one to a HIPAA Workspace.

AI features. Scout and the other AI features use Anthropic's models. In a HIPAA Workspace they work only:

  • with your own Anthropic API key in the project. Anthropic is then your Customer-Connected Service, and you need your own business associate agreement with Anthropic; or
  • with Guidely's own Anthropic account, while we have the business associate agreement with Anthropic described in section 7. The HIPAA settings in the Service show whether that is available.

Otherwise they are off. AI assistants you connect to Guidely yourself, through our MCP server, act as you, and what they read goes to their provider under your agreement with it.

Email. Our email provider doesn't sign business associate agreements, so email is outside this BAA. Email to your End Users is off in HIPAA Workspaces, and our notification emails don't carry PHI (section 5). Don't put PHI into anything that is sent by email, such as invitations.

Public and shared content. Customer Content that the Service shows to End Users or to anyone with a link, such as guides, help articles, how-tos, uploaded media and shared links, isn't a place for PHI and isn't covered (section 11).

Fields not meant for PHI. Workspace, project and environment names and other fields that the Service labels as not for PHI aren't covered.

Your workforce's account data. The names, email addresses and sign-in details of the people on your team who use Guidely are covered by our Privacy Policy, not this BAA.

Support. Don't send us PHI by email, in support requests or on calls. If we need to look at PHI to help you, we'll do it inside the Service with your permission, where this BAA applies.

11. Your obligations

You will:

  1. Turn on HIPAA mode first. Turn on HIPAA mode in a workspace before any PHI is sent to it, and send PHI only to HIPAA Workspaces. Don't copy or move PHI from a HIPAA Workspace to another workspace.
  2. Configure what's collected. Send us only the PHI the Service needs, and set it up so it collects nothing more. HIPAA mode masks text and inputs and blocks images in session recordings, but you decide everything else the SDK and API send: event names and properties, traits passed to identify(), page addresses and titles (turn off URL collection where they could contain PHI), error messages, and answers to surveys and guides. Keep identifiers that aren't needed, such as names and email addresses, out where you can.
  3. Keep PHI out of public content. Don't put PHI into guides, help articles, how-tos, uploaded media or anything else shown to End Users or shared by link.
  4. Keep PHI out of fields not meant for it. Don't put PHI into workspace, project or environment names, or into any other field the Service labels as not for PHI.
  5. Get your own agreements. Have a business associate agreement in place with each Customer-Connected Service before you send it PHI, and turn on AI features in a HIPAA Workspace only as section 10 allows.
  6. Manage your team's access. Give members only the roles and permissions they need, remove people promptly when they leave, keep owners' email addresses current, and protect PHI you export or download from the Service.
  7. Tell us about limits on PHI. Tell us of any limitation in your Notice of Privacy Practices under 45 CFR 164.520, any change in or revocation of an Individual's permission to use or disclose their PHI, and any restriction you have agreed to under 45 CFR 164.522, to the extent it affects what we may do with PHI. Where the Service lets you put it into effect yourself, for example by deleting an End User's data, you will.
  8. Not ask for anything unlawful. Not ask us to use or disclose PHI in any way that would not be permitted under Subpart E of 45 CFR Part 164 if you did it, except as section 3 allows.
  9. Have the right to send it. Get any authorisation or consent from Individuals, and give any notice, that the HIPAA Rules or other laws require for the PHI you send us.

12. Term and termination

Term. This BAA starts for a workspace when an owner accepts it and HIPAA mode turns on, and continues until all PHI is returned or destroyed under section 13.

Turning HIPAA mode off. Because a HIPAA Workspace may already hold PHI, owners can't turn HIPAA mode off themselves. Contact legal@guidelytech.com and we'll turn it off once you confirm that the workspace no longer holds PHI, or once that PHI has been deleted. This BAA keeps protecting PHI we still hold after HIPAA mode is turned off.

Termination for breach. If either party materially breaches this BAA, the other may end it by written notice if the breach isn't cured within 30 days of notice describing it, or straight away if cure isn't possible. If you end this BAA because of our breach, you may also end the Terms for the affected workspaces, and we'll refund any prepaid fees for the unused part of the Service in them. If we end it because of your breach, we may suspend or end the affected workspaces under the Terms.

End of the Terms. This BAA ends when the Terms end, subject to section 13.

13. Return and destruction of PHI

While you use the Service. You can export and delete PHI at any time from the dashboard or API, including everything stored about one End User in one step. Data also expires on the retention periods you set per project.

When this BAA or the Terms end. You have 30 days to export PHI, and we'll help you if you ask. We then delete PHI from the Service. We don't keep copies, except:

  • Database backups, which we can't edit, expire on their normal cycle: daily backups within 35 days and monthly backups within one year.
  • Audit logs of HIPAA Workspaces are kept for six years from when each entry was made, to meet the documentation requirements of the HIPAA Rules, and then destroyed. They are designed to hold record ids rather than PHI.
  • Operational logs, which aren't designed to hold PHI but might incidentally include some, expire within one year.
  • Anything the law requires us to keep.

Returning or destroying these copies earlier isn't feasible. While we hold them, this BAA keeps protecting them, and we limit any further use or disclosure to the purposes that make returning or destroying them infeasible. We restore from backups only to recover the Service, and if we do, we delete again any PHI that you had deleted or that this section requires us to delete. On request, we'll confirm in writing once deletion is complete. The same applies to our Subcontractors.

14. Liability

Each party's liability under this BAA is subject to the limitations and exclusions of liability in the Terms (section 14), except where the law doesn't allow them. This BAA doesn't create any indemnity, or any obligation to reimburse costs, beyond what the Terms provide.

15. How this BAA fits with the Terms and DPA

This BAA forms part of the Terms. If it conflicts with the Terms or the DPA about PHI, this BAA wins. Otherwise the Terms and the DPA continue to apply, including the DPA where data protection laws also apply to PHI.

If you have signed a separate business associate agreement with us, it replaces this BAA for the workspaces it covers.

16. Accepting this BAA

A workspace owner accepts this BAA by turning on HIPAA mode in Workspace settings → HIPAA. To do so, the owner reviews this BAA, types their full name and job title, and confirms they have authority to bind the Customer. The owner's own sign-in must use two-step verification or SAML single sign-on, so that turning on HIPAA mode can't lock them out.

When an owner accepts, we record the version of this BAA, the workspace, the owner's account, the name and title they typed, and the date and time, and the acceptance appears in the workspace's audit log. Acceptance binds the Customer that owns the workspace, and covers that workspace. Each workspace that will hold PHI needs HIPAA mode turned on, and this BAA accepted, separately.

To get a countersigned copy, or if you need to negotiate a business associate agreement, email legal@guidelytech.com.

17. Changes to this BAA

We may publish new versions of this BAA here, each with a new version date. A new version applies to a workspace once one of its owners accepts it in Workspace settings → HIPAA. Until then, the version they accepted continues to apply.

If a change to the HIPAA Rules or other law means this BAA must change, we may amend it to comply by notifying the owners of HIPAA Workspaces by email at least 30 days in advance, or sooner if the law requires. Both parties agree to take the steps needed to amend this BAA as the HIPAA Rules require.

18. General

  • References to the law. A reference to a section of the HIPAA Rules means that section as in effect or as amended.
  • Interpretation. Any ambiguity in this BAA is resolved in favour of a meaning that lets both parties comply with the HIPAA Rules.
  • Independent parties. We provide the Service as an independent contractor. Nothing in this BAA makes us your agent.
  • No third-party beneficiaries. Nothing in this BAA gives any rights to anyone other than you and us, including Individuals.
  • Survival. Sections 4, 6, 7, 9, 13 and 14, and our obligations for any PHI we still hold, survive the end of this BAA.
  • Notices. We send notices to the email addresses of the workspace's owners. Send notices to us at legal@guidelytech.com, and report anything urgent about security to security@guidelytech.com.
  • Governing law. As set out in the Terms, except where the HIPAA Rules apply.

Contact

Questions about this BAA: legal@guidelytech.com. Security concerns: security@guidelytech.com.

Megurp Inc, 104 Meadowbrook Rd, Hanover, MA 02339, USA

On this page

  • 1. Definitions
  • 2. Scope
  • 3. How we may use and disclose PHI
  • 4. What we won't do
  • 5. Safeguards
  • 6. Reporting
  • 7. Subcontractors
  • 8. Individuals' rights
  • 9. Your obligations we carry out, and the Secretary
  • 10. What this BAA doesn't cover
  • 11. Your obligations
  • 12. Term and termination
  • 13. Return and destruction of PHI
  • 14. Liability
  • 15. How this BAA fits with the Terms and DPA
  • 16. Accepting this BAA
  • 17. Changes to this BAA
  • 18. General
  • Contact
© 2026 GuidelyDocumentationSecuritySign in