Higher-impact workflows can route through approval and review surfaces.
Security and privacy
Review Sage security and privacy before you roll it into a real community.
Sage is designed to be useful in live Discord communities, so evaluators need a clear first-pass explanation of approvals, stored data, and operator controls before they dive into deeper repo docs.
The exact stored surface depends on the enabled runtime features and configuration.
Teams can evaluate the product quickly, then move toward deeper infrastructure control if needed.
What this page is for
This is the public trust layer for Sage. It does not replace the detailed repository security reference, but it does make the product’s privacy and control story easier to evaluate from a marketing and SEO perspective.
Next steps
Keep the next click intentional.
Full security and privacy reference
Continue into the repository doc for the complete technical and operator-facing breakdown.
Open full referenceSelf-hosting guide
Review the self-hosted path if ownership and privacy controls are driving the evaluation.
Open self-hosting guide FAQ
Frequently asked questions
Does Sage always store the same data?
No. The stored surface depends on configuration and which optional features are enabled, which is why the detailed repo security reference still matters.
Are higher-impact actions automatic?
Sage is designed with approval-aware workflows so destructive or high-impact actions can stay reviewable.
Why include this page on the website?
Trust content should be available as a first-party product page so evaluators do not have to infer Sage’s privacy model from code or architecture docs alone.