Privacy

Owner review required. This describes the current implementation; a finalized privacy notice is still needed.

What the app uses

Breakfeed stores your Auth0 Google identifier, display name, email when supplied, category and ordering preferences, expiring OAuth transactions, and server-side sessions. Cookies keep you signed in and protect form submissions.

Google sign-in uses Auth0 and includes YouTube authorization. The server stores the connected account identifier and provider tokens, including a refresh token when available, to read your liked videos. The browser receives video metadata and loads YouTube’s embedded player.

Signing out invalidates your local session. To revoke Google’s authorization grant, remove access through your Google account’s third-party connections.

Guest feeds use cached public video metadata without an account’s OAuth tokens. Guest category choices stay in the current page. Auth0 metadata is not used for application preferences. Earlier email-account records are retained pending an owner-approved retention or migration policy; they cannot be used to sign in.

Details still needed

The owner must provide the operator identity, hosting details, retention and deletion policy, privacy-request contact, applicable rights, and effective date. Account deletion and a public privacy contact are not available yet.

See Google’s Privacy Policy for Google and YouTube services.