Reaction Journey

Privacy Policy

Effective October 6, 2026 · Last updated October 13, 2026

This policy explains how Reaction Journey accesses, uses, stores, and shares information when you browse the site, create a member account, participate in the community, or import YouTube subscriptions. Reaction Journey uses YouTube API Services.

Reaction Journey is operated by its independent fan-community administrator, reachable at contact@reactionjourney.com. This policy applies to reactionjourney.com. Google sign-in and YouTube subscription importing are separate choices: you can sign in by email and follow reactors manually without granting YouTube access.

Account and community information

Sign-in is provided through Supabase using email links or Google. We receive an account identifier and verified email address. The authentication provider may process your Google profile information as part of sign-in. We store your member identifier, email, display name, account dates and recent activity times to operate the service and verify access.

We store the information you choose to submit or save: follows, hidden reactors, favorites, watch status, video and reactor ratings, preferences, saved views, comments, chat messages, video suggestions, reports, contribution points, and support requests. If you upload a profile picture, your browser resizes it and converts it to JPEG before sending it to our server. We store the resulting image to display beside your member name. Profile pictures can be retrieved by anyone with their image URL, without signing in; do not upload a private image. You can replace or remove your picture in your profile and select Save profile. Avoid submitting sensitive information in community content or support messages.

Activity and visibility

Member-facing comments, chat messages, profile names, contributions and community scores can be visible to other signed-in members according to moderation and page settings. Support conversations are available to the requesting member and moderators.

Moderators can review member activity summaries, including changes to follows, ratings, watch status, preferences, contributions, support activity, video-detail or preview clicks, clicks that open YouTube videos, and recent site presence. This helps operate the community, investigate errors, and address abuse. A recorded click or watch-status choice does not verify that you watched a video; we do not receive your YouTube playback history through the subscription import.

Optional YouTube connection and subscription import

Connecting YouTube separately asks Google for https://www.googleapis.com/auth/youtube.readonly permission and offline access. This read-only scope can access YouTube account information more broadly; Reaction Journey uses subscriptions.list to read the subscriptions of the account/channel you select when you request an import. The response may contain subscription IDs, dates, subscribed channel IDs, titles, descriptions, and thumbnail URLs. The matching code extracts subscribed channel IDs; the other subscription fields are not saved. We do not request watch history, private videos, playlists, or YouTube messages. Email sign-in and ordinary Google sign-in do not automatically connect YouTube.

The server exchanges a one-time authorization code with Google and stores an encrypted refresh token, a connection identifier, and permission-check timestamps with your member account in Cloudflare's database. Tokens are encrypted with AES-GCM using a server-side secret key. Neither the refresh token nor a Google access token is returned to your browser. Temporary authorization state and an encrypted PKCE verifier expire after ten minutes. The code is consumed by the callback and is not intentionally stored in application records; the hosting provider may record callback request metadata under its logging settings.

The refresh token is used to check permission approximately daily and before each import. These checks do not read your subscription list or automatically add follows. When you request an import, the server reads subscriptions temporarily and sends extracted channel IDs to your browser to prepare the preview. The full subscription response and access token are not retained in database or browser storage. Preview channel IDs remain in browser memory until you cancel, start another import, change accounts, leave the page, or close it.

Only catalog reactor channel IDs you select and confirm are stored as imported follows, with a marker linking them to the YouTube connection. They personalize your feed. Tracked imported follows appear in a dedicated YouTube imports group. Imports do not change manual groups. Selecting that group activates its tracked reactors; switching away does not copy them into a manual group. Independently saved manual memberships remain separate choices. Imported follow additions and removals are excluded from moderator activity records; your complete subscription list and stored tokens are not exposed to moderators by the application. Existing manual follows, hidden reactors, ratings, and favorites are preserved. Import does not change YouTube subscriptions, upload videos, post YouTube comments, or run background subscription synchronization.

