LoopBatch policies
LoopBatch privacy
LoopBatch makes marketing videos for a workspace and posts the videos that a person in the workspace approves.
Your LoopBatch account
If you sign in with Google, LoopBatch stores your Google account identifier, name, email address and profile image, together with login sessions and security records. Google sign-in identifies your LoopBatch account; connecting a social account for publishing requires separate permission. Login provider tokens are encrypted. Signing out ends your LoopBatch session. Contact us to request removal of your LoopBatch account and associated records.
Cookies and browser storage
LoopBatch uses essential cookies to maintain your signed-in session, protect OAuth connection attempts and prevent cross-site requests. LoopBatch does not use advertising cookies or use connected-account data for advertising.
Visits to loopbatch.com
LoopBatch counts each view of a page on loopbatch.com by the page, the name of the site that linked to it (not the page on that site), and any campaign tag in the address: utm_source, utm_medium and utm_campaign. The count keeps no cookie, IP address, browser string or other identifier, and Cloudflare, which stores it, keeps it for three months. LoopBatch also counts tool interactions and invite-link clicks by public page, at most once per action type per page load. These action counts send only the event label and page path, with no tool inputs, file names, file contents or identifiers. They are separate from page views and do not count completed signups or unique visitors. Browser Global Privacy Control and Do Not Track preferences disable these action counts. Cloudflare Web Analytics also measures page views and load times on these pages.
Connecting Instagram lets LoopBatch read your professional account identity and publish Reels you approve. LoopBatch stores your account ID, username, granted permissions and encrypted access token. The token is refreshed to maintain your connection.
TikTok
Connecting TikTok lets LoopBatch read your basic profile (open ID and display name), read your posting settings, and post videos you approve to your TikTok account. LoopBatch stores your open ID, nickname, username, granted scopes and encrypted access and refresh tokens. The tokens are refreshed to maintain your connection.
YouTube
LoopBatch uses the YouTube API Services. Connecting YouTube lets LoopBatch read your channel ID and title, and upload Shorts you approve to your channel. After a Short is uploaded, LoopBatch reads its processing status and its public counts (views, likes and comments), and, if you allowed YouTube Analytics when you connected, its watch time, so the Posts and Evidence pages can show how it did. When you save a public YouTube video as a reference on the Study posts page, LoopBatch reads that video's title, channel and public counts. LoopBatch stores your channel ID, title, handle, granted scopes and encrypted access and refresh tokens, and, during an upload, the encrypted upload session address. The counts and watch time of the Shorts LoopBatch uploaded are kept while your channel stays connected; LoopBatch confirms every hour that your authorization is still in place. The title, channel and counts of a video you saved as a reference are cleared 30 days after they were read; your own link, tags and note stay. 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 LoopBatch's access at any time on the Google security settings page. Disconnecting in LoopBatch deletes the YouTube credential, channel profile, granted scopes, upload session, YouTube-issued video identifiers and links, and the counts and watch time read for your Shorts. LoopBatch performs the same deletion automatically when Google reports that the authorization can no longer be refreshed.
Connecting Facebook lets LoopBatch read your Facebook user ID, the Pages you choose and your permissions on them, and publish Reels you approve to those Pages. LoopBatch stores your Facebook user ID, the ID and name of each Page, the granted permissions and an encrypted access token for each Page. LoopBatch does not keep your personal access token.
Threads
Connecting Threads lets LoopBatch read your Threads user ID and username, and publish videos you approve to your Threads profile. LoopBatch 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 LoopBatch publishes is public.
Bluesky
Connecting Bluesky lets LoopBatch read your account identifier (DID), handle and personal data server, and publish videos you approve as posts on your account. LoopBatch 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.
X
Connecting X lets LoopBatch read your X user ID and username, and publish videos you approve as posts on your account. LoopBatch 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 LoopBatch read your LinkedIn member ID and name, and publish videos you approve as posts on your profile, to the public or to your connections. LoopBatch stores your member ID, name, the granted scopes and an encrypted access token.
Connecting Pinterest lets LoopBatch read your username and your boards, and publish videos you approve as Pins on the board you choose. LoopBatch 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. LoopBatch 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.
Transcripts
When a flow transcribes a video, LoopBatch sends its audio to Cloudflare Workers AI and keeps the transcript in the workspace. When a flow gives a transcript to the AI writer, the writer's provider receives it as part of the request. A transcript can hold personal data about a person who speaks in the video, and these requests can appear in the logs of the AI gateway that carries them. The workspace chooses which videos to transcribe.
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. LoopBatch-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.
Database backups and deletion
LoopBatch keeps encrypted database backups for disaster recovery in private Cloudflare storage. Weekly copies are scheduled to expire 28 days after creation; monthly copies are scheduled to expire 365 days after creation. Storage cleanup may take additional time after expiry. These periods apply to database copies, not rendered media or the separate media backup.
Disconnecting removes connection data from the live application. Older database backups may still contain that data until they expire. Backup copies are restricted to recovery and are not used for publishing, marketing or routine account access. If a backup is restored, completed deletion requests must be reapplied before the recovered data is used. Financial and security records may be retained separately where needed for legal obligations, fraud prevention or resolving disputes. Contact us for the scope of a deletion request, including any retained records and media copies.
Contact hello@loopbatch.com for privacy questions or a request to remove associated LoopBatch records.