docs: clarify fly postgres usage for hipaa (#26231)

apps/docs/content/guides/platform/fly-postgres.mdx

@@ -8,7 +8,7 @@ Fly Postgres databases are deployed on the Fly.io edge network. Fly Postgres is
 
 <Admonition type="note">
 
-Fly Postgres is currently in private alpha. To request early access, [submit the request form](https://forms.supabase.com/fly-postgres). Do not use it for Production workloads.
+Fly Postgres is currently in private alpha. To request early access, [submit the request form](https://forms.supabase.com/fly-postgres). Do not use it for Production workloads or to process Protected Health Information (PHI).
 
 </Admonition>
 

apps/docs/content/guides/platform/shared-responsibility-model.mdx

@@ -54,5 +54,5 @@ You can use Supabase to store and process Protected Health Information (PHI). Yo
 - Enabling [Network Restrictions](/docs/guides/platform/network-restrictions).
 - Disabling [Supabase AI editor](https://supabase.com/dashboard/org/_/general) in our dashboard.
 - 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 using [Edge functions](/docs/guides/functions) or [Fly Postgres](/docs/guides/platform/fly-postgres) to process PHI.
 - Not storing PHI in [public Storage buckets](/docs/guides/storage/buckets/fundamentals#public-buckets).