Connected-Platform Data

Simplee uses OAuth so you can authorize specific media-pipeline actions without giving Simplee your platform password. The provider shows the permissions before you approve them, and the backend—not this public website—handles the resulting credentials.

Rules for every connection

• Simplee requests the least-privilege scopes needed for the feature you choose.
• Client secrets, access tokens, and refresh tokens are never placed in public HTML, browser logs, media, prompts, or support messages.
• A media action is bound to the selected account, exact media, metadata, and approval state.
• Simplee does not sell connected-platform data or use it for unrelated advertising or surveillance.
• Disconnecting stops new actions; provider revocation invalidates the provider grant.

TikTok

The planned initial TikTok integration is designed for Sandbox qualification with the Content Posting API’s video.upload permission. It does not receive that permission until TikTok authorizes the target account and scope and the endpoint and credential controls pass testing. Once enabled, it can send an authorized video to the creator’s TikTok inbox as a draft; the creator must finish editing and posting inside TikTok. Simplee may then store the TikTok account identifier, display information, granted scopes, token status, publish/upload identifier, upload status, failure reason, and the approval record. Direct Post and public posting are separate capabilities and are not inferred from draft-upload permission.

Instagram / Meta

For an eligible professional account, Simplee may request account identity, content-publishing, and permitted insights access. Simplee may store the selected account, media-container and publishing identifiers, status, permalink, approved caption, and permitted metrics. Consumer-account access is not routed through an unofficial workaround.

YouTube / Google

The existing YouTube integration is pilot-only until its exact scopes, user-facing disconnect control, token revocation, and deletion workflow pass qualification. If enabled, Simplee may request YouTube upload, channel-management, read-only channel, and analytics permissions needed for the selected workflow. It may store the channel identity, granted scopes, upload session state, video identifier, visibility, processing status, and permitted analytics. YouTube API Data is kept distinct from other-platform data and is not used for custom content or channel scores, audience inferences, or external-model content ratings. Permitted YouTube reporting remains clearly identified as YouTube-sourced. You can also revoke access in Google Security Settings. Google’s OAuth screen and YouTube API Services policies also apply.

Planned and research-stage providers

The providers below are in Simplee’s adapter catalog, but they are not treated as connected merely because they appear here. Before enabling one, Simplee must publish the exact data categories and scopes, implement the provider’s supported authorization flow, present the connection during onboarding, and pass a provider-specific review. A roadmap entry grants no permission to collect data or act on an account.

Threads and Facebook Pages

A future Meta connection may handle the selected professional profile or Page identity, granted permissions, approved media and text, media-container and post identifiers, delivery status, permalink, and permitted account or post insights. Instagram, Threads, and Facebook grants are recorded separately even when Meta provides a shared developer application.

X (formerly Twitter)

A future X connection may handle the authorized user identity, granted permissions, approved text and media, media-upload and post identifiers, delivery status, permalink, and permitted public or account insights.

Bluesky and Mastodon

A future decentralized-network connection may handle the selected handle, decentralized identifier or server domain, the authorization credential, approved content, blob and post identifiers, delivery status, permalink, and available public engagement data. Credentials remain backend-only, and each account or server connection is independently revocable.

Snapchat and Pinterest

A future connection may handle an eligible Public Profile, creator or business account, selected board, granted permissions, approved media and metadata, publishing identifiers, delivery status, permalink, and permitted analytics. Simplee will not substitute consumer-session automation where an official publishing capability is unavailable.

WeChat Official Accounts

A future WeChat connection may handle an authorized Official Account or other supported business identity, granted permissions, approved media and messages, media and publication identifiers, delivery status, and permitted analytics. It requires a separate regional, data-transfer, retention, and provider-policy review before implementation.

LinkedIn and other future adapters

A future LinkedIn connection may handle the selected member or organization identity, granted permissions, approved content, media and post identifiers, delivery status, permalink, and permitted analytics. Any provider added later must satisfy the same disclosure, least-privilege, consent, revocation, deletion, security, and review requirements.

Retention and deletion

Active connection credentials are retained while needed to provide the authorized feature and are deleted or invalidated after disconnection, revocation, expiry, or account deletion, subject to limited secure backups and legal obligations. Delivery and audit records may be retained separately to document the action you requested, resolve failures, and prevent duplicate uploads. Published posts remain subject to the destination platform and may require deletion there.

To disconnect, revoke, export, or delete data, follow Data Requests & Revocation.