Privacy policy
Effective November 3, 2026
Reelbridge helps transfer reels from an authorized Instagram account to an authorized YouTube channel. This policy explains the current personal preview.
Information we access
- Instagram: the selected professional account’s ID and username, plus reel IDs, captions, posting dates, permalinks, thumbnails, and video download information.
- YouTube and Google: the selected channel’s ID, name, handle, and image, and information about videos uploaded through Reelbridge, including processing status. The application requests the youtube.upload and youtube.readonly OAuth permissions.
- Authorization: access tokens, a Google refresh token when provided, and expiration information. Platform passwords are entered on Google or Meta screens and are not collected by the Reelbridge dashboard.
- Application activity: publishing preferences, selected source reels, destination channel IDs, upload identifiers, resumable-upload information, transfer times, and errors.
- Website and support: hosting providers may process IP addresses, request details, and technical logs to serve and secure this website. If you email us, we receive the information you include.
How information is used
We use connected-account information to identify the source and destination, display the reel library, retrieve selected videos, upload them to YouTube, check processing, refresh authorization when supported, and avoid duplicate transfers. Captions supply upload titles and descriptions. Preferences control visibility and audience declarations.
Automatic discovery checks new reels while the preview server is running and automatic sync is enabled. Previously posted reels can be selected manually. Data is not used for advertising or to train generalized artificial intelligence or machine learning models.
Email sign-in
The dashboard uses Clerk to send email verification codes and manage login profiles and sessions. Clerk processes the email address you enter, verification events, and device/network information used for security checks under its privacy policy. Reelbridge checks the verified primary email on the server and currently permits only the operator’s account. Session identifiers and short-lived session tokens support signed-in requests. Signing out revokes the Clerk session. The current local integration uses Clerk’s development environment; no paid hosting has been activated. SDK product telemetry is disabled in our integration; required security checks remain enabled.
Transfers and service providers
Instagram video bytes are streamed through the local application server to Google’s YouTube upload service for the transfer you authorize. Google and Meta process data under their own policies. YouTube visibility settings control who can access the uploaded copy.
Cloudflare carries the temporary HTTPS OAuth callback during local development. Its request includes a short-lived authorization code and random state; the local server exchanges the code for an access token. The app secret and saved access tokens are not sent to Cloudflare as part of the callback. This public information website is hosted through OpenAI Sites and its hosting infrastructure.
We do not sell connected-account data or share it with unrelated parties for marketing. Data may be disclosed when required by applicable law.
Storage and security
The current preview stores authorization credentials, account profiles, reel metadata, preferences, and transfer records in a local database on the developer’s computer. Access tokens and resumable-upload sessions are encrypted at rest, with a separate local encryption key. Video transfers are streamed rather than intentionally archived by the sync service. Copies independently uploaded to Instagram or YouTube remain on those platforms.
The dashboard is bound to localhost. The temporary development tunnel serves only the OAuth callback; it does not expose the dashboard. No security method can guarantee absolute protection.
Retention and deletion
Disconnecting an account removes its locally saved connection and authorization tokens and pauses automatic discovery. It does not delete existing reel metadata, transfer history, or copies already published on Instagram or YouTube. Already queued jobs are retained and can continue when the required accounts are reconnected.
Local metadata and transfer records remain until the operator deletes them. To request deletion of retained data or support correspondence, contact the operator at nagakrishna0403@gmail.com. We will verify the request before deleting relevant records. Uploaded YouTube copies must be deleted separately through YouTube; deleting Reelbridge data does not delete those copies.
Your controls
You can disable automatic sync, choose older reels individually, set upload visibility and audience, disconnect accounts, and revoke platform authorization. Pausing discovery does not cancel uploads already queued.
- Manage third-party access in your Google Account
- Manage apps and websites in Instagram
- Review Google permissions
Google API user data
Reelbridge’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Children
This personal preview is not offered to children. YouTube’s “made for kids” declaration describes uploaded content and does not make Reelbridge a service intended for children.
Changes and contact
If the product’s data practices change, this policy will be updated with a new effective date. Before opening the service to additional users or changing where connected-account data is hosted, the operator will update the product and these disclosures as appropriate.
Operator: Naga Krishna Vadlamudi
Support and privacy: nagakrishna0403@gmail.com