Security at KBPipe

Your video URL is used only to extract audio for transcription. The transcript is processed in memory to generate your article, then discarded. Only the final article you create is saved.

Every workspace is isolated using Supabase Row-Level Security (RLS). Users can only access their own data. There is no cross-tenant data access, even at the database level.

All data is encrypted using TLS 1.2+ in transit and AES-256 at rest. Your articles, settings, and account data are protected both when moving between services and when stored.

We use Anthropic's Claude API, which explicitly does not use API inputs for model training. Your content is never used to improve AI models. AssemblyAI similarly does not train on customer audio.

We collect only what's needed: your email for authentication and the articles you generate. No analytics cookies, no tracking pixels, no third-party advertising. Essential auth cookies only.

KBPipe runs on Vercel (SOC 2 Type II) with data stored in Supabase (SOC 2 Type II, hosted on AWS). All sub-processors maintain enterprise-grade security certifications.

If you use our API, your API keys are SHA-256 hashed before storage. Even we cannot see your original key. Keys are prefixed with vtk_ for easy identification and rotation.

You can delete your entire account and all associated data at any time from Settings. This removes all articles, workspace data, preferences, and your authentication record. No data is retained.