BIRDLENS MEDIA · BIRDBOT
Privacy Policy
Effective date: October 27, 2026
Who we are
BirdBot is a video localization application from BirdLens Media. This policy explains how we handle information in connection with BirdBot and the BirdLens Media website. Contact us at support@birdlensmedia.com with privacy questions or requests.
Information used by BirdBot
BirdBot handles account and sign-in information, channel connections, language preferences, and the content you provide or select for localization. This can include video identifiers and links, titles, descriptions, captions, translated content, and records of your processing and publication requests.
When you connect YouTube, BirdBot stores authorization credentials that allow it to perform the functions you authorize. BirdBot also keeps workflow records and operational information used to run and troubleshoot the service.
Account records link a WorkOS identifier to a BirdBot user. Depending on information supplied by you or an administrator, account/contact records can contain display name, first and last name, email, phone, timezone, contact preference, and account status. These contact details are not necessarily received from WorkOS.
YouTube information handled by BirdBot includes video and channel identifiers, video links, titles, descriptions, thumbnail links, duration, visibility, category, and language settings. BirdBot also handles caption tracks, translated text, subtitle files, spreadsheets, and processing/publication records. BirdBot’s customer localization workflow processes metadata and caption text; it does not download the video or audio itself in this workflow.
Operational logs can include video titles and identifiers, account/channel/workflow identifiers, languages, processing status and duration, provider/model names, token usage, output paths, messages, and limited provider error details.
How information is used
We use information to authenticate users, associate them with their authorized channels, apply language settings, generate localizations, perform requested YouTube updates, display workflow results, and provide support.
BirdBot localizes existing YouTube videos selected by authorized channel owners. It reads video metadata, existing localizations, and caption metadata/text, and publishes requested title, description, and caption changes. It does not upload new videos.
BirdBot fetches metadata during video discovery, publication, and reconciliation. Authorization validation is scheduled every 24 hours; this checks continued authorization and does not refresh all stored YouTube content. BirdBot does not apply a universal fixed refresh interval to all stored API content.
BirdBot uses YouTube API Services. Google's handling of information is described in the Google Privacy Policy.
AI processing and service providers
BirdBot sends source titles and descriptions and target-language instructions to OpenAI for metadata localization. Title correction can also include the current translated title. Caption translation sends source and target language codes and caption cue numbers and text. These translation requests do not include video or audio bytes.
BirdBot uses Render for hosting, WorkOS for authentication, OpenAI for localization, Dropbox for storage of operator-managed local backup copies, and Porkbun for support email. These providers process information needed for their respective services.
We have not opted BirdBot into voluntary OpenAI API data sharing for model training. OpenAI states that API data is not used for model training unless the customer opts in. This does not mean that submitted content is never retained: API security monitoring and some API features involve data storage. See OpenAI’s API data controls.
BirdLens Media does not sell customer data.
BirdLens Media does not use customer data to target advertisements. We share customer data only with service providers as needed to operate BirdBot, or when disclosure is legally required. We do not share it for unrelated purposes.
Human access to customer content is limited to what is necessary for support, security, or a legal obligation, with customer permission where required.
Cookies and similar technologies
BirdBot uses a session cookie to maintain sign-in, authorization-flow state, request-security values, feedback, and admission correlation. Authentication information is sealed by the WorkOS SDK before it is stored within the application session. Browser session storage is also used for a local workflow draft.
We have not added Google Analytics or advertising trackers to BirdBot or the BirdLens Media website. Service providers may still maintain technical and security logs.
Disconnecting YouTube and revoking access
Disconnecting YouTube in BirdBot makes the connection unavailable and initiates credential revocation or removal and bounded cleanup of covered connection-associated records and files. Cleanup can remain incomplete if a step fails, requires retry, or ownership cannot be established. Disconnecting does not delete your entire BirdBot account or content already published to YouTube.
You can separately review and remove BirdBot's access through your Google Account connections. Removing authorization does not undo content already published to YouTube.
Retention and deletion requests
Render takes daily snapshots of BirdBot’s persistent disk. Its dashboard provides a seven-day snapshot availability window. Render dashboard logs are available for seven days under our current plan. These windows do not set the retention period for records or log files stored by BirdBot itself, and deleting a live record does not immediately remove it from existing snapshots.
Separately, the scheduled operator backup preserves source and configuration files and excludes configured runtime, customer-data, generated-output, log, and credential locations. It is not an ongoing copy of BirdBot’s hosted Render data. Identified historical local and Dropbox-local archives containing application data were deleted, while verified source-only replacement copies were preserved. Dropbox cloud synchronization and Dropbox deleted-file or version history have not been verified.
BirdBot stores account information, workflow records, generated translations, subtitle files, API usage information, and operational records. Covered YouTube workflow and API data becomes eligible for cleanup after 21 days. Eligibility does not guarantee deletion within 21 days and does not establish an expiry period for all account information.
Historical deletion coverage remains incomplete for some artifacts, records without complete customer scope, compatibility runtime files, shared operational data, local originals, and provider-held historical copies. Copies may remain after covered live records are removed. Account-data deletion requests are handled through support, and disconnecting YouTube does not delete the entire BirdBot account.
To request deletion of your BirdBot account data, email support@birdlensmedia.com with the subject “BirdBot data deletion.” Include your account email and the channel concerned. Do not send passwords, API keys, or authorization tokens. We may need to verify your authority before acting on the request.
We aim to acknowledge data-deletion requests within three business days, usually sooner. Acknowledgment confirms receipt of the request, not completion of deletion.
Security and your choices
We use access controls intended to limit access to authorized users. No online service can guarantee absolute security. You can contact us about your information, request corrections or deletion, and manage Google's authorization separately through your Google Account.
Policy updates
We will post updated versions of this policy on this page with their effective date. Material changes to data use will be communicated as required before taking effect.
