You can optionally provide ShortSync with access to your social media accounts to automatically publish your video content across multiple platforms. We only access this data when you use our multi-platform publishing features.
Platform-Specific Data Handling
Instagram/Facebook
What Data We Collect:
- Instagram Business account information
- Authentication tokens
- Publishing permissions
- If you set up comment-to-DM automation: the text of comments left on your posts, and the commenter's and comment's Instagram IDs
How We Use Data:
- Authentication (via Instagram/Facebook Login) and account verification
- Publishing videos to your creator account
- Managing video captions and settings as you specify
- Comment-to-DM automation: when a comment on your post contains a keyword you chose, we send that commenter one private message on your behalf, and an optional public reply under the comment. We check the comment text for your keywords and don't store it. The commenter's username and the matched keyword are used to personalize the message, and if you choose AI-written messages, the comment text is sent to Anthropic to write it (see Third-Party Service Providers below). We keep only the commenter's and comment's IDs and the send status, so the same person isn't messaged twice
Data Sharing and Disclosure:
- Instagram/Facebook data is never sold to third parties
- Data is not shared except when necessary to publish to your creator account
- We comply with Meta's Platform Terms and Instagram/Facebook API Terms of Use
Compliance and Security:
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from Instagram/Facebook APIs is encrypted using HTTPS/TLS
- Tokens are immediately deleted when you disconnect your Instagram/Facebook account
- You can revoke access at any time through your Instagram/Facebook Account settings
TikTok
What Data We Collect:
- TikTok creator account information
- Authentication tokens
- Video publishing permissions
- Privacy settings and content restrictions
- Your public video list and post statistics (views, likes, comments, shares)
- If you choose TikTok as a repurposing source: copies of your own TikTok posts (video and image files, captions and post dates), received through TikTok's Data Portability API. This is available for TikTok accounts in the EEA and UK.
How We Use Data:
- Authentication (via TikTok Login) and account verification
- Publishing videos to your TikTok account
- Managing video descriptions, privacy settings, and disclosures as you specify
- Showing your post analytics in ShortSync
- Importing your own TikTok posts into your ShortSync library, only after you connect TikTok and confirm, so you can republish them to the other accounts you choose, when you choose. We only request new posts while you have an active repurposing workflow, at most once a day.
Deleting Imported TikTok Data:
- Delete any imported post from your Library at any time
- Delete a repurposing workflow to stop future imports
- Delete your account in Settings to remove all your data, including every imported TikTok post
- Or request deletion at shortsync.app/data-deletion; we confirm by email once it is done, within 30 days
Data Sharing and Disclosure:
- TikTok data is never sold to third parties
- Data is not shared except when necessary to publish to your TikTok account, or to publish your imported TikTok posts to the other accounts you pick
- We comply with TikTok's Developer Terms of Service and API policies
Compliance and Security:
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from TikTok APIs is encrypted using HTTPS/TLS
- Tokens are immediately deleted when you disconnect your TikTok account
- You can revoke access at any time through your TikTok Account settings
YouTube (and Google Authentication)
ShortSync uses YouTube API Services to enable video publishing to your YouTube channel. By using ShortSync's YouTube integration, you also agree to the Google Privacy Policy.
What Data We Collect:
- YouTube channel name, channel ID, and profile picture
- Video upload permissions and channel capabilities
- OAuth2 refresh and access tokens for authenticating with YouTube API Services
- Video metadata (titles, descriptions, tags) that you provide for publishing
- Basic Google account information for authentication
How We Use Data:
- Authentication (via Google Login) and account creation
- Uploading videos to your YouTube channel
- Managing video metadata and upload settings as you specify
Data Sharing and Disclosure:
- Google data is never sold to third parties
- Data is not shared except when necessary to publish to your YouTube channel
- We do not transfer data for advertising or credit worthiness purposes
Compliance and Security:
- ShortSync's use of information received from Google APIs will adhere to Google API Services User Data Policy
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from Google/YouTube APIs is encrypted using HTTPS/TLS
- Tokens are immediately deleted when you disconnect your account
Revoking YouTube Access:
- You can disconnect your YouTube account from ShortSync at any time via the platform settings in your workspace, which will immediately delete your stored tokens
- You can also revoke ShortSync's access to your Google account by visiting your Google third-party app connections
- For complete data deletion (including all YouTube-related data stored by ShortSync), contact us at [email protected]
Snapchat
What Data We Collect:
- Snapchat account information (username, display name, avatar)
- OAuth access and refresh tokens
- Permissions for Snapchat Marketing API and Public Profile API (Story Studio) scopes you grant during sign-in
How We Use Data:
- Authentication (via Snapchat Login) and account verification
- Publishing videos to your Stories, Saved Stories, and Spotlight as you specify
- Managing captions and content settings you provide
Data Sharing and Disclosure:
- Snapchat data is never sold to third parties
- Data is not shared except when necessary to publish to your Snapchat account
- We comply with Snap's Snap Kit Terms of Service and Marketing API Terms
Compliance and Security:
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from Snapchat APIs is encrypted using HTTPS/TLS
- Tokens are immediately deleted when you disconnect your Snapchat account
- You can revoke access at any time through your Snapchat account's Connected Apps settings
LinkedIn
What Data We Collect:
- Your LinkedIn member ID (URN), full name (given and family name), and profile photo (avatar URL)
- For each LinkedIn Company Page you administer and elect to publish from: the Page URN, Page name, and Page logo, cached at connect time so you can choose a destination
- OAuth access token, refresh token, and token expiry timestamp, encrypted at rest
- The list of scopes you granted at connect time so the app knows what actions you have authorized
- Metadata about posts you publish through ShortSync: the post URN, publish timestamp, and any first-comment URN returned by LinkedIn
How We Use Data:
- Identifying which LinkedIn member you have connected, so the correct account name and avatar appear in the ShortSync dashboard
- Publishing posts and videos to your personal profile or Company Pages you administer, on the schedule you set
- Posting an optional first comment under each published post via the LinkedIn social actions API
- Applying the post visibility you choose (public, connections only, or logged-in members) at publish time
Data Sharing and Disclosure:
- LinkedIn data is never sold to third parties
- Data is not shared except when necessary to publish to your LinkedIn account or organization page
- We comply with the LinkedIn API Terms of Use and LinkedIn's Marketing Developer Platform policies
Compliance and Security:
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from LinkedIn APIs is encrypted using HTTPS/TLS
- When you disconnect LinkedIn from ShortSync, we immediately clear the stored access token and refresh token and mark the connection inactive so no further LinkedIn API calls can be made. Non-token metadata (member URN, name, avatar URL, cached Company Page list) is retained until you delete your ShortSync account, at which point the entire connection row is removed
- You can revoke access at any time through LinkedIn's Settings > Data Privacy > Permitted Services
X (Twitter)
What Data We Collect:
- X account information (username, display name, user ID)
- OAuth 2.0 access and refresh tokens
- Permissions for posting tweets, uploading media, and managing reply settings
- Community memberships you elect to publish to (when X Communities is used)
How We Use Data:
- Authentication (via X Login) and account verification
- Publishing posts and videos to your X account
- Managing reply settings, community targeting, and caption text as you specify
Data Sharing and Disclosure:
- X data is never sold to third parties
- Data is not shared except when necessary to publish to your X account
- We comply with the X Developer Agreement and Developer Policy
Compliance and Security:
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from X APIs is encrypted using HTTPS/TLS
- Tokens are immediately deleted when you disconnect your X account
- You can revoke access at any time through X's Settings > Security and account access > Apps and sessions
Threads
What Data We Collect:
- Threads account information (username, display name, profile picture)
- OAuth access and refresh tokens
- Publishing permissions for posts and replies on Threads
How We Use Data:
- Authentication (via Threads Login) and account verification
- Publishing posts, videos, and images to your Threads account
- Managing captions and content settings as you specify
Data Sharing and Disclosure:
- Threads data is never sold to third parties
- Data is not shared except when necessary to publish to your Threads account
- We comply with Meta's Platform Terms and the Threads API Terms of Use
Compliance and Security:
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from Threads APIs is encrypted using HTTPS/TLS
- Tokens are immediately deleted when you disconnect your Threads account
- You can revoke access at any time through Meta's Accounts Center connected apps settings
Bluesky
What Data We Collect:
- Bluesky handle and decentralized identifier (DID)
- App password and session tokens that you provide during connect
- Publishing permissions for posts and media uploads
How We Use Data:
- Authentication against your home PDS (Personal Data Server) and account verification
- Publishing posts, videos, and images to your Bluesky account
- Managing post text, language tags, and content settings as you specify
Data Sharing and Disclosure:
- Bluesky data is never sold to third parties
- Data is not shared except when necessary to publish to your Bluesky account via the AT Protocol
- We comply with Bluesky's Terms of Service and AT Protocol usage guidelines
Compliance and Security:
- App passwords and session tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from Bluesky/AT Protocol APIs is encrypted using HTTPS/TLS
- Credentials are immediately deleted when you disconnect your Bluesky account
- You can revoke access at any time by removing the app password through Bluesky's Settings > Privacy and security > App passwords
Pinterest
What Data We Collect:
- Pinterest account information (username, account type, profile image)
- List of boards you own (board name, board ID, privacy setting) so you can choose where to publish
- OAuth access and refresh tokens
- Permissions for boards:read, boards:write, pins:read, pins:write, and user_accounts:read scopes
How We Use Data:
- Authentication (via Pinterest Login) and account verification
- Publishing image and video pins to the board you select
- Optionally creating new boards on your behalf when you use the in-app "Create board" feature
- Managing pin titles, descriptions, alt text, and destination links as you specify
Data Sharing and Disclosure:
- Pinterest data is never sold to third parties
- Data is not shared except when necessary to publish to your Pinterest account
- We comply with the Pinterest Developer Guidelines, API Terms, and Acceptable Use Policy
Compliance and Security:
- OAuth tokens are stored securely in our database with access controls and row-level security policies
- All data transmitted to/from Pinterest APIs is encrypted using HTTPS/TLS
- Tokens are immediately deleted when you disconnect your Pinterest account
- You can revoke access at any time through Pinterest's Settings > Apps and websites
Discord
What Data We Collect:
- For each channel you connect, the webhook URL Discord creates when you authorize ShortSync for that channel (or that you paste in yourself), stored encrypted
- The channel's server name and icon, the IDs of the channel and server, and the name you give the channel in ShortSync
- When you use "Add a channel with Discord", we use Discord's sign-in once to read your server list for the server name, then revoke that access immediately
How We Use Data:
- Verifying the webhook and showing which channel is connected
- Publishing text, images, and videos to the channels you select, and deleting those messages when you ask us to
Data Sharing and Disclosure:
- Discord data is never sold to third parties
- Data is not shared except when necessary to publish to your Discord channels
- We comply with Discord's Terms of Service and Developer Policy
Compliance and Security:
- Webhook URLs are stored encrypted in our database with access controls and row-level security policies
- All data transmitted to/from Discord APIs is encrypted using HTTPS/TLS
- The webhook URL is deleted from ShortSync when you disconnect your Discord channel
- You can revoke access at any time by deleting the webhook in Discord's Server Settings > Integrations > Webhooks
Tumblr
What Data We Collect:
- OAuth access and refresh tokens, stored encrypted
- Your Tumblr username
- The list of your account's blogs (name, title, URL, and which one is your primary blog) so you can choose where to publish
- The IDs and links of posts you publish through ShortSync
How We Use Data:
- Authentication (via Tumblr's OAuth sign-in) and showing which account and blogs are connected
- Publishing text, photo, photo set, and video posts to the blog you select, and deleting those posts from Tumblr when you ask us to
Data Sharing and Disclosure:
- Tumblr data is never sold to third parties
- Data is not shared except when necessary to publish to your Tumblr blogs
- We comply with Tumblr's Terms of Service and API License Agreement
Compliance and Security:
- OAuth tokens are stored encrypted in our database with access controls and row-level security policies
- All data transmitted to/from Tumblr APIs is encrypted using HTTPS/TLS
- Tokens are deleted from ShortSync when you disconnect your Tumblr account
- Tumblr does not offer an API for revoking tokens, so to fully revoke ShortSync's access, remove ShortSync from your Tumblr settings at tumblr.com/settings/apps
Pixelfed
What Data We Collect:
- OAuth access and refresh tokens, stored encrypted
- The address of the Pixelfed server you connect (for example pixelfed.social)
- Your account ID, username, display name, avatar URL, and profile URL on that server
- The server's posting limits (such as caption length, album size, and file size) so we can check posts before publishing
How We Use Data:
- Authentication (via your Pixelfed server's OAuth sign-in) and showing which account is connected
- Publishing photos, videos, and albums to your account, posting first comments you set up, and deleting those posts when you ask us to
Data Sharing and Disclosure:
- Pixelfed data is never sold to third parties
- Data is only sent to the Pixelfed server you connect, when necessary to publish to your account
- We comply with the terms and policies of the Pixelfed server you connect
Compliance and Security:
- OAuth tokens are stored encrypted in our database with access controls and row-level security policies
- All data transmitted to/from Pixelfed servers is encrypted using HTTPS/TLS
- Tokens are deleted from ShortSync when you disconnect your Pixelfed account
- Pixelfed does not offer an API for revoking tokens, so to fully revoke ShortSync's access, remove ShortSync on your Pixelfed server under Settings > Applications
Google Business Profile
What Data We Collect:
- OAuth access and refresh tokens for the Google account you connect, stored encrypted
- Your Google account's name, email address and profile picture, to show which account is connected
- The Business Profile accounts and locations that account manages: location name, address, Google Maps link and whether Google lets the account post to it
- The IDs and links of the posts we publish for you, so you can open and delete them from ShortSync
How We Use Data:
- Showing your locations so you can pick where to post
- Publishing the updates you create or schedule to the locations you select, and deleting those posts when you ask us to
- We don't read or change your business information, reviews, photos or messages
Data Sharing and Disclosure:
- Google Business Profile data is never sold to third parties
- Data is not shared except when necessary to publish to your Business Profile
- ShortSync's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements
Compliance and Security:
- Tokens are stored encrypted in our database with access controls and row-level security policies
- All data transmitted to/from Google APIs is encrypted using HTTPS/TLS
- When you disconnect Google Business Profile, we revoke ShortSync's access with Google and delete the tokens
- You can also revoke access at any time in your Google Account under Security > Your connections to third-party apps & services
Reddit
We connect to Reddit through our publishing partner bundle.social. You sign in on Reddit's own authorization page, and bundle.social holds the Reddit access tokens on our behalf. ShortSync never sees your Reddit password.
What Data We Collect:
- Your Reddit username, avatar and account ID, to show which account is connected
- The bundle.social reference for your connection (stored in our database; the Reddit tokens themselves stay with bundle.social)
- The subreddits you can post in and their post flairs, fetched when you choose where to post
- The IDs and links of the posts we publish for you, so you can open them from ShortSync
How We Use Data:
- Authentication (via Reddit's OAuth sign-in) and account verification
- Publishing the video, image and text posts you create or schedule to the subreddit or profile you select, with the title, flair and NSFW setting you choose
- We don't read your messages, votes, comments or browsing history on Reddit
Data Sharing and Disclosure:
- Reddit data is never sold to third parties
- Post content and settings are shared with bundle.social and Reddit only to publish to your account
- We comply with Reddit's User Agreement and Developer Terms
Compliance and Security:
- Connection data is stored in our database with access controls and row-level security policies
- All data transmitted to/from bundle.social and Reddit is encrypted using HTTPS/TLS
- When you disconnect Reddit, we remove the account from bundle.social and delete the connection from ShortSync
- You can also revoke access at any time on Reddit under reddit.com/prefs/apps
The only way our Service accesses your social media data is after you explicitly accept our Privacy Policy and provide us with the right to connect to your accounts. We are fully compliant with each platform's API requirements and developer policies.
The use and transfer of information received from social media platform APIs will adhere to each platform's respective developer policies and data use requirements, including any limitations on data usage and sharing.