Scope and contact
This Privacy Policy applies to For The People ("FTP"), including the FTP website, team communities, creator tools, live broadcast rooms, and the optional YouTube connection. FTP is responsible for the information described in this policy.
For privacy questions, complaints, or deletion requests, email info.ftp.dev@gmail.com.
Information FTP collects
Account and profile data
Name, email address, account identifiers, profile image, username, favorite teams, role, subscription status, and information you choose to add to your profile.
Community and creator data
Posts, comments, reactions, follows, messages, uploaded media, invitations, live-room settings, broadcast layouts, and other content or settings you submit.
Service and device data
IP address, browser and device details, timestamps, page and feature activity, error reports, security events, and diagnostic data needed to operate and protect FTP.
Support and transaction data
Messages you send to support and records related to invitations, subscriptions, or purchases. Payment providers process payment credentials; FTP does not store complete payment-card numbers.
How FTP uses information
- Provide accounts, team communities, messaging, creator tools, live rooms, and requested broadcasts.
- Personalize the interface using your selected team, theme, and layout preferences.
- Authenticate users, enforce permissions, prevent abuse, and protect the service.
- Process subscriptions, respond to support requests, and send service communications.
- Measure reliability and feature use, diagnose failures, and improve FTP.
- Comply with law, enforce our Terms of Service, and protect users and the public.
YouTube API Services and Google data
FTP uses YouTube API Services for an optional creator feature. When a host chooses Connect YouTube, Google asks that person to authorize FTP to access and manage the selected YouTube channel. This authorization is separate from signing in to FTP.
Data FTP accesses and stores
The requested YouTube permission allows FTP to view and manage YouTube account data needed for live broadcasting. FTP may access or store the connected channel ID and title, channel metadata returned by YouTube, an encrypted OAuth refresh token, YouTube broadcast and stream IDs, broadcast title, visibility, made-for-kids selection, lifecycle and health status, timestamps, and provider error information.
FTP uses short-lived OAuth access tokens only while performing authorized operations and does not persist them. The refresh token is stored only on the server, encrypted at rest, and is not exposed to other FTP users. FTP does not ask for or store the Google account password. FTP uses the minimum Google permission needed for the connected live-broadcast feature.
How FTP uses YouTube data
FTP uses this data only to identify the authorized channel, display it to the connection owner and invited FTP users, create and bind a YouTube live broadcast and ingestion stream after the user confirms the settings, transition the broadcast through its lifecycle, display delivery status, complete the broadcast, troubleshoot failures, and maintain or revoke the connection.
A connection owner can invite selected FTP users to publish through that connection. Recipients see the channel identity and owner on Connected accounts and may accept or decline. No publishing access is granted until acceptance. FTP records the selected user, connection, permission description version, owner consent, and recipient acceptance time. Accepted collaborators can see the channel identity and connection health and choose titles, visibility, and audience settings for broadcasts in rooms they host. Each host confirms these settings before publishing. Collaborators never receive Google tokens or permission to reconnect, disconnect, or share the connection with others.
FTP does not sell YouTube Authorized Data, use it for targeted advertising, build advertising profiles from it, or allow unrelated third parties to use it for their own purposes.
Sharing for a user-requested simulcast
FTP sends requests and the user-approved broadcast settings to Google and YouTube to perform the requested channel actions. FTP uses Mux to deliver the live program from FTP to YouTube. For that purpose, Mux processes the audiovisual program feed and the YouTube ingestion details needed to route it. Hosting, database, authentication, monitoring, and security providers may process limited data only as needed to operate FTP under contractual and confidentiality controls. FTP may also disclose information when required by law or to protect users, FTP, Google, YouTube, or the public.
Retention, revocation, and deletion
FTP retains YouTube Authorized Data only while the connection is active and as needed to provide the feature. The connection owner can use Connected accounts > YouTube > Disconnect in FTP. Finish any active broadcast before using this control. FTP disables further use immediately, requests programmatic revocation of the Google token, and deletes the encrypted token and other YouTube Authorized Data held by FTP as soon as possible and no later than seven calendar days after revocation.
Removing an FTP collaborator blocks future broadcast starts but allows an already-confirmed broadcast to finish. It does not revoke Google authorization. Disconnecting a provider connection removes its FTP collaborators and may also invalidate related Google authorizations; other connections may need to be reconnected.
Users can also revoke FTP through Google Security Settings. When FTP detects external revocation or a token that can no longer be refreshed, it disables the connection and deletes the related YouTube Authorized Data as soon as possible and no later than 30 calendar days after revocation.
Disconnecting YouTube or deleting YouTube data held by FTP does not delete broadcasts, videos, comments, or other content held by YouTube. YouTube-side content must be deleted through YouTube, YouTube Studio, or another authorized client that supports that action. To request deletion when the in-product control is unavailable, email info.ftp.dev@gmail.com.
Google's handling of information is described in the Google Privacy Policy.
Optional SMS/MMS notifications
If you choose SMS/MMS notifications for unread private messages, generic room-access alerts, replies, comments, mentions, subscribed creators starting a confirmed live stream, or requested game reminders, FTP stores your phone number privately, verifies it through Twilio, and records your notification consent and disclosure version, time zone, and delivery status. Your number is not part of your public profile. Verification alone does not subscribe you. Unread-message texts require the original or expanded disclosure. Each added alert category requires acceptance of a disclosure that names its scope in FTP's SMS/MMS notification settings.
Unread-message notifications link back to FTP and, when available, may include the full text of an unread private message, images uploaded with it, shared links, and link-preview titles, descriptions, and images. Content may be shortened or omitted because of message, media, safety, or device limits. Other alert categories are generic and link back to FTP; they do not include private-message content. When enabled for an opted-in recipient, sending them a private message may result in that content being delivered to their phone, subject to their notification consent and FTP's delivery limits. Conversation replies take place inside FTP; SMS replies are not forwarded to the other user.
Message frequency varies with the alert categories you enable. Message and data rates may apply.
Twilio and telecommunications providers process your number, verification messages, notification text, any included media or media links, and delivery data to verify ownership and deliver requested notifications. Delivered content may appear in the recipient's messaging app or on their lock screen, depending on device settings. Deleting content in FTP cannot recall copies already delivered to a phone. FTP does not sell or share mobile numbers or SMS/MMS opt-in consent with third parties or affiliates for marketing or promotional purposes.
You can disable notifications or remove your connected number in FTP's SMS/MMS notification settings, or reply STOP. Removing a number clears it from your contact settings. FTP retains limited consent and delivery records and, when applicable, a suppression record of your number to honor opt-outs and prevent abuse. Replying START removes the text-message block but does not re-enable your FTP notification preference. Reply HELP for help. For support, privacy, or deletion requests, contact info.ftp.dev@gmail.com. Program details, rates, and delivery limits are in the SMS/MMS terms.
Other service providers and disclosures
FTP uses service providers for authentication, application hosting, databases, search, media storage and delivery, live video, payments, email, analytics, and error monitoring. These providers process data to perform services for FTP and are not permitted to use it for unrelated purposes. FTP may disclose information in a business transaction, with appropriate protections, or when required by law. YouTube Authorized Data is excluded from a business-transaction transfer unless FTP first obtains the user's explicit consent for that transfer. FTP does not sell personal information.
Cookies and local device storage
FTP and its authentication, security, analytics, and payment providers use cookies or similar technologies to keep users signed in, protect sessions, remember theme and team preferences, preserve layout choices, measure product use, and diagnose errors. Disabling required cookies may prevent sign-in or other core features from working. FTP does not use YouTube Authorized Data for advertising cookies or personalized ads.
Retention and security for other FTP data
FTP retains non-YouTube account and community information while an account is active and for only as long as needed for the purposes in this policy, including security, dispute resolution, and legal obligations. Retention periods vary by data type. FTP uses access controls, encryption in transit, protected secret storage, logging, and other administrative and technical safeguards. No system can be guaranteed completely secure.
Your choices
Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or an objection to certain processing. You can update many profile settings in FTP, disconnect YouTube as described above, or contact support. FTP may need to verify your identity before completing a request.
Children
FTP is not directed to children under 13 and does not knowingly allow them to create accounts. The YouTube connection is available only to a person who can validly authorize and manage the selected channel under applicable law and YouTube's requirements. Contact FTP if you believe a child provided personal information without required permission.
Changes to this policy
FTP may update this policy as the service or legal requirements change. The effective date will be revised when that happens. If FTP changes how it uses Google or YouTube data, FTP will provide notice and obtain any consent required before using that data for a new purpose.
Return to the homepage, read the Terms of Service, or contact support.