Effective October 12, 2026. This notice describes data used by Beauty AI Content Factory. The tool connects only social accounts explicitly authorized by the owner; it does not obtain access to mobile app customer accounts.
What the tool handles
The local tool stores authorized channel and professional-account identifiers, names, OAuth credentials, selected videos and captions, review records, schedule times, publication identifiers, status, and available account and video statistics. Google access uses youtube.upload and youtube.readonly, with separately authorized yt-analytics.readonly for performance reports. Meta access uses the four publishing permissions listed on the Content Factory home page, with separately authorized instagram_manage_insights for performance reports. It does not request email inboxes, private messages, contacts, advertising accounts or payment details.
How data is used and shared
Account data is used to identify the intended destination, upload reviewed videos, confirm publication and inspect available performance observations. Owner-requested analytics snapshots help compare content and plan subsequent production; unavailable metrics are not treated as measured results. The selected video, caption and publication settings are sent to the selected platform through its official API. OAuth credentials are sent only to the relevant provider to authenticate or renew access. Account data is not sold, used for advertising targeting, or used to train AI models. AI generation is a separate production step; social-account credentials are not sent to a generation model.
Buffer and public video assets
For TikTok, the owner authorizes Buffer to access the selected account. The local tool sends the selected video URL, caption, schedule and supported disclosure settings to Buffer through its official API. Buffer then processes and delivers the post under its own privacy policy. The local API key is limited to account, post and read-only insights access; TikTok grants to Buffer also include statistics and comments required by its connection flow. The Content Factory code does not use Buffer comment or message features. Selected video masters are hosted at publicly accessible URLs on beautyai.app so Buffer can retrieve them. A hashed filename is not access control: do not stage confidential or unreleased private material.
Google API data
Beauty AI Content Factory’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Access is used for authorized publishing and owner-requested analytics features. The operator may inspect the account, publication records and performance observations to operate the tool, plan content and resolve technical issues.
Storage and retention
Credentials are stored in owner-only local files, excluded from the source-code repository. API traffic uses HTTPS. Local videos, queue records, publication history and analytics snapshots remain on the operator’s computer until deleted by the operator; history prevents accidental duplicate posts. Analytics snapshots are excluded from the source-code repository. Content already uploaded to a platform is stored under that platform’s policies. No safeguard guarantees absolute security.
Revoke access and request deletion
Revoke Google access in your Google Account connections and Meta access in Facebook Business Integrations. This prevents further access using the revoked grant; it does not delete already published platform videos. To request deletion of local credentials and account/publication records, contact team@beautyai.app and identify the account. Delete platform videos through the relevant platform. The operator can also remove local authorization with the Content Factory disconnect command.
Stop Buffer access
Revoke the Content Factory key in Buffer API settings and remove Buffer authorization in TikTok app permissions to stop that access. A local pause or disconnect does not cancel a post already scheduled in Buffer; cancel it separately in Buffer. Public website video assets must be removed through the website deployment process if the operator requests removal.