Platform integrations

Last updated: 7 May 2026

This page describes how GuildOS connects to third-party creator platforms — what data we request, what consent the user gives, and how we comply with each platform's developer policies. It is written for the customers who entrust their accounts to us, and for the platform-developer reviewers who evaluate our integrations.

1. The integration model, in one paragraph

GuildOS is a multi-tenant SaaS. Each customer creates an isolated workspace, connects their own platform accounts via the platform's official OAuth flow, and authorises GuildOS to act on their behalf within scopes they explicitly grant. GuildOS never operates on accounts the customer doesn't own or hasn't connected, and never posts without an explicit per-post confirmation by the customer (or by a schedule the customer has set up and reviewed).

2. The TikTok integration

2.1 Audience and use case

GuildOS is offered as a paid subscription to creators, freelance producers, and creator agencies who need to plan and publish content across multiple platforms. It is sold and delivered to a wide, public audience through three storefronts (Lemon Squeezy, Gumroad, GitHub Sponsors) and is not limited to any internal group. The same fleet has produced eleven publicly-listed iOS apps, listed on our /apps page — concrete evidence that GuildOS is a working content-and-product factory, not a personal automation.

2.2 Scopes requested

The TikTok integration requests four scopes through TikTok Login, and only with the customer's explicit consent at OAuth time:

• user.info.basic — display name, avatar, open ID, union ID. Used to identify which connected account the customer is operating in.
• video.list — list of videos posted by the connected account. Used to associate posts created through GuildOS with their TikTok counterparts and to surface basic post-level metrics back to the customer's analytics.
• video.publish — permission to publish video on the customer's behalf, used only when the customer (or a schedule the customer has configured) confirms publication.
• video.upload — permission to upload video files for publication via the Content Posting API.

2.3 The posting flow

GuildOS implements TikTok's Content Posting API consent UX requirements without exception. For every post that goes through our integration, the customer:

• Sees the connected creator's nickname displayed in the upload UI, so it is unambiguous which TikTok account will receive the post;
• Sees a content preview of the video and any preset text, with the ability to edit the title, hashtags, and any other user-facing fields before publishing;
• Manually selects the privacy status from the options TikTok's creator_info API returns — there is no default;
• Manually opts in to each interaction setting (Comment, Duet, Stitch). None are pre-checked, and any setting the creator has disabled in their TikTok app settings is greyed out;
• Discloses commercial content (Your Brand and/or Branded Content) where applicable. The publish button is disabled if the disclosure toggle is on and no sub-option is selected;
• Acknowledges TikTok's Music Usage Confirmation and, when applicable, the Branded Content Policy before the publish button is enabled.

GuildOS calls TikTok's creator_info endpoint before every post to verify the creator can still post and that the video meets their max_video_post_duration_sec. If the creator has hit their posting cap, the publish attempt is stopped and the customer is asked to retry later.

2.4 What we do not do

We never:

• superimpose GuildOS branding, watermarks, logos, or links on content posted to TikTok;
• copy arbitrary content from other platforms into TikTok on the customer's behalf;
• remove or interfere with creator copyright mechanisms (watermarks, music attribution) on third-party content;
• use TikTok data outside the customer's own workspace, or for advertising, profiling, or AI model training;
• sell, share, or rent TikTok-derived data to third parties.

2.5 Token storage and revocation

OAuth access and refresh tokens are stored encrypted at rest, and used only to fulfil the customer's own publishing requests. The customer can revoke GuildOS's access at any time from inside our application or directly from their TikTok account's connected-apps settings. On revocation we delete the tokens and purge cached TikTok data within 30 days. Full detail in our Privacy Policy.

3. The YouTube integration

The YouTube integration follows the same multi-tenant, explicit-consent model as TikTok. GuildOS uses the official YouTube Data API and Content ID-respecting upload paths under the scopes the customer authorises. Customer credentials are encrypted at rest and used only to fulfil that customer's publishing requests.

4. Compliance and contact

Our use of each platform's APIs is governed by our Terms of Service, our Privacy Policy, and the developer policies of each integrated platform — including, without limitation, the TikTok Developer Guidelines and TikTok Developer Terms of Service.

For platform-developer review correspondence, security disclosures, and any technical question about the integrations described above, write to developer@guild-os.net.