subprocessors data sharing · Privacy Policy
Clawvisor policy finding
“ Clawvisor interacts with third-party services only when you configure it to, whether on the cloud service or a self-hosted instance: External APIs (Google, GitHub, Slack, etc.) are called on your behalf when agents make requests. You register your own API credentials with each provider. Data exchanged with these services is subject to their respective privacy policies. SAML identity providers: If you configure SAML SSO, authentication requests are sent to your organization's identity provider. We store the IdP's entity ID, SSO URL, and signing certificate to validate responses. Your email address is extracted from the SAML assertion. Telegram is used for approval notifications if you configure a bot. Message content includes service names, actions, and truncated parameters. Resend is used for email verification on the cloud service. Your email address is shared with Resend to deliver verification messages. Cloud relay and push: Local daemon installations connect to the Clawvisor cloud relay by default, and push notifications are enabled when you pair a mobile device. Data handling for these services is described in Section 3a. Clawvisor internal AI features: If you enable optional intent verification or task risk assessment, Clawvisor uses AI models to evaluate agent requests. For intent verification, only request metadata (service, action, parameters, and agent-provided reason) is sent to the model. ”
- Document
- Privacy Policy
- Captured
- 2026-07-20
- Location
- § 6 (Third-Party Services)
- Snapshot SHA-256
- 85c871ad5b3fc409e797c6103f3c76b3f36fe10e5dea7f167798a3fb44c5b55e
Informational only, not legal advice. Terms change; verify the source and capture date.