Privacy choices
To turn off analytics and advertising measurement, open Privacy choices and select Reject measurement. You can return here to change your choice. Rejecting measurement does not affect sign-in, payments, or video creation.
Information we collect
We collect account details, product settings, generated content, billing records, service logs, and information you choose to provide. When you connect a social account, we store encrypted OAuth access and refresh tokens and the account identifiers needed to provide publishing features.
If you choose Sign in with Google, we receive your verified email address, name, and profile image to create or identify your FacelessReels account. Google sign-in is separate from connecting YouTube and does not itself authorize YouTube publishing. The account email used for permitted purchase measurement is described under Cookies; YouTube channel data and authorization credentials are not used for that measurement.
YouTube API Services and Google data
FacelessReels uses YouTube API Services. By using our YouTube features, you also agree to the YouTube Terms of Service and should review the Google Privacy Policy.
Connecting YouTube is optional. Google asks you to authorize youtube.upload and youtube.readonly so FacelessReels can identify your selected channel, publish videos you approve, and display the results. We do not request or store your Google or YouTube password.
Data we access and how we use it
- Channel and authorization data: we receive the channel ID, channel name or handle, profile image URL, granted permissions, and OAuth access and refresh tokens with their expiry information. We use the channel details to identify the publishing destination in your workspace. Our server uses the encrypted credentials to make authorized YouTube requests and maintain an eligible connection.
- Publishing data: we send the video, optional thumbnail, title, description, tags, and publishing settings you select or authorize through your Series settings to YouTube. We store the publishing status, YouTube video ID and link, visibility, publication time, and error information to show the result, reconcile interrupted uploads, and troubleshoot failures. Your visibility choice controls who can see the uploaded video on YouTube.
- Video statistics: we retrieve view, like, and comment counts for videos published through FacelessReels. We store time-stamped observations to show performance in your workspace. These API statistics and any metrics derived from them are excluded from external AI-generation prompts.
Who can receive or access YouTube data
- You and authorized internal personnel: you can see your connected channel, publication records, and available statistics in your account. Restricted administrative tools allow our authorized personnel to view channel identity, connection status, publication records, and errors when needed to operate the service, investigate security or abuse, or resolve support and publishing issues. OAuth tokens are not displayed in these tools.
- Google and YouTube: our servers send the authorization credentials and request data needed to connect, refresh access, upload your approved content, retrieve status or statistics, and revoke access. Google processes that information under its own privacy policy.
- Hosting, database, and operational service providers: these providers process and store the records described above on our behalf to host FacelessReels, run background jobs, store encrypted credentials, and diagnose service failures. Access is limited to what is needed for those services.
- Email delivery providers: connection or publishing notices may include your account email, channel name or handle, video title, and a relevant status or error explanation. These providers deliver the notice to you; they do not receive your OAuth tokens.
We do not sell YouTube API data, disclose it to advertisers or data brokers, or use it for advertising, creditworthiness, or surveillance. We do not send YouTube API-derived channel data, credentials, video statistics, or comments to external AI providers. Separately, the briefs, scripts, and media you provide or create in FacelessReels are processed by AI and media providers to create the videos you request. We do not use Google API user data to train generalized AI or machine-learning models.
FacelessReels' use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Information received through the YouTube integration is used only to provide or improve the user-facing YouTube features described here. Disclosure required by law is limited to the information and recipients necessary to meet the applicable obligation.
Instagram data
When you connect an Instagram professional account, FacelessReels uses the Instagram API with Instagram Login and requests instagram_business_basic and instagram_business_content_publish. We access the professional account ID, username, display name, profile picture, granted permissions, and an OAuth access token so you can identify the selected account and publish Reels that you create or approve.
We store the Instagram account identifiers, profile display information, granted scopes, token expiration, encrypted OAuth token, publishing status, media container and Reel identifiers, permalink, caption settings, and publishing errors. We use this data only to maintain the connection, show the selected account, and publish or troubleshoot content at your request. We do not sell Instagram data, use it for advertising, or publish without your configured authorization.
How we use and share data
We use data to authenticate you, create and render videos, publish content you request, operate subscriptions, prevent abuse, provide support, and improve reliability. Infrastructure and media-storage providers host the application and your assets; AI and media-processing providers process your creative inputs to produce scripts, images, speech, and videos; payment providers process subscription and transaction information; and email providers deliver account and service messages. Optional website analytics and advertising measurement are described under Cookies. YouTube API data is handled only as described in the YouTube section above and is not shared for those optional analytics or advertising purposes.
Storage, security, and retention
We apply technical and organizational safeguards designed to protect Google user data, OAuth credentials, generated content, and other sensitive information against unauthorized access, alteration, disclosure, or destruction.
- Encryption in transit: production traffic between your browser, FacelessReels, Google, YouTube, and our service providers is transmitted over HTTPS using TLS.
- Encryption at rest: OAuth access and refresh tokens are encrypted before database storage using authenticated AES-256-GCM encryption with a unique initialization vector. Tokens are decrypted only when an authorized server-side process must call the connected provider.
- Key and secret isolation: encryption keys, OAuth client secrets, and service credentials are kept in protected server-side environment configuration, separated from application data, and are never embedded in public client code.
- Access control and data minimization: authentication and authorization checks restrict connected-account data to the account owner, necessary server processes, and authorized personnel using restricted administrative tools for the purposes described above. OAuth tokens are not returned to the browser or exposed through the user interface.
- Operational protection: we limit the data fields and OAuth scopes requested to those needed for visible product features, monitor service failures and suspected abuse, maintain dependency and platform updates, and investigate reported security events.
- Service-provider controls: infrastructure and processing providers receive only the minimum information needed to perform contracted services and are required to protect that information consistently with their contractual and legal obligations.
YouTube data refresh and expiry
Refreshing an OAuth access token does not refresh stored YouTube data. For connected accounts with a current paid subscription, our maintenance process re-fetches channel details and revalidates stored video links and visibility beginning 28 days after the last successful data check. It verifies that the authorization still corresponds to the same channel and that each checked video remains available. A paused Series does not prevent these data checks; the checks do not publish videos or resume generation.
YouTube statistics are time-stamped snapshots, not permanent historical records. Snapshots expire 29 days after collection. Cached channel details and publication links that have not been refreshed also expire after 29 days. Expired data is excluded from application reads, and scheduled maintenance deletes the expired cache and associated derived observations. We remove unavailable videos from the API cache instead of continuing to display stale results. Free accounts and accounts whose paid subscription has ended do not receive background connection refreshes or reconnect emails; their stale YouTube API caches follow the same expiry rules.
Connection credentials are stored separately from API caches. For accounts without a current paid subscription, connections become eligible for local deletion when their channel data has not been successfully refreshed for 29 days or their authorization requires reconnection. Maintenance rechecks subscription eligibility before deletion and defers connections with unresolved uploads. This automatic expiry removes local credentials and associated YouTube API records; it does not revoke permission at Google or delete videos on YouTube. Connections with a current paid subscription and valid authorization continue to receive maintenance. A connection known to require reauthorization is blocked from publishing; if its YouTube data has not been successfully refreshed for 29 days, its local connection credentials and associated API records also become eligible for deletion, and you must reconnect to use YouTube publishing again. This cleanup does not remove your subscription, Posts balance, original videos, or other platform connections. Completing a disconnection in FacelessReels or deleting your account removes its active local connection credentials and associated API data and requests provider revocation where supported. An unresolved upload may require reconciliation before normal disconnection can complete; this does not authorize another upload. You can also revoke access directly through Google or contact us to request deletion.
Your original briefs, scripts, generated videos, subscription records, and local workflow records are separate from the cached YouTube API data. They may remain in your FacelessReels account until deleted, or for applicable accounting and legal requirements. Removing our local YouTube data does not delete videos already uploaded to YouTube. Residual encrypted copies may remain temporarily in access-restricted disaster-recovery backups and expire through the applicable backup lifecycle unless longer retention is legally required.
If we identify a security incident affecting personal or Google user data, we will investigate, contain and remediate the incident, preserve necessary records, and notify affected users or authorities when required by applicable law. Security concerns can be reported to support@facelessreels.co.
Control and deletion
You can disconnect YouTube, Instagram, or TikTok in Dashboard Settings. Disconnecting removes the connection and associated local data and requests revocation from the applicable provider. You can also revoke FacelessReels from your Google security permissions or Instagram connected-app settings. Meta deauthorization and data-deletion callbacks are processed automatically. You may delete your entire FacelessReels account from Settings or request deletion by emailing support@facelessreels.co.
Your rights and contact
Depending on your location, you may request access, correction, export, restriction, objection, or deletion. Contact support@facelessreels.co. See also our Terms of Service.
Service operator
FacelessReels is operated by Shenzhen City Jiesen Chao Technology Network Co., Ltd. Our business address, service description, and contact information are available in Company details.