Privacy
Privacy Policy
Last updated June 11, 2026. This page explains how Kybernis handles account data, run traces, approvals, connector metadata, and support records.
Review skill
Lead to Meeting
Needs
lead email, company, use case, preferred time
Tools
CRM, Google Calendar, Gmail
Collection
What Kybernis collects
Kybernis stores the information needed to run and improve your workspace: account and organization details, agent configuration, approval history, connected-channel metadata, billing records, support messages, and the requests or responses needed to operate reusable skills.
Account, workspace, and organization records
Messages, run traces, approvals, and saved skill plans
Connected tool metadata and install state
Billing, audit, and support records
Use
How the data is used
We use collected data to authenticate users, execute requests, resume approved work, connect tools, secure the platform, troubleshoot incidents, and understand whether a saved skill is still working reliably over time.
Deliver the service and keep sessions authenticated
Run, review, resume, and audit skill activity
Operate billing, abuse prevention, and support
Measure reliability so broken reuse can be corrected
Connectors
Third-party apps and subprocessors
When you connect external apps, Kybernis may send data to those services on your behalf. Authentication and infrastructure partners may also process limited data necessary to provide login, hosting, billing, notifications, and managed tool access.
Connected apps receive the data required for the requested action
Identity, hosting, billing, and tool-fabric providers may process operational metadata
Kybernis does not sell customer data
Workspace admins are responsible for what connectors are enabled
Retention
Retention, deletion, and security
We retain workspace data for as long as it is needed to operate the service, maintain auditability, and meet security or legal obligations. We use access controls, scoped credentials, and approval gates to reduce accidental or unauthorized actions.
Run and approval history may remain available for audit and debugging
Backups and logs can persist for a limited operational period
Deletion and export requests can be sent through support
Security incidents are investigated using retained operational logs
Contact
Questions or requests
If you need a data export, deletion review, or clarification about this policy, contact the Kybernis team through the contact page or your active support channel and include the workspace or organization involved.
Support requests should identify the affected workspace
Privacy reviews may require administrator confirmation
Policy updates will be reflected on this page with a new date
Next step
What work should Kybernis learn first?
Start with one typical request. Let the agent do the work once. Approve the skill for next time.