docs: remove Classic-era Data Privacy / SaaS UI section

The Data Privacy section described what the Robusta Classic OSS
sends to sinks (Slack, MS Teams, etc.) and the SaaS UI's role
relative to that pipeline. Both are Classic-era framing.

https://claude.ai/code/session_019GQrc8wVq14if8f7F3pp4f

Author: claude

docs/setup-robusta/privacy-and-security.rst

@@ -8,27 +8,6 @@ Robusta was designed with security in mind. Our four guiding security principles
 3. **Design for security:** Secure systems are designed to be secure from day one. Discuss security when planning new features.
 4. **Experience matters:** Hire engineers who have built secure enterprise platforms before. Make security a core part of company culture.
 
-Data Privacy
-********************
-The Robusta Open Source doesn't store persistent information itself.
-Information is sent to destinations (sinks) like Slack or MSTeams, and they are responsible for storing it.
-
-By default, the following data is sent to sinks. It can be customized if necessary.
-
-- Prometheus alerts
-- Alert enrichments, or insights. (Example: an alert for high memory usage will include a memory graph.)
-- Technical events from Kubernetes itself. (Example: notifications on crashing pods, K8s warning events.)
-- Logs from unhealthy pods. (Note: Robusta does *not* gather logs continuously, rather only from crashing or misbehaving pods.)
-
-SaaS UI
-----------
-When the Robusta SaaS platform is enabled (optional), it receives the above data, as well as metadata about nodes and workloads in your cluster.
-This is used, for example, to show you when deployments were updated and what YAML fields changed.
-
-All data in the SaaS platform is encrypted at rest and stored in accordance with industry standards.
-
-If necessary, the SaaS UI can be run on-prem as part of our paid plans. Contact support@robusta.dev for details.
-
 Running Robusta in Airgapped Environments
 ******************************************
 Refer to :ref:`Deploying Behind Proxies`.