Privacy Policy

TubeVault · tubevault.io
Last updated: May 3, 2026 · Operator: Robin Jost, Cottbus, Germany

Deutsche Version →

1. Data Controller

Data Controller within the meaning of Art. 4 No. 7 GDPR:

Robin Jost
Ziegeleigrund 10, 03051 Cottbus, Germany
Phone: +49 176 22789264
Email: jost@ikigai-dynamics.com
Website: https://tubevault.io

Note: Robin Jost operates as a freelancer (Freiberufler) under §18 EStG and is registered with the Finanzamt Cottbus. The Kleinunternehmerregelung pursuant to §19 UStG applies; no VAT is charged. No trade registration (Gewerbeanmeldung) is required under German law for freelance activity. The appointment of a Data Protection Officer is not required under Art. 37 GDPR given the nature and scale of processing activities.

2. Overview of Data Processed

When you use TubeVault, we process the following categories of personal data:

  • Contact data: Email address (upon registration)
  • Profile data: Name and profile picture (when signing in with Google OAuth)
  • Conversation data: Chat history including your questions, AI-generated answers, source references, and timestamps (see Section 5a)
  • Usage data: Search queries, channel interactions, feature usage, conversion events
  • Technical data: IP address (in server logs), browser information
  • Payment data: Processed exclusively by Stripe — we do not receive or store payment card details
  • Technical identifiers: Hashed device characteristics for anonymous users (no persistent tracking)
  • Attribution data: UTM parameters, referrer URL, landing page variant (only with consent)
  • Persistent session identifier: tv_session_id for attribution (only with consent)
  • Consent records: Which categories accepted, timestamp, IP-hashed (for GDPR Art. 7 accountability)

3. Legal Bases for Processing

We process personal data on the following legal bases:

  • Art. 6(1)(b) GDPR — Processing necessary for the performance of a contract (providing the platform, managing subscriptions)
  • Art. 6(1)(c) GDPR — Processing necessary for compliance with a legal obligation (retention obligations under German commercial and tax law)
  • Art. 6(1)(f) GDPR — Processing based on legitimate interests (IT security, abuse prevention, product analytics, server logs)
  • Art. 6(1)(a) GDPR — Consent (where explicitly obtained, e.g. marketing emails)

4. Registration and User Account

4.1 Email Registration

To create an account, we collect your email address and a password you choose. This data is processed and stored via Supabase Auth (see Section 12).

Legal basis: Art. 6(1)(b) GDPR

Retention: For the duration of the contractual relationship; deletable at any time upon request (Section 15).

4.2 Google OAuth (Single Sign-On)

Alternatively, you may sign in using your Google account. Google transmits the following data to us: email address, display name, profile picture URL, and an anonymised Google user ID. We do not receive your Google password or access any Google data beyond what is necessary for authentication.

Google Privacy Policy: https://policies.google.com/privacy

Legal basis: Art. 6(1)(b) GDPR

5. Search Queries and AI Answer Generation

TubeVault enables semantic search across indexed YouTube channel archives. Each search query is processed to generate an AI-assisted answer with source references.

5.1 Processing Steps

  • Your search input is used as a vector query against our local Qdrant database (Hetzner server, Germany)
  • The most relevant transcript excerpts are identified
  • Your search query and relevant transcript excerpts are transmitted from our server to the OpenAI API (international transfer — see Section 12) to generate a summarised answer. Your browser does not communicate directly with OpenAI.
  • The answer is displayed to you with timestamp links to the source videos on YouTube

5.2 Purpose and Legal Basis

