From 34e2ce7701fe673b62cbd6973f3693076a8e57f2 Mon Sep 17 00:00:00 2001 From: kobiebotha Date: Wed, 16 Sep 2026 15:36:16 -0600 Subject: [PATCH 1/3] minor additions --- resources/hipaa.mdx | 2 +- resources/security.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/resources/hipaa.mdx b/resources/hipaa.mdx index 08203852..a9bfb99f 100644 --- a/resources/hipaa.mdx +++ b/resources/hipaa.mdx @@ -37,7 +37,7 @@ The customer remains the owner of their application, databases, and client devic * **Client Device Security** - Customers must implement all necessary **administrative, physical, and technical safeguards** on the **client-side devices** (mobile, web app). This includes device access controls, encryption of the client-side PowerSync SQLite database, and secure disposal of data when a user or device is de-provisioned. + Customers must implement all necessary **administrative, physical, and technical safeguards** on the **client-side devices** (mobile, web app). This includes device access controls, encryption of the client-side PowerSync SQLite database (see [client-side encryption](https://docs.powersync.com/client-sdks/advanced/data-encryption#at-rest-encryption)), and secure disposal of data when a user or device is de-provisioned (see the `disconnectAndClear` method across various SDKs). * **Data Filtering and Access Control** diff --git a/resources/security.mdx b/resources/security.mdx index e9f60134..b54d0773 100644 --- a/resources/security.mdx +++ b/resources/security.mdx @@ -25,7 +25,7 @@ See [Private Endpoints](/configuration/source-db/private-endpoints) for connecti ### HIPAA Compliance -PowerSync Cloud is HIPAA compliant. You can sync Protected Health Information (PHI) or electronic PHI (ePHI) using PowerSync Cloud provided that you fulfill your obligations under our shared responsibility model. Refer to our [HIPAA Compliance](/resources/hipaa) page for details. +PowerSync Cloud is HIPAA compliant for Team and Enterprise customers. You can sync Protected Health Information (PHI) or electronic PHI (ePHI) using PowerSync Cloud provided that you fulfill your obligations under our shared responsibility model. Refer to our [HIPAA Compliance](/resources/hipaa) page for details. ## Client-Side Security From c1b82b36e4e37d6ab0c822c5eb4cae792c7ad6fd Mon Sep 17 00:00:00 2001 From: kobiebotha Date: Wed, 16 Sep 2026 15:38:35 -0600 Subject: [PATCH 2/3] use relative link --- resources/hipaa.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resources/hipaa.mdx b/resources/hipaa.mdx index a9bfb99f..842b21bf 100644 --- a/resources/hipaa.mdx +++ b/resources/hipaa.mdx @@ -37,7 +37,7 @@ The customer remains the owner of their application, databases, and client devic * **Client Device Security** - Customers must implement all necessary **administrative, physical, and technical safeguards** on the **client-side devices** (mobile, web app). This includes device access controls, encryption of the client-side PowerSync SQLite database (see [client-side encryption](https://docs.powersync.com/client-sdks/advanced/data-encryption#at-rest-encryption)), and secure disposal of data when a user or device is de-provisioned (see the `disconnectAndClear` method across various SDKs). + Customers must implement all necessary **administrative, physical, and technical safeguards** on the **client-side devices** (mobile, web app). This includes device access controls, encryption of the client-side PowerSync SQLite database (see [client-side encryption](/client-sdks/advanced/data-encryption#at-rest-encryption)), and secure disposal of data when a user or device is de-provisioned (see the `disconnectAndClear` method across various SDKs). * **Data Filtering and Access Control** From ea8cc230773ad4cb14458e2d629155525c967743 Mon Sep 17 00:00:00 2001 From: kobiebotha Date: Wed, 16 Sep 2026 15:55:22 -0600 Subject: [PATCH 3/3] raw tables --- resources/hipaa.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resources/hipaa.mdx b/resources/hipaa.mdx index 842b21bf..fb546870 100644 --- a/resources/hipaa.mdx +++ b/resources/hipaa.mdx @@ -37,7 +37,7 @@ The customer remains the owner of their application, databases, and client devic * **Client Device Security** - Customers must implement all necessary **administrative, physical, and technical safeguards** on the **client-side devices** (mobile, web app). This includes device access controls, encryption of the client-side PowerSync SQLite database (see [client-side encryption](/client-sdks/advanced/data-encryption#at-rest-encryption)), and secure disposal of data when a user or device is de-provisioned (see the `disconnectAndClear` method across various SDKs). + Customers must implement all necessary **administrative, physical, and technical safeguards** on the **client-side devices** (mobile, web app). This includes device access controls, encryption of the client-side PowerSync SQLite database (see [client-side encryption](/client-sdks/advanced/data-encryption#at-rest-encryption)), and secure disposal of data when a user or device is de-provisioned. To clear the whole database, see the `disconnectAndClear` method across various SDKs ([JavaScript example](https://powersync-ja.github.io/powersync-js/common/interfaces/CommonPowerSyncDatabase#disconnectandclear)). If using Raw Tables, be sure to set a `clear` statement for each table containing ePHI, as specified in [Deleting Data and Raw Tables](/client-sdks/advanced/raw-tables#deleting-data-and-raw-tables) * **Data Filtering and Access Control**