Privacy Policy

1 Introduction

ShiftFeed is an OpenShift and Kubernetes news aggregator developed by an independent developer based in the Czech Republic. It surfaces publicly available articles, GitHub release announcements, Red Hat security advisories, and an AI-generated daily briefing in a single feed.

By using the app you agree to the practices described in this policy.

2 Data the App Does Not Collect

ShiftFeed does not collect, store, or transmit any of the following, regardless of whether you are signed in or not:

• Location data
• Device or advertising IDs
• Usage analytics
• Crash reports
• Contacts or microphone
• Camera or photos
• Browsing history
• Biometric data
• Marketing communications
• Payment instruments

Signed-in users do have an email address and a Supabase user UUID stored — see Section 3. Everything else on the list above is never collected, even with an account.

3 Data the App Does Handle

Article Content Anonymous

The app fetches publicly available article metadata — title, URL, source name, summary, tags, and publication date — along with AI-generated daily briefings from a Supabase-hosted database. This content is identical for every reader and contains no user data.

Anonymous Link Submissions Anonymous

Any user, signed in or not, can submit a public URL via the Submit a Link form. The URL is stored in a submissions table for editorial review. If you are not signed in, no identity is attached to the submission. If you are signed in, your user UUID is associated with the submission for editorial purposes only.

Authentication Signed-in

Sign-in is via Supabase magic link — no password. You enter your email address; Supabase sends a one-time sign-in link; tapping it opens the app and establishes a session via a custom URL scheme (shiftfeed://auth-callback). This is not a system permission; it is a deep-link handled by the app.

We store: your email address, a Supabase-issued user UUID, and standard auth metadata (created at, last sign-in timestamp). Your email is used only to deliver the magic link and as the account identifier. We do not send marketing email.

Bookmarks Signed-in

When signed in, bookmarks sync across your devices via a user_bookmarks table keyed to your user UUID. Anonymous users' bookmarks are stored locally on-device only and are never transmitted.

Push Notifications

Push notifications operate in two distinct modes depending on sign-in status:

• Broadcast topics Anonymous — on Android and iOS, the device subscribes to all (daily briefing), security (CVE alerts), and releases (software release alerts) via Firebase Cloud Messaging. These are broadcast to every subscribed device; no identity is attached and no token is stored by the developer.
• Per-device targeted push Pro — for signed-in Pro users, the device's FCM registration token is stored in a user_device_tokens table linked to your user UUID. This enables the backend to deliver alert-rule matches and personalised briefings directly to your device. Stale tokens are pruned automatically when FCM reports them invalid.

Pro Feature Data Pro

The following data is stored only for signed-in Pro users, each in its own Supabase table scoped to your user UUID:

• Custom alert rules (user_alert_rules) — keyword filters, source category filters, and optional CVSS score thresholds you configure.
• Custom RSS feeds (user_rss_sources) — RSS feed URLs you add. The backend fetches these on your behalf and writes resulting articles to the shared articles table tagged as user-submitted. Those articles are visible only to you, enforced by Supabase row-level security.
• Personalised digest preferences (user_digest_prefs) — your chosen delivery hour and your device's IANA timezone string (e.g. Europe/Prague), read from the operating system via the flutter_timezone plugin. We do not derive or store geolocation; the timezone is used only to schedule your briefing at roughly the right local time.

Paid Subscriptions Pro

Billing is handled entirely by Apple App Store or Google Play. ShiftFeed never sees your card details or payment instrument. Subscription state is managed by RevenueCat, which receives your Supabase user UUID and standard purchase metadata (product ID, store, status) from the platform after sign-in. RevenueCat uses the UUID to link entitlements to your account across devices. No payment data is transmitted to or stored by the developer.

In-App Browser

On Android and iOS, tapping an article opens it in an embedded WebView. On web and desktop, it opens in your external browser. Destination websites (Red Hat Blog, Kubernetes Blog, GitHub, etc.) may set their own cookies and log your visit per their own privacy policies. ShiftFeed does not inject scripts, intercept content, or collect anything from these browsing sessions.

Local-Only Preferences

Light/dark theme, trial-banner-dismissed state, and similar transient UI flags are stored on-device only using standard platform local storage. They are never transmitted.

Row-Level Security

Every per-user Supabase table uses auth.uid() = user_id row-level security policies. A signed-in user can only read and write their own rows. The backend ingestion job uses a separate service-role key to write public article rows; that key never ships in the app binary.

4 Device Permissions

Android

• INTERNET — required to fetch articles and briefings from the backend database.
• POST_NOTIFICATIONS — requested at runtime on Android 13 and above to deliver push notifications. You can deny or revoke this at any time in system settings; the rest of the app continues to function normally.
• Deep-link URL scheme — the magic-link sign-in flow uses the shiftfeed://auth-callback scheme to return you to the app after tapping the sign-in link in your email. This is not a system permission; it is registered in the app's manifest and does not require user approval.

iOS

• Notifications — requested at runtime to deliver push notifications. You can deny or revoke at any time in system settings.
• Deep-link URL scheme — same as Android above; shiftfeed://auth-callback is registered as a URL scheme in the app's Info.plist. No user approval required.

Web and Desktop

No special permissions are requested. The web version runs as a static site and makes anonymous read requests to the backend database, and also fetches font files from Google's servers (see Section 5). Account features and the Pro tier are not available on web or desktop.

5 Third-Party Services

ShiftFeed relies on the following third-party services. No other SDKs, analytics tools, or advertising networks are included.

Manages Pro subscription entitlements on Android and iOS. The RevenueCat SDK initialises on every mobile (Android/iOS) app launch — before any sign-in — creating an anonymous, RevenueCat-generated app-user ID and contacting RevenueCat's backend. Once you sign in, that identity is associated with your Supabase user UUID, and standard purchase metadata (product ID, store, subscription status) is linked so your Pro entitlements follow your account across devices. RevenueCat does not receive payment instrument details. Not used on web or desktop.

RevenueCat privacy policy: revenuecat.com/privacy