Privacy Policy
FeedFocus App · As of: 1 October 2026 · Version 11
1. Controller
Miklós Hegybíró · c/o IP-Management #11238 · Ludwig-Erhard-Str. 18 · 20459 Hamburg, Germany
Email: support@feedfocus.app
No data protection officer has been appointed, as fewer than 20 persons are constantly engaged in the automated processing of personal data (§ 38 (1) BDSG).
2. Overview of data processing
FeedFocus processes personal data solely to provide the app's functions. We do not sell data, do not display advertising and do not carry out tracking.
3. Data collected and purpose
3.1 Sign-in (Google OAuth or Apple)
When signing in with Google OAuth, the following data is processed:
- Google User ID, email address, profile name — we receive this data and store it in our database
- YouTube OAuth token (scope: youtube.readonly) — read-only access to the list of subscribed channels; this token remains on your device
Purpose: user authentication and provision of the feed from subscribed channels. No write access to the YouTube account (e.g. likes, comments) takes place. The YouTube OAuth token is generated exclusively on your device and kept there in the protected system storage (iOS Keychain); the exchange takes place directly between your device and Google. The token is never transmitted to our backend or to third parties and is not stored there. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
Alternatively, you can sign in with Apple (Sign in with Apple). In this case, we receive from Apple an Apple user identifier, your email address (optionally a relay address assigned by Apple) and, on first sign-in, your name. No connection to YouTube is established with this sign-in method; you can then use the app with the "Discover" area (see 3.2) and add a YouTube connection later. Legal basis: Art. 6(1)(b) GDPR.
3.2 YouTube data (feed)
To provide the distraction-free feed, the following data is retrieved:
- List of subscribed channels (YouTube Data API, read-only) — retrieved and cached exclusively on your device; the subscription list is not stored on our servers
- New videos from subscribed channels via YouTube's public RSS feeds, as well as video metadata (title, channel, duration) via the YouTube Data API
This data is used exclusively to display the feed and for notifications about new videos. The "Discover" area shows summaries that already exist in the cross-user pool (see 6.) and does not require access to your YouTube account. Legal basis: Art. 6(1)(b) GDPR.
3.3 Video transcripts
Video transcripts required for AI summaries are obtained via an external service provider: Supadata (Dumpling Software UG (haftungsbeschränkt), Berlin, Germany). Only the public YouTube video ID or video URL is transmitted to this provider — no personal data, no user identifier and no OAuth token.
Video transcripts are processed only transiently (read, process, discard): they are held in a temporary technical cache and automatically deleted after 24 hours at the latest. Permanent storage of full video texts does not take place. Legal basis: Art. 6(1)(b) GDPR.
3.4 User data stored in the app
The following data is stored in our database (Supabase, hosted at AWS, region eu-west-1):
- Dismissed videos (dismissed_videos), saved videos (saved_videos), channel groups and channel settings
- Created digests (audio podcasts) as MP3 files — automatic deletion after 30 days
- Briefing rules (automatic digest creation according to user configuration)
- Usage statistics: consumption for AI summaries in units per billing period (measured by video length: one unit per started 60 minutes, up to 4 units per video; the length of the respective video is processed for this purpose), audio productions/month (digests and briefings), perspectives/month, Ask-the-Video usage/month
- User settings: language, voice selection, notification settings, push token, subscription status, as well as the times of the most recently sent notifications (see 3.10)
- Recently viewed channels: When you open a video's detail view, we store the associated channel (channel ID and channel title) with a timestamp on our servers. Purpose: personalising the app and selecting the content of the weekly newsletter and the weekly recap. Legal basis: Art. 6(1)(b) GDPR (performance of contract).
- Cancellation survey: If you cancel a subscription, you can voluntarily tell us the reason in the app (selection from predefined reasons, optional free text). We store the reason, the free text and the cancelled product to improve the app. Providing this is voluntary; the cancellation is independent of it. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in product improvement).
To prevent circumvention of usage limits (e.g. by deleting and recreating an account), usage quotas are additionally tied to a pseudonymized identifier: a cryptographic hash (HMAC-SHA256) of the Google or Apple user identifier. The plaintext identifier is not stored for this purpose; the hash cannot be reversed to the person. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in abuse prevention).
3.5 AI processing by third-party providers
To create AI summaries, podcast scripts, AI perspectives and answers of the "Ask the Video" feature, video transcripts and metadata (title, channel name) as well as your questions about the video are transmitted to the following AI providers:
a) Server-side processing (via Supabase Edge Functions, API keys stored with the provider):
- Anthropic Claude API — summaries, podcast scripts, AI perspective, "Ask the Video". Servers: USA.
- Google Gemini API — summaries, AI perspective, video analysis as a technical fallback. Servers: USA/EU.
- xAI Grok API — AI perspective (synthesis) as well as speech synthesis (see 3.6). Servers: USA.
The respective current model versions are used; the specific models used are disclosed in the AI Transparency Statement.
b) Optional user-side processing (user's API keys, encrypted in the iOS Keychain via SecureStore; PRO tier only): Users can store their own API keys for the supported AI providers (Anthropic, Google, xAI) in the settings. In this case, the data is transmitted directly from the device to the respective provider. By entering their own key, the user actively consents to this transmission.
No personal data of the user is transmitted to the AI providers — only video transcripts, metadata and the questions entered by the user. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
3.6 Text-to-Speech (audio)
Speech output (MP3) for digests and briefings is produced by xAI (Grok TTS, five synthetic voices). Only the texts to be voiced (podcast scripts) are transmitted; no personal data. Processing takes place server-side via Supabase Edge Functions.
3.7 Payment processing
In-app purchases are processed via Apple StoreKit and managed by RevenueCat Inc. (USA). From RevenueCat we receive:
- Subscription status (free/pro, trial), purchase date, expiry date, cancellation status, App User ID
- No payment data (credit card, bank details etc.) — these remain with Apple
RevenueCat stores the Supabase User ID as the App User ID for mapping. Legal basis: Art. 6(1)(b) GDPR.
3.8 Newsletter
When you sign up for the newsletter, we store the email address in our database. Dispatch takes place via Resend Inc. (USA). Double opt-in is implemented: dispatch only begins after confirmation via the link sent. Unsubscribing is possible at any time via the link in every email. Legal basis: Art. 6(1)(a) GDPR (consent).
3.9 Crash reporting and diagnostics
Sentry (Functional Software Inc., USA) records crash reports of the app, technical performance and session data (e.g. load times, session start) as well as server-side error events of our Edge Functions for troubleshooting. These events contain technical context data (e.g. error codes, video IDs, a device-related installation identifier), but no plaintext data such as name or email address. In the development environment, Sentry is disabled. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in the stability of the app).
3.10 Push notifications
When push notifications are activated, an Expo Push Token is generated on the device and stored in our database. Dispatch takes place via the Expo Push Service (650 Industries Inc., USA). You receive notifications for new videos from your channels, completed briefings, reaching quotas, a weekly recap of your usage as well as — after cancelling a subscription — a one-time reminder (without any promotional offer) before it expires. You can disable notifications at any time in the app or iOS settings. Legal basis: Art. 6(1)(a) GDPR (consent).
3.11 Data stored on the device
FeedFocus stores the following data locally on the user's iOS device:
- YouTube OAuth token (see 3.1) — encrypted in the iOS Keychain via SecureStore
- Optional own API keys for supported AI providers — encrypted in the iOS Keychain via SecureStore/LargeSecureStore
- List of subscribed channels (channel IDs), feed cache (AsyncStorage, 2 hours), channel cache (4 hours), perspectives cache (7 days)
- Onboarding status, language setting, playback positions of digests
4. Processors and third-country transfers
The following services process data on our behalf or receive data to provide their services:
| Service | Provider | Location | Purpose | Safeguard | Legal basis |
|---|---|---|---|---|---|
| Supabase | Supabase Inc. | USA (hosting: AWS eu-west-1) | Database, auth, storage, Edge Functions | EU SCCs, DPF | Art. 6(1)(b) |
| Supadata | Dumpling Software UG (haftungsbeschränkt) | Germany (EU) | Sourcing of video transcripts (only public video IDs transmitted) | no third-country transfer | Art. 6(1)(b) |
| Anthropic Claude | Anthropic PBC | USA | AI summaries, podcast scripts, AI perspective, "Ask the Video" | EU SCCs, DPF | Art. 6(1)(b) |
| Google (YouTube) | Google LLC | USA/EU | OAuth, YouTube Data API (read-only), RSS feeds | EU SCCs, DPF | Art. 6(1)(b) |
| Google Gemini | Google LLC | USA/EU | AI summaries, AI perspective, video fallback | EU SCCs, DPF | Art. 6(1)(b) |
| xAI Grok | xAI Corp. | USA | AI perspective, text-to-speech (Grok TTS) | EU SCCs | Art. 6(1)(b) |
| RevenueCat | RevenueCat Inc. | USA | Subscription management, entitlement check | EU SCCs, DPF | Art. 6(1)(b) |
| Resend | Resend Inc. | USA | Newsletter dispatch, double opt-in | EU SCCs | Art. 6(1)(a) |
| Sentry | Functional Software Inc. | USA | Crash reporting, performance data, error monitoring (app + server) | EU SCCs, DPF | Art. 6(1)(f) |
| Expo | 650 Industries Inc. | USA | Push notifications, build service | EU SCCs | Art. 6(1)(a) |
| Apple | Apple Inc. | USA/EU | Sign in with Apple, in-app purchase, app distribution | EU SCCs, DPF | Art. 6(1)(b) |
For transfers to the USA, we rely on EU Standard Contractual Clauses (SCCs) and, insofar as the respective provider is certified, the EU-US Data Privacy Framework (DPF). Details of the individual safeguards can be requested from the controller.
Note: When users use their own API keys, a direct contractual relationship exists between the user and the respective AI provider. The privacy policy of the respective provider then applies additionally.
5. Data security and protection of sensitive data (Art. 32 GDPR)
We take technical and organisational measures to protect personal and sensitive data — in particular Google user data (in particular the recently viewed channels; the list of subscribed channels is processed exclusively on the device and not stored on our servers) — against unauthorised access, loss and misuse:
- Encryption in transit: All data transfers between the app, backend and third-party providers take place exclusively TLS-encrypted (HTTPS).
- Encryption at rest: All data stored in the database and storage (Supabase, AWS region eu-west-1) is encrypted server-side (AES-256).
- Protection of OAuth tokens: YouTube OAuth tokens are not stored on our servers. They are generated on the device and kept there in the protected system storage (iOS Keychain); the exchange with Google takes place directly from the device over TLS-secured connections. No transmission to our backend or to third parties takes place.
- Record-level access control: Row Level Security in the database ensures that each user can access only their own data.
- Data minimization: Least-privilege scope (read-only access, youtube.readonly), no permanent storage of full video texts (automatic deletion after 24 hours at the latest), pseudonymization of control identifiers via HMAC-SHA256 (see 3.4).
- Device security: Credentials stored on the device (YouTube OAuth token, optional own API keys) are stored encrypted in the iOS Keychain.
- Monitoring and response: Continuous error monitoring without plaintext data (see 3.9); security incidents are handled in accordance with Art. 33/34 GDPR.
- Deletion and revocation: Deleting your account removes all user-related data irreversibly. If a YouTube connection exists, the app revokes the YouTube authorisation granted to it with Google before deletion. Independently of this, you can revoke the authorisation at any time in the app under Settings → "Disconnect YouTube", or via your Google security settings athttps://security.google.com/settings/security/permissions.
Use of YouTube API Services: FeedFocus uses YouTube API Services. By using FeedFocus you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). The Google Privacy Policy applies in addition (https://policies.google.com/privacy). You can revoke the access granted to FeedFocus at any time via the Google security settings page:https://security.google.com/settings/security/permissions.
FeedFocus' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Storage period
- Account data: until account deletion by the user (account deletion in the app settings)
- Recently viewed channels: automatically deleted 30 days after the channel was last used (opening another video of the channel restarts the period), at the latest upon account deletion
- Cancellation survey: until account deletion
- YouTube OAuth token (device): until the connection is revoked, the account is deleted, or the app is uninstalled
- Video transcripts: temporary cache, automatic deletion after 24 hours at the latest
- Digest MP3 files: automatic deletion after 30 days
- AI summaries and AI perspectives: stored permanently (cross-user pool without personal data, video ID and language as key)
- Pseudonymized usage identifiers (hash, see 3.4): remain even after account deletion in order to prevent circumvention of usage limits by recreating an account; attribution to the person is not possible
- Newsletter data: until unsubscription (unsubscribe link in every email); upon account deletion, the subscription is automatically removed as well
- Crash reports and performance data (Sentry): 90 days
- Feed cache (device): 2 hours, channel cache: 4 hours, perspectives cache: 7 days (automatic)
7. Your rights
You have the following rights vis-à-vis us under the GDPR:
- Access (Art. 15 GDPR) — which data we store about you
- Rectification (Art. 16 GDPR) — correction of inaccurate data
- Erasure (Art. 17 GDPR) — please use the account deletion in the app settings (Settings → Delete account). All user-related data is irreversibly removed; if a YouTube connection exists, the app additionally revokes the YouTube authorisation granted to it with Google. Deleting the data stored by us does not affect data stored by YouTube itself — you manage that data through the YouTube services or your Google account.
- Restriction (Art. 18 GDPR) — restriction of processing
- Data portability (Art. 20 GDPR) — provision of your data in a machine-readable format
- Objection (Art. 21 GDPR) — objection to processing based on legitimate interests
- Withdrawal of consent (Art. 7(3) GDPR) — at any time with effect for the future (e.g. newsletter unsubscribe, disabling push notifications)
- Revocation of the YouTube authorisation — at any time in the app under Settings → "Disconnect YouTube"; the app revokes the authorisation directly with Google. Alternatively via your Google security settings:https://security.google.com/settings/security/permissions
To exercise your rights, contact us at: support@feedfocus.app
You have the right to lodge a complaint with a data protection supervisory authority. Competent supervisory authority: Die Landesbeauftragte für den Datenschutz Niedersachsen, Prinzenstraße 5, 30159 Hannover, poststelle@lfd.niedersachsen.de
8. Changes
We reserve the right to adapt this privacy policy in the event of changes to the app's functions or the legal situation. The current version is always available at feedfocus.app/privacy.
Privacy Policy | FeedFocus | feedfocus.app | Version 11 (1 October 2026)