Purpose: Performance of contract (provision of the platform's core functionality)

Legal basis: Art. 6(1)(b) GDPR

5.3 Storage of Search Queries

Search queries may be stored in our server logs for a maximum of 30 days for abuse prevention and IT security purposes. No personalised analysis of individual queries is carried out.

5a. Chat History and Conversation Data

When you use TubeVault while signed in, your conversations (questions and AI-generated answers) are stored in your account so you can revisit them later across sessions and devices.

5a.1 What We Store

  • Your search questions (plain text)
  • AI-generated answers (plain text)
  • Source references (video titles, URLs, timestamps)
  • Conversation metadata: title, associated channel, creation and update timestamps
  • For cross-channel searches: which channels were queried

5a.2 Purpose and Legal Basis

Purpose: Providing the chat history feature as part of the platform's core functionality, allowing you to continue conversations and review past answers.

Legal basis: Art. 6(1)(b) GDPR (contract performance)

5a.3 Retention and Deletion

Conversations are stored for as long as your account exists. You can delete individual conversations at any time from your dashboard. When you delete your account, all conversations and messages are permanently deleted.

5a.4 AI Title Generation

To help you identify conversations, a short topic title is automatically generated for each conversation using OpenAI's API (the same provider used for answer generation; see Section 12.3). The first question and answer of a conversation are sent to OpenAI to produce a brief title. You can rename conversations at any time.

6. Usage Analytics

To improve TubeVault and understand how users interact with the platform, we collect pseudonymised product analytics. All analytics data is stored exclusively on our own servers (Hetzner, Germany). We do not use any third-party analytics services such as Google Analytics or Mixpanel.

6.1 What We Collect

  • Search queries — stored as a cryptographic SHA-256 hash; readable query text is stored for a maximum of 7 days then automatically deleted
  • Channel interactions — which channels are viewed and searched
  • Feature usage — which platform features are used (e.g. transcript view, cross-channel search)
  • Conversion events — upgrade button clicks, subscription starts, new signups

6.2 Privacy Safeguards

  • Unauthenticated users: only hashed data is stored, never raw query text
  • Authenticated users: raw query text is stored for a maximum of 7 days, then automatically nulled by a scheduled cleanup job
  • Aggregate statistics (without any personal reference) are retained indefinitely for product development purposes

TubeVault uses two distinct tracking systems:

  • Analytics tracking (anonymous): Session identifiers are derived from a daily-rotated hash of browser characteristics. These identifiers do not persist across days and cannot identify you personally.
  • Attribution tracking (consent-based): A persistent UUID (tv_session_id) is stored in your browser's localStorage to correlate marketing campaign visits with subsequent signups. This identifier persists until you clear your browser data or revoke attribution consent. It is only created after you grant attribution consent.

Legal basis: Art. 6(1)(f) GDPR — legitimate interest in improving the product and understanding user needs

Retention: Raw queries: 7 days. Event logs: 30 days. Aggregates: indefinite (no personal data).

7. Technical Identifiers for Anonymous Users

To limit use of the free tier to 5 queries per day for unauthenticated users, we generate a non-persistent hashed fingerprint from the following information:

  • Browser type and version (User-Agent string)
  • Screen resolution
  • Preferred browser language

This fingerprint is stored as a cryptographic hash value. It does not enable identification of your person, is not stored persistently, and is scoped to the current calendar day. No cookies are set for this purpose.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in preventing abuse of the free offering)

8. Cookies & Local Storage

TubeVault uses the following client-side storage mechanisms:

Strictly necessary (no consent required)

  • Authentication cookies (Supabase Auth) — for login session
  • tv_consent — your cookie consent preferences
  • tv_audit_session_id — anonymous identifier for consent audit trail (GDPR Art. 7 documentation requirement)

Analytics (consent required)

  • Daily-rotated session hash (server-side) — for usage statistics

Attribution (consent required)

  • tv_session_id (localStorage) — persistent UUID linking sessions for conversion tracking
  • tv_attribution (localStorage) — captured UTM parameters and referrer (90-day retention)

You can manage your consent at any time via the “Cookie settings” link in our footer.

9. Attribution Tracking

When you visit our landing pages, we may capture:

  • UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term) from the URL
  • Referrer (the website that linked to us)
  • Landing page variant (which version of our landing page you saw)
  • Persistent session identifier (UUID stored in your browser)

This data is only collected after you grant attribution consent via our cookie banner. Without consent, no attribution data is recorded.

Retention: Attribution records are automatically deleted after 90 days. Consent records (consent_log) are retained for the duration of our legal accountability obligations under GDPR Art. 7(1).

10. Cookie Consent (TTDSG)

In compliance with §25 TTDSG and GDPR Art. 6(1)(a), we obtain your explicit consent before storing non-essential information on your device. Our cookie banner offers three options:

  • Accept all: All categories enabled (analytics + attribution)
  • Necessary only: Only strictly necessary cookies are stored
  • Settings: Granular control over each category

Your consent choice is stored in localStorage (tv_consent) and a cookie (tv_consent) for server-side enforcement. Both expire after 12 months, after which you will be asked again.

You can revoke or change your consent at any time via the “Cookie settings” link in the footer of our website.

11. Payment Processing

Subscription payments are processed by Stripe Payments Europe Ltd., Ireland. We do not store credit card numbers or full payment details. Stripe acts as a data processor under Art. 28 GDPR; a Data Processing Agreement is in place. For payments routed through US-based Stripe entities, Standard Contractual Clauses ensure adequate protection.

Stripe Privacy Policy: https://stripe.com/privacy

Legal basis: Art. 6(1)(b) GDPR

Retention: Stripe retains payment records in accordance with applicable financial record-keeping obligations (Germany: 10 years under HGB). Full deletion of Stripe payment data after account closure is therefore not always possible; such data is anonymised where deletion is not legally permissible.

12. Service Providers and International Transfers

We engage the following service providers, each under a Data Processing Agreement (DPA) pursuant to Art. 28 GDPR:

12.1 Supabase

Supabase is used as our authentication provider and user data database, configured with an EU server location (Frankfurt). A DPA under Art. 28 GDPR is in place.

Privacy information: https://supabase.com/privacy

12.2 Hetzner Online GmbH

Our servers (application, vector database, embeddings, analytics) are located exclusively at Hetzner data centres in Germany. A DPA is in place with Hetzner.

Privacy information: https://www.hetzner.com/legal/privacy-policy

12.3 OpenAI (International Transfer to USA)

