Vivu Privacy Policy

Data we process

• Account identity: verified email address, display name, provider identifier, workspace, role, and sign-in timestamps.
• Project data: project names, descriptions, visibility, ownership, video filenames, durations, indexing status, and search results.
• Media and derived data: uploaded video, compressed analysis copies, transcripts, embeddings, thumbnails, metadata, and user-requested exports.
• Operational data: request timestamps, service errors, security events, and cloud resource metrics. Vivu does not request Claude chat history or memory.

How data is used

We use this data only to authenticate users, isolate workspaces and projects, upload and index video, execute searches, generate previews or exports, prevent abuse, and operate the service. Vivu does not sell personal data or use customer video to train a public model.

Storage and retention

Projects, source media, derived index data, and search metadata remain until the user or workspace administrator deletes them, or the account is closed. Short-lived preview URLs normally expire within 15 minutes. Temporary cloud exports are scheduled for removal after 24 hours. OAuth access tokens expire after one hour and refresh sessions after 30 days unless revoked sooner. Operational logs follow the configured Google Cloud retention period.

Sharing and subprocessors

Vivu uses Google Cloud services, including Cloud Run, Cloud Storage, Firestore, Vertex AI, and Identity Platform, to provide the service. Data is shared with those services only as required to complete the requested operation. Organization projects may be visible to other members of the same workspace; private projects are restricted to their owner and authorized administrators.

Your controls

You can delete videos and projects in the Web App, disconnect the Claude connector, revoke Vivu Local folder access, or request account deletion. For privacy or deletion requests, contact support@vivu.ai.

Security

Vivu uses HTTPS, OAuth 2.1 with PKCE, short-lived signed media URLs, server-side tenant and project authorization, and least-privilege service identities. No internet service can guarantee absolute security; report suspected issues through the support page.