From ea19dcfb15f3a13a37d4005bfb5a319e7eecc679 Mon Sep 17 00:00:00 2001 From: Eric Kharitonashvili Date: Wed, 9 Jul 2025 16:02:53 -0400 Subject: [PATCH] remove OpenAI sharing data from shared responsibility model as we use bedrock now. --- .../content/guides/deployment/shared-responsibility-model.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/apps/docs/content/guides/deployment/shared-responsibility-model.mdx b/apps/docs/content/guides/deployment/shared-responsibility-model.mdx index be95087802e..a5c86283827 100644 --- a/apps/docs/content/guides/deployment/shared-responsibility-model.mdx +++ b/apps/docs/content/guides/deployment/shared-responsibility-model.mdx @@ -1,3 +1,4 @@ +# filename: apps/docs/content/guides/deployment/shared-responsibility-model.mdx --- id: 'shared-responsibility-model' title: 'Shared Responsibility Model' @@ -96,8 +97,6 @@ You can use Supabase to store and process Protected Health Information (PHI). Yo - Enabling [Point in Time Recovery](/docs/guides/platform/backups#point-in-time-recovery) which requires at least a [small compute add-on](/docs/guides/platform/compute-add-ons). - Turning on [SSL Enforcement](/docs/guides/platform/ssl-enforcement). - Enabling [Network Restrictions](/docs/guides/platform/network-restrictions). -- Disabling data sharing for [Supabase AI editor](https://supabase.com/dashboard/org/_/general) in our dashboard. - - Specifically, "_Opt-in to sending anonymous data to OpenAI_" should be disabled (Opt-out). - Complying with encryption requirements in the HIPAA Security Rule. Data is encrypted at rest and in transit by Supabase. You can consider encrypting the data at your application layer. - Not using [Edge functions](/docs/guides/functions) to process PHI. - Not storing PHI in [public Storage buckets](/docs/guides/storage/buckets/fundamentals#public-buckets).