Identity and access
Sign-in uses Google or Microsoft. MCP connections use OAuth 2.1 with PKCE by default, or a manually created connection key for clients without OAuth. Workspace access is derived from current memberships on each request.
SECURITY & TRUST
Clear controls. No inflated claims.
SkilzVolt is the governed home for your organisation's AI skills. This page describes the safeguards we operate today and links to the policies that explain how we handle data.
Controls we operate today
Connection safeguards
OAuth access and refresh tokens, authorization codes, and manual connection keys are stored as one-way hashes. Connection access can be revoked from the Agents page and revocation takes effect on the next request.
Governed content history
Skills, proposals, reviews, and connection events are recorded in an audit trail. Changes create proposals and new immutable versions; SkilzVolt does not provide a tool that rewrites version history.
Transport protection
SkilzVolt uses encrypted transport for browser and MCP traffic. We do not make a blanket encryption-at-rest claim on this page; data-hosting details are maintained in the Subprocessor List.
Your content and AI
Workspace skills and resources are customer-authored content. At the MCP boundary, returned content is explicitly marked as workspace-authored and untrusted reference material. We do not use workspace content to train AI models. Where an optional server-side AI feature is enabled, the limited content sent to the provider is described in our Privacy & AI Notice and Subprocessor List.
Assurances and availability
We do not currently claim SOC 2, ISO 27001, a specific data-residency commitment, a service level agreement, or a public third-party uptime monitor. We will publish those assurances only when they are independently supported. For an operational issue, contact hello@skilzvolt.com.
Policies and documentation
Read our Privacy & AI Notice, Business Data Processing Terms, Subprocessor List, and MCP connection guide.
Report a security concern
Email hello@skilzvolt.com with “Security report” in the subject. Our machine-readable security contact is also available at /.well-known/security.txt. Please avoid including secrets or live credentials in an initial report.