Your search queries are transmitted to OpenAI for AI answer generation. OpenAI processes this data in the USA. The transfer is based on EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) and a Data Processing Agreement. Under OpenAI's API terms (as of 2024), data submitted via the API is not used by default for training AI models; we have contractually ensured this.

Privacy information: https://openai.com/policies/privacy-policy

12.4 Stripe Payments Europe Ltd.

Payment processing is handled by Stripe Payments Europe Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. Stripe processes:

  • Email address (for receipts and customer record)
  • Subscription tier and price ID
  • Payment card details (handled directly by Stripe; never seen by TubeVault)
  • Supabase user ID (as metadata for subscription correlation)

Legal basis: Contract performance (Art. 6(1)(b) GDPR).

Data location: EU (Stripe Payments Europe Ltd., Ireland).

For payments routed through US-based Stripe entities, Stripe maintains Standard Contractual Clauses for adequate protection.

Privacy information: https://stripe.com/privacy

13. Server Logs and Technical Data

When you access our platform, technical information is automatically recorded in server log files:

  • IP address (truncated after 24 hours)
  • Date and time of access
  • URL accessed
  • HTTP status code
  • Data volume transferred
  • Browser type and operating system

This data is used solely to ensure technical operation, IT security and abuse prevention. It is not combined with other data.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest)

Retention: Maximum 30 days, then automatically deleted

14. Data Security

We implement appropriate technical and organisational security measures, including:

  • Encrypted transmission via HTTPS/TLS (Let's Encrypt certificate via Caddy)
  • Production database accessible only via secured SSH connections
  • Qdrant vector database bound exclusively to localhost (no external access)
  • CORS restrictions limited to authorised domains
  • API key protection for administrative endpoints
  • SSH password authentication disabled (key-based access only)

Please note that no data transmission over the internet is entirely secure.

15. Your Rights as a Data Subject

Under the GDPR, you have the following rights regarding your personal data:

Right of Access (Art. 15 GDPR)

You have the right to obtain confirmation of whether we process personal data about you and, if so, to receive a copy of that data free of charge.

Right to Rectification (Art. 16 GDPR)

You have the right to request correction of inaccurate or incomplete personal data.

Right to Erasure (Art. 17 GDPR)

You have the right to request deletion of your data, provided no statutory retention obligations apply. You can delete your account directly in your account settings under “Delete Account”. Upon deletion we will erase:

  • Your Supabase user account (including email, password hash, OAuth link)
  • All conversations and chat messages (questions, answers, source references)
  • All stored search queries and analytics events associated with your account ID
  • All preference data

Stripe payment data cannot be fully deleted due to statutory retention obligations (German Tax Code / AO: 10 years); such data will be anonymised.

Right to Restriction of Processing (Art. 18 GDPR)

You have the right to request restriction of the processing of your data under the conditions set out in Art. 18 GDPR.

Right to Data Portability (Art. 20 GDPR)

You have the right to receive your data in a structured, commonly used and machine-readable format.

Right to Object (Art. 21 GDPR)

You have the right to object at any time to processing of your data based on Art. 6(1)(f) GDPR (legitimate interest), including profiling based on those provisions.

Right to Lodge a Complaint

You have the right to lodge a complaint with a supervisory authority. The authority competent for us is:

Die Landesbeauftragte für den Datenschutz Brandenburg (LDA Brandenburg)
Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany
www.lda.brandenburg.de

You may also lodge a complaint with the supervisory authority in your country of residence or place of work within the EU.

16. Data Retention Periods

Personal data is deleted as soon as it is no longer required for the processing purpose and no statutory retention obligations apply. Key retention periods:

  • Conversation data: Stored until you delete the conversation or your account
  • Raw search queries: 7 days
  • Server logs: 30 days
  • Attribution records (landing_attribution): 90 days
  • Consent records (consent_log): retained for the duration of our legal accountability obligations under GDPR Art. 7(1)
  • tv_consent localStorage entry: 12 months
  • tv_session_id localStorage entry: until manually cleared by user
  • Payment records: 10 years (German commercial and tax law)
  • Aggregate statistics: indefinite (no personal data)

See the specific sections above for additional details on each data category.

17. Minors

TubeVault is not directed at children under the age of 16. We do not knowingly collect personal data from persons under 16. If we become aware that a person under 16 has created an account, we will delete the account and all associated data without delay.

18. Changes to This Privacy Policy

We reserve the right to update this Privacy Policy as necessary, in particular when the platform changes, new service providers are engaged, or the legal framework evolves. Registered users will be notified of material changes by email. The date of the most recent update is always shown at the top of this document.

19. Contact

For questions about data protection or to exercise your rights, please contact:

Email: jost@ikigai-dynamics.com

We respond to requests within 30 days as required by Art. 12(3) GDPR.

You can also submit GDPR requests directly via our online form: Submit a Data Request →

Version History

  • Version 1.1 — May 3, 2026: Added Section 5a (Chat History and Conversation Data); updated data overview, erasure rights, and retention periods.
  • Version 1.0 — April 27, 2026: Initial publication.

TubeVault · Robin Jost · Cottbus, Germany