Use Disconnect YouTube and delete imported follows in Reactors to delete follows tracked to the connection, remove its stored credential, cancel pending authorization, and request Google token revocation. If Google is temporarily unavailable, an encrypted credential is retained in a private retry queue for up to seven days solely to retry revocation; it is not used to import data. You can also revoke permission in Google security permissions. A definitive revoked/expired permission response triggers deletion of the tracked imported follows and connection. Temporary network or Google service errors do not immediately remove follows. If permission cannot be successfully verified for 25 days, the scheduled cleanup removes the tracked follows and connection rather than retaining them indefinitely. Scheduled checks depend on the service being operational.

Unfollowing an imported reactor removes its import marker; any later manual follow is a separate choice. Following also offers Reset all reactor follows, which removes manual and imported reactor follows together. Imports saved before connection tracking was introduced cannot reliably be distinguished from manual follows and are not automatically deleted. Review those older follows in Following or request assistance at contact@reactionjourney.com to remove older imported information and activity records. Revoking access does not delete your Reaction Journey, Google, or YouTube account.

Google user data and Limited Use

Google sign-in supplies identity information such as your Google account identifier, verified email address and available profile name or image to our authentication provider, Supabase. We use identity information for account creation, authentication and account display, not to read your Gmail or Google Drive. YouTube access is a separate optional authorization.

Reaction Journey’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use authorized subscription information only to provide the import you request and the follows you select. We do not sell it, use it for advertising, provide it to data brokers, use it for lending decisions or use it to train generalized AI models. Tracked imported follow changes are excluded from moderator activity records. Connection credentials and the full subscription response are not available to moderators through the application. Older imports may have existing activity records; contact us to request their removal.

Use and sharing

We use information to authenticate members, personalize feeds, save choices, operate discussions and moderation, maintain the reaction catalog, provide support, and protect the service. We do not sell personal information or use Google user data for targeted advertising. We do not use imported subscription information to train generalized AI models.

Cloudflare provides website delivery, application hosting, database storage and operational logging. Supabase provides authentication and processes account identity and sign-in/session information. Cloudflare processes saved member records, uploaded profile pictures, confirmed follows, and technical request information for hosting and storage. These providers process information needed to deliver their services under their respective policies: Cloudflare Privacy Policy and Supabase Privacy Policy. Google and YouTube receive requests when you sign in, authorize imports, load YouTube images, play an embedded preview, or open YouTube. Hosting and authentication services may process technical information such as IP addresses, request times, browser details and security events.

Public YouTube video and channel metadata is used in the catalog. Videos remain hosted by YouTube. YouTube previews and external links may expose you to YouTube's own cookies, measurement, content and advertising. See the Google Privacy Policy. We may also disclose information when required by law or necessary to address security incidents or protect rights.

Data handling summary

Browser storage and security

The site stores authentication sessions in browser storage to keep you signed in and uses browser storage or account settings for preferences. External providers may use cookies or similar technologies under their own policies. Clearing browser storage can sign you out; it does not delete records saved on our servers.

We use HTTPS and authenticated access controls for member services, with moderator-only administrative functions. No online system is guaranteed secure. Do not share sign-in links, access tokens, passwords, or API keys.

Retention, access and deletion

Account settings and community records remain stored while needed to provide your account and the community, unless you remove them through available controls or request deletion. The service currently has no self-service account-deletion button or fixed automatic expiry for all member records. Activity, moderation, support and operational records may be retained to investigate abuse, support the service, comply with legal obligations or preserve data integrity. Backups and provider logs may remain for their applicable retention periods.

To request access, correction, an export, or deletion of your account or imported YouTube information, email contact@reactionjourney.com, preferably from your account email, or use Contact while signed in. Specify whether you want imported follows removed or the entire account deleted. Requests are handled manually after reasonable identity verification; do not send passwords or sign-in tokens. We will explain any information that must be retained and why. Deletion of your Reaction Journey account does not delete your Google or YouTube account.

Children and policy changes

Reaction Journey is intended for users aged 13 or older and does not knowingly collect personal information from children under 13. Contact us if you believe a child has supplied personal information. We may update this policy as the service changes and will identify the effective date. Material changes to Google-data use will require appropriate notice and consent.

Contact

For privacy questions or complaints, contact the Reaction Journey administrator at contact@reactionjourney.com.