OpBuildX Uploader Privacy Policy

Last updated October 29, 2026.

This is the privacy policy for OpBuildX Uploader, the app named in the Google and TikTok developer applications for opbuildx.com. It explains what OpBuildX Uploader collects when a Google account or a TikTok account is connected, why that information is collected, who receives it, how it is protected, and how long it is kept.

The public pages at opbuildx.com can be read without an account. This policy also covers those pages.

OpBuildX Uploader’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who operates OpBuildX Uploader

OpBuildX Uploader is operated by the owner of opbuildx.com. Privacy requests, including deletion, go to hello@opbuildx.com.

Google and YouTube data

This section applies only to data received from Google APIs (YouTube, YouTube Analytics, and Google Drive). TikTok data is covered separately in the TikTok data section.

Google user data OpBuildX Uploader accesses

When the account owner connects Google, OpBuildX Uploader requests the scopes below. Each scope returns only the data described. OpBuildX Uploader does not receive the Google account password.

• YouTube account management (https://www.googleapis.com/auth/youtube and https://www.googleapis.com/auth/youtube.force-ssl). YouTube returns the connected channel’s identity, playlists, and video details that the account can manage, including titles, descriptions, and privacy settings. These calls are made over HTTPS.
• YouTube video upload (https://www.googleapis.com/auth/youtube.upload). YouTube accepts the video file the account owner asks OpBuildX Uploader to publish, plus the title, description, and privacy status sent with that file, and returns the video id of the upload.
• YouTube partner and channel audit (https://www.googleapis.com/auth/youtubepartner and https://www.googleapis.com/auth/youtubepartner-channel-audit). YouTube returns partner features and channel-audit details tied to the connected channel.
• YouTube Analytics (https://www.googleapis.com/auth/yt-analytics.readonly). YouTube Analytics returns read-only reports for the connected channel, such as views, watch time, and related performance figures. OpBuildX Uploader cannot change the channel through this scope.
• Google Drive file access (https://www.googleapis.com/auth/drive, https://www.googleapis.com/auth/drive.photos.readonly, and https://www.googleapis.com/auth/drive.appdata). Drive returns the files and folders the connected account can access, including file names, file contents, and the metadata needed to store and move those files. Photo files are read only. The app-data scope is limited to the hidden folder Google Drive reserves for this app.

How OpBuildX Uploader uses Google user data

OpBuildX Uploader uses Google user data only to run the content pipeline the account owner connected:

• To upload and publish videos to the connected YouTube channel.
• To pull YouTube Analytics for those videos and that channel.
• To store and move video files, captions, thumbnails, and related pipeline files in the connected Google Drive.

OpBuildX Uploader does not use Google user data for any other purpose. It does not use Google user data for advertising, and it does not sell Google user data.

With whom Google user data is shared, transferred, or disclosed

Google user data is shared only with the account owner’s own connected Google account and with the OpBuildX Uploader backend that performs the action the account owner requested. A video upload is sent to that user’s YouTube channel. A Drive file is read or written in that user’s Drive. Analytics figures are retrieved for that user’s channel.

OpBuildX Uploader does not sell Google user data. OpBuildX Uploader does not share, transfer, or disclose Google user data with third parties for advertising. OpBuildX Uploader does not share Google user data with an advertising network or a data broker.

How OpBuildX Uploader protects Google user data

Sensitive Google user data, including OAuth access tokens and refresh tokens, is protected as follows:

• Encryption in transit. The site and every call to Google APIs use HTTPS.
• Access is limited to the authenticated user. A token is used only for the Google account that granted it. OpBuildX Uploader does not use one person’s Google token to act on another person’s account.
• Tokens are stored encrypted on the OpBuildX Uploader server. A refresh token is used only to obtain a new access token when the current access token expires.

Retention and deletion of Google user data

OpBuildX Uploader keeps Google access tokens, refresh tokens, and the associated Google user data (channel identity, video ids, analytics pulls, and Drive file references held for the pipeline) only while the Google account stays connected.

When the account owner disconnects the Google account, or emails a deletion request to hello@opbuildx.com, OpBuildX Uploader deletes those tokens and the associated Google user data within 30 days. OpBuildX Uploader does not retain Google user data indefinitely. A copy is kept longer only when a law requires it.

TikTok data

This section applies only to data received from TikTok through TikTok Login Kit and the Content Posting API. Google data is covered separately in the Google and YouTube data section.

TikTok permissions (scopes) and what each is used for

Scope	What TikTok shares or allows	What OpBuildX Uploader uses it for
user.info.basic	Basic profile information, such as the account identifier (open id), display name, and avatar.	To identify the connected account, attach each upload to it, and show the account name and avatar in the dashboard so the owner knows where a video will go.
video.upload	Permission to upload a video to the connected account’s TikTok inbox.	To send the video the account owner chooses to their own TikTok inbox, where the owner adds the caption and finishes the post in the TikTok app.

Tokens TikTok issues for these scopes are encrypted before they are stored on the OpBuildX Uploader server and are used only for the account that granted them. OpBuildX Uploader does not sell TikTok data and does not use it for advertising. The account owner can revoke access at any time in TikTok’s settings (Manage apps) or by emailing hello@opbuildx.com; retention and deletion are described below.

Information OpBuildX Uploader collects from TikTok

OpBuildX Uploader collects only the information needed to connect one TikTok account and to upload videos to that account.

TikTok login. OpBuildX Uploader uses TikTok Login Kit. The account owner signs in on TikTok. TikTok sends an authorization code to the redirect URI https://site.opbuildx.com/callback. OpBuildX Uploader exchanges that code for an access token and a refresh token. The authorization code is not kept after the exchange. The tokens are stored encrypted on the OpBuildX Uploader server.

With the tokens, OpBuildX Uploader stores the TikTok account identifier (open id), the permission scope TikTok granted, the token type, and the expiry times TikTok returns for the access token and the refresh token. The scopes requested at login are user.info.basic and video.upload. OpBuildX Uploader does not ask TikTok for the account password, and the password is never sent to opbuildx.com.

Video uploads. When the account owner sends a video through OpBuildX Uploader, the app collects only the video file; there is no caption field. OpBuildX Uploader receives a working copy on its server and sends the video file to the connected account’s TikTok inbox. The account owner adds the caption and chooses privacy and other posting settings in the TikTok app when finishing the post.

Operations log. OpBuildX Uploader keeps a server log of each upload attempt. The log can include the video file name, the result, the TikTok upload identifier when TikTok returns one, the upload status, and the time of the attempt.

Messages you send us. If you email hello@opbuildx.com, OpBuildX Uploader receives the address you write from and the message you send, so the request can be answered.

This website. The public pages do not require an account. They do not set advertising cookies or analytics cookies. They do not ask visitors to sign in.

Why OpBuildX Uploader collects TikTok information

• To complete TikTok login and keep the connection so a later upload uses the same account.
• To attach each upload to the TikTok account that authorized it, using the open id.
• To send the video file to the connected account’s TikTok inbox.
• To record whether an upload succeeded, so a failed upload can be retried and a successful one is not treated as unfinished.
• To answer a disconnect request, a deletion request, or another message sent to the contact address.

OpBuildX Uploader does not use this information to sell advertising, and it does not use it to post to any TikTok account other than the one that was connected.

Who OpBuildX Uploader shares TikTok information with

OpBuildX Uploader shares the video file and the authorization TikTok requires with TikTok, because that is how the upload the account owner requested is delivered. TikTok’s own privacy policy applies to information TikTok holds after the post.

Email sent to the contact address is received through the email provider for hello@opbuildx.com, which processes the message in order to deliver it.

OpBuildX Uploader does not sell personal information. OpBuildX Uploader does not buy personal information from data brokers. OpBuildX Uploader does not share personal information with an advertising network. Google user data is covered by the sharing section above.

How long OpBuildX Uploader keeps TikTok information

Access tokens, refresh tokens, the open id, the granted scope, and token expiry information are kept while the TikTok account stays connected, so later uploads can be made for that account. The login service also limits stored token records and drops the oldest records once that limit is reached.

The authorization code is discarded after it is exchanged for tokens.

A working copy of a video stays on the OpBuildX Uploader server so the upload can be prepared and sent. It is not published anywhere except the connected TikTok account.

The operations log is kept so the result of an upload can be checked.

After the account owner disconnects TikTok, or after a deletion request, OpBuildX Uploader deletes the tokens, the open id and related login fields, the video working copies, and the operations-log entries for that account within 30 days. A copy is kept longer only when it is required to meet a legal obligation. Google user data follows the 30-day deletion rule in the Google section above.

How OpBuildX Uploader protects TikTok information

Access tokens and refresh tokens are encrypted before they are written to disk. The OpBuildX Uploader server is access-controlled. No method of storage is perfect. The account owner can disconnect and request deletion at any time. Google tokens are protected as described in the Google section above, including encryption in transit over HTTPS.

Children, your requests, and changes

Children

OpBuildX Uploader is not directed to children under 13. A person who connects a TikTok or Google account must meet that service’s minimum age. OpBuildX Uploader does not knowingly collect personal information from a child under 13. If you believe a child’s information was submitted, email hello@opbuildx.com and OpBuildX Uploader will delete it.

Your requests

You may ask OpBuildX Uploader what Google user data, TikTok login data, video working copies, and upload-log entries it holds for the accounts you connected. You may ask OpBuildX Uploader to delete that information, or to disconnect the account. Email hello@opbuildx.com from an address that lets the operator identify the account. OpBuildX Uploader completes a deletion request within 30 days, except where a copy must be kept to meet a legal obligation. Google user data is not retained indefinitely.

Disconnecting TikTok or Google inside that service’s own settings stops future use of the old authorization. Sending the email above is how you ask OpBuildX Uploader to delete the copies it still holds.

Changes to this policy

If this OpBuildX Uploader Privacy Policy changes, the updated policy will be posted at this URL with a new “last updated” date. The prior version is replaced by the page you are reading.