From 80fc25ea010002aa7cfe745f8330e0d4fa99952e Mon Sep 17 00:00:00 2001 From: Eric Kharitonashvili <33439489+ekhar@users.noreply.github.com> Date: Thu, 10 Jul 2025 08:12:48 -0400 Subject: [PATCH] Shared Responsibility Remove OpenAI Section (#36996) * remove OpenAI sharing data from shared responsibility model as we use bedrock now. * Update shared-responsibility-model.mdx --------- Co-authored-by: Pamela Chia --- .../content/guides/deployment/shared-responsibility-model.mdx | 2 -- 1 file changed, 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..ed553ae0680 100644 --- a/apps/docs/content/guides/deployment/shared-responsibility-model.mdx +++ b/apps/docs/content/guides/deployment/shared-responsibility-model.mdx @@ -96,8 +96,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).