Feedline makes marketing videos for a workspace and posts the videos that a person in the workspace approves.
If you sign in with Google, Feedline stores your Google account identifier, name, email address and profile image, together with login sessions and security records. Google sign-in identifies your Feedline account; connecting a social account for publishing requires separate permission. Login provider tokens are encrypted. Signing out ends your Feedline session. Contact us to request removal of your Feedline account and associated records.
Feedline uses essential cookies to maintain your signed-in session, protect OAuth connection attempts and prevent cross-site requests. Feedline does not use advertising cookies or use connected-account data for advertising.
Connecting Instagram lets Feedline read your professional account identity and publish Reels you approve. Feedline stores your account ID, username, granted permissions and encrypted access token. The token is refreshed to maintain your connection.
Connecting TikTok lets Feedline read your basic profile (open ID and display name), read your posting settings, and post videos you approve to your TikTok account. Feedline stores your open ID, nickname, username, granted scopes and encrypted access and refresh tokens. The tokens are refreshed to maintain your connection.
Connecting YouTube lets Feedline read your channel ID and title, and upload Shorts you approve to your channel, through the YouTube API Services. Feedline stores your channel ID, title, handle, granted scopes and encrypted access and refresh tokens, and, during an upload, the encrypted upload session address. By connecting YouTube you agree to the YouTube Terms of Service. Google's use of data is described in the Google Privacy Policy. You can revoke Feedline's access at any time on the Google security settings page. Disconnecting in Feedline deletes the YouTube credential, channel profile, granted scopes, upload session and YouTube-issued video identifiers and links. Feedline performs the same deletion automatically when Google reports that the authorization can no longer be refreshed.
Connecting Facebook lets Feedline read your Facebook user ID, the Pages you choose and your permissions on them, and publish Reels you approve to those Pages. Feedline stores your Facebook user ID, the ID and name of each Page, the granted permissions and an encrypted access token for each Page. Feedline does not keep your personal access token.
Connecting Threads lets Feedline read your Threads user ID and username, and publish videos you approve to your Threads profile. Feedline stores your Threads user ID, username, the requested permissions and an encrypted access token. The token is refreshed to maintain your connection. Every Threads post that Feedline publishes is public.
Connecting Bluesky lets Feedline read your account identifier (DID), handle and personal data server, and publish videos you approve as posts on your account. Feedline stores your DID and handle, the granted scopes, and encrypted access and refresh tokens with their signing key. The tokens are refreshed to maintain your connection. Every Bluesky post is public.
Connecting X lets Feedline read your X user ID and username, and publish videos you approve as posts on your account. Feedline stores your user ID, username, the granted scopes and encrypted access and refresh tokens. The tokens are refreshed to maintain your connection. Every X post is public.
Connecting LinkedIn lets Feedline read your LinkedIn member ID and name, and publish videos you approve as posts on your profile, to the public or to your connections. Feedline stores your member ID, name, the granted scopes and an encrypted access token.
Connecting Pinterest lets Feedline read your username and your boards, and publish videos you approve as Pins on the board you choose. Feedline stores your account ID, username, board names and privacy, the granted scopes and encrypted access and refresh tokens. The tokens are refreshed to maintain your connection.
Approved captions and media are sent to Meta, TikTok, YouTube, Bluesky, X, LinkedIn or Pinterest for publication. Feedline uses Cloudflare and its configured database provider to host the application and its data. Connection data is used to operate these integrations; it is not sold or used for advertising.
Connection data is retained while connected. Disconnecting removes the stored credential, granted permissions, cached profile, provider account identity, upload-operation identifiers, provider post identifiers and provider links, and stops future queued publishing for that connection. Feedline-created run status, rendered media, user-provided or approved titles and descriptions, and security and publication events remain as workspace records until separately removed. Posts already published remain on the platform.
Contact confrontjournal@gmail.com for privacy questions or a request to remove associated Feedline records.