Legal
Privacy Policy
Last updated: October 7, 2026. This page explains how Kleoverse handles identity, source, evidence, sharing, and account data.
Data We Process
Kleoverse processes account details, identity records, Profile sections, imported source data, evidence, sharing settings, and usage data needed to operate the platform.
How Data Is Used
Your authorized data is used to build and maintain your living identity, answer scoped questions, create reviewed representations, enable sharing workflows, and keep the product secure and reliable.
Sharing Controls
You decide which identity information and evidence are visible and which links are shared. Public and recipient views follow your configured visibility and share-link settings.
Service Providers
Kleoverse may use infrastructure, authentication, storage, analytics, and AI service providers to deliver product functionality. Providers are used only for platform operation.
Google and YouTube Data
With your permission, Kleoverse reads YouTube account information such as liked videos and playlists. A separate Google Data Portability authorization transfers the watch history Google makes available, including video titles, URLs, channels and viewing timestamps. We use these records as private source context and to suggest interests and learning activity for your review. Watching a video does not establish mastery, authorship or course completion. Imported history is private; you control approval and sharing of profile information.
YouTube Storage and Removal
YouTube history records and temporary history authorization credentials are encrypted in storage. Temporary credentials are removed when a history transfer completes or is cancelled. Disconnecting stops future synchronization; it does not delete previously imported information. After disconnecting, Delete imported data removes YouTube source records and unapproved suggestions from the active database. Separately approved profile content remains until you remove it. Cancellation does not remove entries already imported. Database backups may retain earlier copies until they expire; deletion does not remove the original history in your Google Account. You can also revoke access through your Google Account connections.
YouTube Retention and AI Assistance
Imported YouTube records are retained until you remove them; separately approved profile information is retained until you remove that content. Our current database provider, Supabase, maintains daily backups with a seven-day recovery window on our current plan. Backup copies may therefore contain information removed from the active database. When you use AI assistance, relevant approved source or profile context may be sent to OpenAI to generate a response. The history-transfer and initial suggestion steps do not send the watch-history archive to an AI model. AI processing is distinct from importing history; provider-side retention depends on the applicable service configuration and terms. We do not promise zero provider retention.
Your Choices
You can update identity information, disconnect sources, change visibility, revoke supported access, or stop using the service. Some records may be retained when required for security, audit, or legal reasons.