Skip to content

Commit

Permalink
HIPAA on Enterprise (#11941)
Browse files Browse the repository at this point in the history
  • Loading branch information
dylburger authored May 14, 2024
1 parent 2f4b327 commit 94426fd
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 3 deletions.
2 changes: 0 additions & 2 deletions docs-v2/pages/privacy-and-security/best-practices.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,6 @@

Pipedream implements a range of [privacy and security measures](/privacy-and-security/) meant to protect your data from unauthorized access. Since Pipedream [workflows](/workflows/), [event sources](/sources/), and other resources can run any Node.js code and process any event data, you also have a responsibility to ensure you handle that code and data securely. We've outlined a handful of best practices for that below.



## Store secrets as Pipedream connected accounts or environment variables

Even if your workflow code is private, you should never store secrets like API keys in code. These secrets should be stored in one of two ways:
Expand Down
2 changes: 1 addition & 1 deletion docs-v2/pages/privacy-and-security/hipaa.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# HIPAA compliance

Pipedream can [sign Business Associate Addendums (BAAs)](#signing-a-business-associate-addendum) for covered entities or business associates intending to pass PHI to Pipedream. We can also provide a third-party SOC 2 report detailing our HIPAA-related controls.
Pipedream can [sign Business Associate Addendums (BAAs)](#signing-a-business-associate-addendum) for Enterprise customers intending to pass PHI to Pipedream. We can also provide a third-party SOC 2 report detailing our HIPAA-related controls.

## HIPAA-eligible services

Expand Down

0 comments on commit 94426fd

Please sign in to comment.