Privacy Policy
TikTok application identity
Xingyu Studio is the registered TikTok application used by Content Distributor. These policies cover that integration as well as the Content Distributor workspace; the separate names do not indicate separate permission grants or production approval.
Content Distributor is a local-first tool used to connect authorized social accounts and publish content selected by the operator. This policy explains the data involved in those operations.
Data the tool accesses
- Basic channel, Page, or professional-account identifiers and display information.
- OAuth access and refresh tokens granted by the account owner.
- Media, captions, titles, hashtags, covers, schedules, and publishing preferences supplied by the operator.
- Platform post identifiers and delivery results needed for status checks and retries.
Google and YouTube data
For YouTube, the application requests only permission to view the authorized channel identity and to manage videos for that channel. Channel identifiers and display information are used to show the selected destination account. Video-management access is used only when the user explicitly submits a video or requests its current delivery status. The application does not use Google user data for advertising, data brokerage, credit decisions, or AI-model training.
How data is used
Data is used only to connect accounts, prepare publishing jobs, upload approved content, report results, refresh authorization, and support explicit retries. The tool does not sell personal data or use connected-account data for advertising.
Storage and security
Credentials and publishing records are kept in the operator-controlled environment. Tokens are encrypted at rest by the application and are not embedded in this public site. Platform authorization codes are not cached by this site.
Sharing
Content and required metadata are sent only to the destination platforms selected by the operator. Service providers may process infrastructure traffic only as needed to operate the public site and authorization flow.
Retention and deletion
Authorization data is retained only while an account remains connected or while records are needed for the operator's publishing history. See the data deletion instructions for removal steps.
Platform terms
Use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Facebook and Instagram data is handled according to applicable Meta Platform Terms.
Changes
Material changes will be published on this page with an updated effective date.
YouTube API Services and Google user data — October 3, 2026
Content Distributor uses YouTube API Services. With your authorization, the operational workspace reads your YouTube channel identifier and display information to identify the destination, and sends the video, title, description, privacy choice and other settings you select to YouTube when you confirm an upload. It may query the video identifier, processing and publication status to show a delivery result. The public information pages do not access your YouTube account.
The workspace processes these data internally only to connect the account, prepare the chosen upload, refresh authorization and display its status. It shares the selected upload data with Google/YouTube, and uses its configured hosting, database and private media-storage providers only to operate the service. It does not sell Google user data or share it with advertisers or data brokers. An operator of a self-hosted installation can access that installation's data and must apply its own access controls.
The public information pages do not set application login or advertising cookies. Cloudflare may process request data and use security cookies to deliver and protect this site. The separate authenticated workspace may store a session identifier in a browser cookie and receive standard device/browser request data, such as IP address and user agent, for login, security and service operation. We do not use these data for cross-site advertising. Connected-account credentials and publishing records are stored in the operator-controlled environment, not in this public information page. On the /youtube page, the embedded YouTube player sends basic browser data to YouTube when it loads to show the video and check playability; playback can send additional data. See the Google Privacy Policy linked below.
Google's own handling of information is described in the Google Privacy Policy.
Where your operational installation offers Disconnect, use it to remove that installation's active YouTube connection and credentials. You can independently revoke Google's authorization in Google Account security settings or Google Account connections. For removal of saved posts, media, delivery history or other stored data, follow the data deletion steps in the operational installation. Revoking Google access stops future API access but does not by itself erase local history or videos already uploaded to YouTube.
For privacy or deletion help with a local Content Distributor installation, use the contact provided by that installation's operator. This public information site lists the project's public contact below. The separate Xingyu Studio hosted workspace has its own signed-in request form for its TikTok data.
Facebook, Instagram and Threads data — November 6, 2026
You can connect Facebook Pages you manage, your Instagram professional account and your Threads profile through Meta's official authorization. We never ask for your Meta password. We store the account or Page identifier and name, your authorization tokens (encrypted at rest), the text and media you chose, and the identifiers and status of posts sent through the product.
Some data is read from Meta only when a signed-in member of your workspace opens the relevant page, and is not written to our database: account and post metrics, comments on your posts with the commenter's name or username, and Facebook Page and Instagram direct messages with the sender's name or username. Threads has no direct messages in the product. Meta includes a participant's email address in Facebook conversation data; we discard it on our server and never display or keep it.
Replies to comments, hiding comments, replies to direct messages and deleting posts happen only when a workspace member performs that action. We record that the action happened, who did it and for which account, but not the text. We do not send automated or bulk messages.
We use this data only to show it to members of the workspace that connected the account and to carry out their actions. We do not sell it, share it with advertisers or data brokers, use it for advertising, combine it with data from other sources, or use it to train AI models. Our hosting provider, Cloudflare, processes this data in transit to operate the service.
You can disconnect an account in the product, which removes its active tokens, or revoke access in your Facebook Business Integrations settings, Instagram Apps and websites settings, or Threads Website permissions settings. Disconnecting does not delete posts already published. To request removal of stored records, contact huhuwen09@gmail.com. Meta's handling of information is described in the Meta Privacy Policy.
Requests from government and public authorities — November 6, 2026
We do not sell user data, and we do not voluntarily give user data to any government or public authority. When a government or public authority asks for user data, we follow this procedure:
- We review the legal basis and scope of the request to confirm that it is valid.
- We challenge or refuse a request we consider unlawful or too broad.
- We disclose only the minimum data that the law requires.
- We keep a record of each request, our response, the legal reasoning and the parties involved.
LinkedIn data — October 29, 2026
You can connect your own LinkedIn profile, and LinkedIn Pages that you administer, through LinkedIn's official OAuth authorization. We never ask for your LinkedIn password. For your profile we request openid, profile and email to show which account is connected, and w_member_social to publish a post after you confirm it. For a LinkedIn Page we request rw_organization_admin to list the Pages where you are an administrator so you can choose one, w_organization_social to publish to that Page after you confirm, and r_organization_social to show the status of posts made through the product.
We store your LinkedIn member or Page identifier and name, your authorization tokens (encrypted at rest), the text and media you chose, and the identifiers and status of posts sent through the product. We do not collect data about other LinkedIn members, sell LinkedIn data, use it for advertising, or use it to train AI models. You can disconnect in the product, which removes the active tokens, or revoke access in LinkedIn's permitted services settings. Disconnecting does not delete posts already published on LinkedIn.
Pinterest data — updated November 2, 2026
Content Distributor lets you publish image and video Pins to a board you choose. You connect your own Pinterest account through Pinterest's official OAuth authorization; we never ask for your Pinterest password or session cookies. We request user_accounts:read to show which account is connected, boards:read to list your boards so you can choose one, boards:write because Pinterest requires it to add a Pin to that board (we do not create, edit or delete boards), and pins:read and pins:write to create a Pin after you confirm it and show its status.
We store your Pinterest username, your authorization tokens (encrypted at rest), the board, title, description, link and media you chose, and the identifiers and status of Pins created through the product. We do not collect other Pinterest users' data, sell Pinterest data, use it for advertising, or use it to train AI models. You can disconnect in the product or remove Content Distributor from the connected apps list in your Pinterest account settings. Disconnecting does not delete Pins already published on Pinterest. To request removal of stored LinkedIn or Pinterest records, contact huhuwen09@gmail.com.
Telegram data — October 29, 2026
Content Distributor publishes to a Telegram channel through our bot, @ContentDistributorXYBot. To connect a channel, you first add the bot as a channel administrator with permission to post, then log in with Telegram's official Login Widget. We never ask for your Telegram password, phone number or login codes. From the Login Widget we receive your Telegram user ID, name, username, profile photo link and login time, and we use them only to confirm with Telegram that you are the owner or a posting administrator of the channel you connect.
We store your Telegram user ID, the channel's ID and title, the text and media you chose, and the identifiers and status of messages sent through the product. The bot only posts messages you confirm and does not read your chats or other users' messages. We do not sell Telegram data, use it for advertising, or use it to train AI models. You can disconnect the channel in the product or remove the bot from your channel at any time. Neither deletes messages already posted.
Mastodon data — October 29, 2026
You can connect your own account on mastodon.social through Mastodon's official OAuth authorization; we never ask for your Mastodon password. We request read:accounts to show which account is connected, read:statuses to check that a post we published for you is still available, and write:statuses and write:media to publish a post and its media after you confirm it, or to delete it when you ask. We store your account ID and handle, your authorization token (encrypted at rest), the text and media you chose, and the identifiers and status of posts sent through the product. We do not collect other Mastodon users' data, sell Mastodon data, use it for advertising, or use it to train AI models. You can disconnect in the product or revoke access under Preferences → Account → Authorized apps on Mastodon. Disconnecting does not delete posts already published.
Tumblr data — October 29, 2026
You can connect your own Tumblr account through Tumblr's official OAuth authorization and choose one of your blogs; we never ask for your Tumblr password. We request basic to show your account and list your blogs, write to publish a post to the blog you chose after you confirm it, and offline_access so the connection keeps working without asking you to log in again. We store your Tumblr username, the blog you chose, your authorization tokens (encrypted at rest), the text and media you chose, and the identifiers and status of posts sent through the product. We do not collect other Tumblr users' data, sell Tumblr data, use it for advertising, or use it to train AI models. You can disconnect in the product or revoke access in Tumblr's account settings under Apps. Disconnecting does not delete posts already published. To request removal of stored Telegram, Mastodon or Tumblr records, contact huhuwen09@gmail.com.
Bluesky data — October 29, 2026
You can connect your own Bluesky account through Bluesky's official OAuth authorization (AT Protocol OAuth); we never ask for your Bluesky password or app passwords. You enter your handle, sign in on Bluesky's own page and approve access there. We request the atproto and transition:generic scopes, which Bluesky currently requires for an app to create posts and upload images to your account; we use this access only to publish a post and its images after you confirm it. We store your Bluesky DID and handle, the address of the server that hosts your account, your authorization tokens (encrypted at rest), the text and images you chose, and the identifiers and status of posts sent through the product.
We do not read your timeline, direct messages, follows or other users' data, sell Bluesky data, use it for advertising, or use it to train AI models. You can disconnect in the product or revoke the authorization in your Bluesky account settings at any time. Disconnecting does not delete posts already published. To request removal of stored Bluesky records, contact huhuwen09@gmail.com.
X data — November 1, 2026
You can connect your own X account through X's official OAuth 2.0 authorization; we never ask for your X password. We request users.read to show which account is connected, tweet.write to publish a post after you confirm it or delete it when you ask, media.write to upload the images or video you attached to that post, tweet.read to check that a post we published for you is still available, and offline.access so the connection keeps working without asking you to log in again. We do not request your email address, direct messages, follows or likes.
We store your X user ID and username, your authorization tokens (encrypted at rest), the text and media you chose, and the identifiers and status of posts sent through the product. We do not collect other X users' data, sell X data, use it for advertising, or use it to train AI models. You can disconnect in the product or revoke access in X under Settings → Security and account access → Apps and sessions → Connected apps. Disconnecting does not delete posts already published. To request removal of stored X records, contact huhuwen09@gmail.com.
Reddit data — October 28, 2026
A Reddit connection is planned for Content Distributor and is not yet available. It will be enabled only after Reddit approves our Data API access. This section describes how Reddit data will be handled once it is enabled.
You connect your own Reddit account through Reddit's official OAuth authorization. We never ask for your Reddit password. We request only the identity scope to show which account is connected, the submit scope to send a post after you confirm it, and the read scope to show the status of posts made through the product. A refresh token is kept only so that a post you scheduled can be sent at the time you chose.
We store your Reddit username, your authorization tokens (encrypted at rest), the subreddit, title and body you chose, and the identifiers and status of posts sent through the product. Every post is reviewed and confirmed by you before it is sent. We do not collect other Reddit users' data, sell Reddit data, use it for advertising, or use Reddit content to train AI models.
You can disconnect your Reddit account in the product, which removes its active tokens and cancels posts that have not been sent. You can also revoke access at any time in Reddit's authorized apps settings. Disconnecting or revoking does not delete posts already published on Reddit; delete those on Reddit. To request removal of stored Reddit records, contact huhuwen09@gmail.com.
Limited hosted private-draft workbench — October 8, 2026
A separate workbench is available at app.xingyuzhitong.com for Google identity sign-in, private media and unassigned drafts. Platform connections, scheduling and publishing are available only for the platforms enabled for a given workspace; the section for each platform in the Privacy Policy describes the data involved. Google identity scopes are openid, email and profile; this login is not YouTube channel authorization or public-upload approval.
The workbench uses a dedicated Cloudflare D1 database and private R2 media bucket. It stores the Google account identifier, name, verified email, profile image, session/request information, identity sign-in credential data, uploaded media and prepared draft content. Google and Cloudflare process the information needed for identity, hosting and storage. The workbench does not ask for a Google password and does not sell this data or use it for advertising or model training. The separate platform-connection backend's token-encryption design does not mean every identity or session field uses that application encryption.
The browser uses an HTTP-only session cookie, localStorage for the selected workspace and a versioned draft copy scoped to the user and workspace, and a short-lived sessionStorage context where platform authorization is enabled. Draft copies contain preparation text/settings and selected account identifiers, not OAuth access or refresh tokens; they are not cloud schedules. Use Clear draft or browser site-data controls to remove them. A displayed Google profile image may request Google's image service, which receives normal browser request data.
Deleting an unused private file removes its active object and metadata. Referenced media is protected. This does not remove a platform video or erase database recovery history, replicas or backups, and is not complete account deletion. Contact huhuwen09@gmail.com to request stored account-data removal. A request or active-file deletion receipt is not proof of complete erasure. Other installations and Xingyu Studio retain their separately described operating boundaries.