Platform API Data Use & Compliance
SkedCastconnects your social accounts and publishes to them on your behalf through each platform’s official API. This page consolidates, per platform, what we access, how we use it, how we comply with that platform’s developer policy, and the verbatim statements and disclosures the platforms require.
1. Our commitment across every platform
For every platform you connect, SkedCastfollows the same core commitments: we act only with your authorization and through the platform’s official OAuth flow; we use the access we obtain solely to schedule and publish the content you compose, at your direction; we store OAuth tokens (never your passwords) encrypted in our token vault; we do not sell platform data, use it for advertising, or use it for surveillance; we retain it only as long as the feature needs it; and we revoke and erase it on disconnection or on a deletion request. See our Privacy Policy, Data Deletion page, and Security page for the full detail.
2. Google API Services — Limited Use & YouTube
SkedCast uses YouTube API Services. Where you connect a Google service (the YouTube Data API), SkedCast makes the affirmative commitment required by the Google API Services User Data Policy:
SkedCast’s use of information received from Google APIs (including the YouTube Data API) will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In practice, we limit our use of YouTube API data to the upload and scheduling features that are prominent in SkedCast; we do not transfer it to third parties except as that policy permits (to provide those features with your consent, for security, or to comply with law); we do not let humans read it except in the narrow cases the policy allows; we never use it to serve advertisements or to determine credit-worthiness; and we never use it to train generalized AI or ML models.
The Google Privacy Policy governs Google’s handling of your data. By using SkedCast with YouTube you also agree to the YouTube Terms of Service — By using SkedCast you agree to be bound by the YouTube Terms of Service. You can review or revokeSkedCast’s access at any time at myaccount.google.com/permissions. On revocation through SkedCast we revoke the token and delete the authorized YouTube data; on revocation through your Google settings we delete related YouTube API data within the periods Google requires.
3. TikTok posting disclosures
Our composer implements TikTok’s required posting experience: it calls TikTok before composing to determine eligibility, shows your creator nickname and avatar, presents a privacy selector with no default value, reflects the interaction (Comment/Duet/Stitch) settings, and surfaces the commercial-content and music-usage disclosures. We never add promotional watermarks to your content or strip attribution. The two consent statements presented in the composer before publishing are, verbatim:
By posting, you agree to TikTok’s Music Usage Confirmation.
By posting, you agree to TikTok’s Branded Content Policy and Music Usage Confirmation.
4. Per-platform compliance
For each platform we integrate with, the following sets out what we access, the purpose, how we comply with that platform’s developer policy, the retention and deletion behavior, and a link to the platform’s own developer terms.
Meta — Facebook, Instagram & Threads
- We access your Page/professional-account identifiers and the OAuth access and refresh tokens needed to publish to the Facebook Pages, Instagram, and Threads you connect.
- We use it solely to schedule and publish the content you compose to your connected Meta accounts, at your direction.
- SkedCast complies with Meta — Facebook, Instagram & Threads’s developer policy: We use Meta Platform Data only to provide the SkedCast scheduling features you authorize, we never sell it or use it for surveillance, we limit retention to what those features need, and we expose Meta’s required data-deletion mechanism.
- Tokens are held encrypted while the account is connected and are revoked and erased on disconnection or on a deletion request; we honor Meta’s data-deletion requirements through our data-deletion page and callback.
Google — YouTube Data API
- We access your YouTube channel identifiers and the OAuth tokens needed to upload and schedule videos to the channel you connect.
- We use it solely to upload, schedule, and publish the videos you provide to your connected YouTube channel, at your direction.
- SkedCast complies with Google — YouTube Data API’s developer policy: SkedCast’s use of YouTube API data adheres to the Google API Services User Data Policy, including the Limited Use requirements; we only use the data for the upload/scheduling features visible in our product and never transfer or sell it for advertising or any unrelated purpose.
- Tokens are held encrypted while the channel is connected; on revocation through SkedCast we revoke the token and delete the associated authorized data, and on revocation through your Google security settings we delete related API data within the periods Google requires.
X (Twitter)
- We access your X account identifier and the OAuth tokens needed to post on your behalf.
- We use it solely to publish the posts you compose to your connected X account, at your direction.
- SkedCast complies with X (Twitter)’s developer policy: We act on your X account only with your express, informed consent, we keep any stored X content in sync with X (deleting it within 24 hours of deletion or request), and we do not redistribute or sell X content or match it to off-X data.
- Tokens are held encrypted while the account is connected and erased on disconnection; if you delete content on X or ask us to, we delete or update any corresponding stored copy promptly (within 24 hours).
TikTok
- We access your basic TikTok creator info and the OAuth tokens needed to post content on your behalf.
- We use it solely to publish the videos and photos you compose to your connected TikTok account, at your direction.
- SkedCast complies with TikTok’s developer policy: Our composer implements TikTok’s required posting disclosures — a non-default privacy selector, your creator nickname, the interaction toggles, and the commercial-content and Music Usage Confirmation statements — and we never strip attribution from your content or sell TikTok data.
- Tokens are held encrypted while the account is connected and erased on disconnection or on a deletion request.
- We access your member or organization identifier and the OAuth tokens needed to publish to your personal profile or to a Company Page you administer.
- We use it solely to publish the content you compose to your connected LinkedIn profile or Page, for your benefit and at your direction.
- SkedCast complies with LinkedIn’s developer policy: We use LinkedIn member data only to manage the profile or Page you connect — never for any other use case — we keep storage to what the feature needs, and we delete member data on request.
- We store only the member data needed to provide the posting feature, within LinkedIn’s storage limits, and we delete it on your request or when our access ends.
- We access your Pinterest business-account identifier and the OAuth tokens needed to create Pins and boards on your behalf.
- We use it solely to publish the Pins you compose to the boards you choose on your connected Pinterest account, at your direction.
- SkedCast complies with Pinterest’s developer policy: We follow the Pinterest Developer Guidelines: we publish only with your authorization, we do not share or sell Pinterest API data with third parties, and we delete stored access on request.
- Tokens are held encrypted while the account is connected and erased on disconnection or on a deletion request; we do not retain Pinterest data beyond what the posting feature requires.
Bluesky (AT Protocol)
- We access your handle/DID and the per-account credential or session needed to post on your behalf.
- We use it solely to publish the posts you compose to your connected Bluesky account, at your direction.
- SkedCast complies with Bluesky (AT Protocol)’s developer policy: We follow the Bluesky Developer Guidelines: SkedCast posts only at your direction, we provide a way to delete content and data on request, and we publish monitored contact information.
- Credentials are held encrypted while the account is connected and erased on disconnection or on a deletion request.
Telegram (Bot API)
- We access the bot token you configure and the channel/chat identifiers needed to post where your bot is an administrator.
- We use it solely to publish the messages you compose to the Telegram channels you choose, at your direction.
- SkedCast complies with Telegram (Bot API)’s developer policy: We follow the Telegram Bot Developer Terms: we store only the data needed to operate the integration, comply with applicable privacy law, and do not misuse Telegram branding.
- The bot token and channel references are held encrypted while configured and erased on disconnection or on a deletion request.
5. Platform-specific retention & deletion commitments
Several platforms impose specific storage or deletion rules, which we honor:
- X (Twitter) — we keep any stored X content current and delete or update it within 24 hours of deletion or modification on X, or on request; we do not redistribute or sell X content or match it to off-X data.
- YouTube— authorized YouTube data is refreshed or deleted within the periods Google requires; on a deletion request we delete it promptly, and on revocation through Google we delete related API data within Google’s window.
- LinkedIn— we store only the member data the posting feature needs, keep it within LinkedIn’s storage limits, and delete it immediately on your request or when your account or our access ends.
- Pinterest — we do not retain Pinterest API data beyond what the posting feature requires (tokens and identifiers), and we delete stored access on request.
- Meta — we delete Platform Data on request or when you no longer have an account, through the data-deletion mechanism below.
- TikTok, Bluesky & Telegram — stored tokens and identifiers are erased on disconnection or on a deletion request.
6. Revocation & deletion mechanism
You can disconnect any account at any time, which revokes and erases the stored tokens for that account. You can also request deletion of your account and all platform-derived data. We complete verified deletion requests within 30 days, as described on our Data Deletion & Account Removal page — the same page we provide to the platforms as our data-deletion instructions and as the Meta data-deletion callback URL.
7. Related policies & contact
This page works together with:
- Our Privacy Policy (including “Data from the platforms you connect”).
- Our Terms of Service (the “Connected third-party platforms” section, including the YouTube binding statement).
- Our Acceptable Use Policy (per-platform compliance, rate limits, and AI-content disclosure).
- Our Data Deletion page and Security page.
For any question about how SkedCast uses platform data, contact privacy@skedcast.com.