docs: clarify data access and deletion, remove encrypted sandbox pricing

content/docs/resources/faq.mdx

@@ -65,6 +65,16 @@ description: The questions that come up most often. What Fluso is, how it works,
 ## Privacy and security
 
 <AccordionGroup>
+  <Accordion title="When we connect our email and Slack to Fluso, what data can Prem AI access? What changes if we don't use the secure enclave?">
+    Fluso accesses your email and Slack content within the permissions you grant. With encrypted inference, model processing happens inside a secure enclave on Prem's infrastructure, without sending your prompts or content to an external model provider.
+
+    The Fluso runtime is separate from encrypted inference. Its data is protected by strict internal access policies and procedures under our SOC 2 Type II compliance program; the runtime itself does not run inside an enclave.
+
+    For greater control, Fluso can run in your own VPC or cloud while using Prem's encrypted inference. Your workspace stays in your infrastructure, and inference content is protected inside the enclave. See [deployment options](/deployment-models).
+  </Accordion>
+  <Accordion title="What happens to our data when we leave Fluso? What do you retain after we delete our account?">
+    Deleting your account deletes your dedicated sandbox and all associated data, including your files, conversations, connected-account credentials, and other records held by Fluso. We do not retain your data after account deletion.
+  </Accordion>
   <Accordion title="Can it see all my emails?">
     It reads emails when you ask it to (e.g., *"summarise my inbox"*) and as part of auto-task extraction. It does not keep a separate mailbox copy; requested content is processed under the controls described in [Privacy](/resources/privacy).
   </Accordion>

content/docs/resources/pricing.mdx

@@ -61,7 +61,6 @@ Model routing depends on the feature. Fluso uses both open-weight models and pro
     - Dedicated account executive
     - Dedicated support
     - Custom obligation detection
-    - Encrypted sandbox
     - Custom data retention
     - Server-backed audit logging (implementation scoped)
     - Custom skills
@@ -126,7 +125,7 @@ Obligation detection scans your connected apps for things you have committed to:
     On Pro and Enterprise, Fluso runs your workload in a hardware-isolated environment so the model provider cannot read it. Useful when the work itself is sensitive. The technical details are on the [pricing page](https://fluso.ai/pricing.html).
   </Accordion>
   <Accordion title="Enterprise security?">
-    Custom data retention and encrypted sandboxes are part of the Enterprise scope. Governance records persist the configured identity and access history, but Microsoft Entra metadata does not verify a directory or provide SSO by itself. Prem has attained SOC 2 Type I; Type II is underway. [Review the current security posture.](https://www.premai.io/security-at-prem)
+    Custom data retention is part of the Enterprise scope. Governance records persist the configured identity and access history, but Microsoft Entra metadata does not verify a directory or provide SSO by itself. Prem has attained SOC 2 Type I; Type II is underway. [Review the current security posture.](https://www.premai.io/security-at-prem)
   </Accordion>
   <Accordion title="Custom skills?">
     Custom skills are part of the Enterprise tier and are built with the Fluso team. For workspace-level skill creation on Plus and Pro, see [Skills](/features/skills).