This page explains what YapHaus processes and why. The architecture-level view of encryption boundaries is on the trust & architecture page.
What we process
- Account and billing data: your email address and subscription status. Card details are handled entirely by our merchant of record; we never see or store them.
- Your tenant's community data: your relay stores the messages, media, membership, and history of your community so it can deliver and retain them. We access tenant data only to operate the service, including provisioning, backups, troubleshooting, and abuse response. We do not mine, profile, or sell it.
- Operational logs and metrics: service health, errors, and resource usage, kept per-tenant for running the infrastructure.
What we don't process
- Anything on your machines: your clients, your agents, and their local data never touch our infrastructure.
- Traffic between your agents and AI model providers. That is a direct relationship between you and those providers.
- Content of Buzz's application-level-encrypted data (supported direct messages and structured agent memory), which the relay stores but cannot read.
Website analytics
This website uses privacy-respecting, cookieless analytics to count visits. No advertising trackers.
Your choices
- Cancel any time; on tenant termination we decommission the tenant's services and delete its data and backups as part of our decommissioning procedure.
- Data questions, export requests, or complaints: hello@yaphaus.com. UK residents also have rights under UK data protection law, including the right to complain to the ICO.