Privacy Policy

Last Updated: November 9, 2026

This Privacy Policy explains what data ShortSync collects, how we use it, and your rights. We collect personal information only when necessary to provide our services, with your knowledge and consent, and we don't share it publicly or with third parties except when required by law or to publish to your connected platforms.

You can refuse to provide information, but this may limit some services. External links are subject to their own privacy policies.

Information We Collect

Information You Provide Directly

  • Account information
  • Video content you upload to our service
  • Video metadata
  • Billing and payment information (processed by Stripe)
  • Communications with our support team

Information Collected Automatically

  • Device information (device model, operating system and version, app version)
  • IP address and approximate location derived from it
  • Usage analytics such as screens visited, features used, and session duration (collected via PostHog; see Third-Party Service Providers below)
  • Crash reports and error logs
  • Server request logs (timestamps, endpoints accessed, response codes)

Information from Social Media Platforms

  • Authentication tokens and access credentials
  • Basic profile information
  • Account verification status and permissions
  • Platform-specific creator information and capabilities

Information from Connected Content Sources

  • Sign-in tokens or API keys for the sources you connect
  • Basic account details from the source (account ID, name or email, and profile picture if the source provides one)
  • The files you choose to import, and their details

See Content Import Integrations below for details on each source.

Information from Connected AI Clients (MCP)

  • Name and redirect URI of each AI client you connect via OAuth 2.0 Dynamic Client Registration
  • OAuth access and refresh tokens issued to that client, stored as SHA-256 hashes only
  • Scopes granted at consent time (read, write, or both)
  • Connection metadata: when the client was connected, when it was last used, when it was revoked

How We Use Your Information

We use the information we collect for the following purposes:

  • Service Delivery: To provide our core video distribution service across multiple social media platforms
  • Account Management: To create and maintain your user account, authenticate access, and verify your identity
  • Platform Authentication: To establish and maintain connections with your social media accounts for content publishing
  • Content Processing: To upload, process, and distribute your video content according to your preferences
  • Customer Support: To respond to your inquiries, troubleshoot issues, and provide technical assistance
  • Service Improvement: To analyze usage patterns and improve our features, performance, and user experience
  • Security: To detect and prevent fraud, abuse, and unauthorized access to our services
  • Legal Compliance: To comply with applicable laws, regulations, and legal processes
  • Communication: To send you service-related notifications, updates, and promotional materials (with your consent)

Data Retention

We retain your information for different periods depending on the type of data:

  • Account Information: Retained while your account is active and for a reasonable period after account deletion
  • Uploaded Video Files: Retained while your account has active paid access or ongoing free-tier activity. In line with data minimization principles, we automatically remove the original video files from our storage 30 days after a paid subscription ends (with email notice at cancellation and reminders at approximately 15 days and 3 days before removal), and after 60 days of inactivity on free accounts (with reminder emails during the window). You can delete individual videos at any time from the app. Signing back in, resubscribing, or being covered by another organization's active paid subscription before the removal date cancels the removal.
  • Video Metadata: Identifiers, captions, publication history, and analytics aggregates for published posts are retained after the underlying video file is removed, so your record of what you posted and how it performed remains intact
  • Authentication Tokens: Stored securely until you disconnect a platform or content source, or revoke access
  • Imported Files: Treated the same as Uploaded Video Files above. Disconnecting a content source doesn't remove files you already imported
  • Usage Analytics: Aggregated and anonymized data may be retained as needed for service improvement purposes
  • Server Logs: Retained for operational purposes and automatically purged on a regular basis
  • Billing Information: Retained by Stripe according to their retention policies and legal requirements

Full retention windows, exact triggers, and the exceptions for team workspaces on paid organizations are described in Section 17 (“Content Retention and Deletion”) of our Terms of Service.

Social Media Platform Integration

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.

Content Import Integrations

You can optionally import photos, videos and documents into ShortSync from other services. We only access a source when you connect it and use it. Each source's own privacy policy and terms also apply to your account there.

What Data We Collect:

  • The sign-in tokens or API key for the source, encrypted with AES-256-GCM. For a pasted API key we also keep its last four characters, so you can recognize it in Settings
  • Basic account details from the source: your account ID, your name or email, and your profile picture if the source provides one
  • A copy of each file you import, stored with your other uploads
  • Details of each imported file: its name, size and type, which source it came from and its ID at that source, plus any title or caption the source provides

How We Use Data:

  • Showing your files or items from the source so you can pick them, and importing the ones you choose
  • Publishing and scheduling imported files where you tell us to
  • Running the automation workflows you set up, as described under Twitch and RSS below
  • We only copy what you import, never the rest of your account at the source. We don't change, move or delete anything there
  • A source connection belongs to you and isn't shared with teammates. Files you import go into the workspace you import them to, so members of that workspace can see them

Sources:

  • Google Drive: You pick files in Google's file picker. We use Google's per-file access, so we can only open the files you pick
  • Google Photos: You pick photos and videos in Google's own picker. Our access is read-only and limited to the items you pick, so we can't see the rest of your library
  • Dropbox: Nothing to connect, and we store no Dropbox token. You pick files in Dropbox's own window, which gives us a temporary link to each file. We remove the link once the import ends
  • Box: You browse your folders in ShortSync. Box shows this access as “read and write” because it only lets apps download files with write access, but we only read
  • OneDrive: You sign in with Microsoft and browse your files in ShortSync. Our access is read-only
  • Frame.io: You sign in with your Adobe ID and browse your projects and folders in ShortSync
  • Canva: You sign in with Canva and pick designs, which we import as images or videos. Our access to your designs is read-only
  • Twitch: You sign in with Twitch and pick clips from your channel. If you set up a repurposing workflow, we also check your channel for clips and import them automatically until you pause or delete the workflow or disconnect Twitch
  • Klap: You sign in with Klap and pick clips, which come with the caption Klap wrote
  • OpusClip, HeyGen and Descript: You paste an API key or token from that service, and we use it to list and import your clips, videos or compositions. It can do whatever that service allows the key to do, but we only use it to read and import
  • Adobe Express add-on: You sign in to ShortSync inside the add-on, and it sends us the pages you choose to send
  • Import from a link: We download the file at the link you paste and keep that link with the file
  • RSS and podcast feeds: No account is needed. If you set up a repurposing workflow, we check the feed URL you give us for new items until you pause or delete the workflow

Google User Data:

  • ShortSync's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements
  • We use Google Drive and Google Photos data only to import the items you pick and post them where you tell us to
  • We don't sell this data, use it for advertising, or use it to train AI models
  • It is only shared with the service providers listed below that run ShortSync, and with the platforms you publish to
  • People at ShortSync don't read this data unless you ask us to (for example in a support request), or it is needed for security or to comply with the law

Disconnecting and Revoking Access:

  • You can disconnect a source at any time in Settings → Integrations, which immediately deletes your stored tokens or API key
  • For Google Drive, Google Photos, Twitch, Canva and Box we also ask the service to revoke our access
  • For OneDrive, Frame.io and Klap, you can also remove ShortSync in your account settings at that service
  • For OpusClip, HeyGen and Descript, delete the API key at that service if you no longer want to use it
  • You can revoke Google access at any time in your Google third-party app connections
  • Files you already imported stay in your ShortSync library until you delete them, or until they are removed as described in Data Retention. Deleting your account removes your connections and imported files

AI Client Integration (Model Context Protocol / MCP)

ShortSync offers an optional MCP endpoint that lets you connect third-party AI clients (Claude Desktop, Cursor, and any other Model Context Protocol client) to your ShortSync account. When you connect an AI client and grant it access, that client can act on your behalf within the scopes you choose.

What Data We Collect:

  • The name and redirect URI of any AI client you connect, registered via OAuth 2.0 Dynamic Client Registration
  • OAuth 2.0 access and refresh tokens issued to that client (stored as SHA-256 hashes only; plaintext is never persisted after issuance)
  • The scope you granted at consent time (shortsync:read, shortsync:write, or both)
  • Usage metadata: when each connection was created, when it was last used, and when it was revoked

What AI Clients Can Do On Your Behalf:

Subject to the scopes you granted at consent time, a connected AI client can:

  • Read your ShortSync profile, workspaces, organizations, and platform connections
  • Read post drafts, scheduled posts, analytics, and inbox conversations
  • Create video upload records, including by fetching a video from a URL you provide to the AI client
  • Create, update, schedule, publish, or cancel post drafts across your connected platforms
  • Reply to comments on posts you have published

Actions taken by a connected AI client are treated as your own actions under our Terms of Service. Content the AI client publishes on your behalf reaches your connected social media platforms using the same OAuth tokens described above, and is subject to the same platform policies.

Data Sharing and Disclosure:

  • MCP tokens are never shared with any third party
  • The prompts and messages you send to the AI client stay with that client's operator (for example, Anthropic or Cursor). They do not flow through ShortSync
  • ShortSync only receives the tool calls the AI client makes to our MCP endpoint and the arguments included in those calls

Compliance and Security:

  • Access and refresh tokens are stored as SHA-256 hashes only. The plaintext is returned to the AI client once at issuance and is not retrievable afterward
  • Access tokens expire after 1 hour; refresh tokens after 30 days. Refresh tokens rotate on every use, and reuse of a revoked refresh token triggers revocation of the entire token family for that client and user (RFC 6819 §5.2.2.3)
  • All MCP requests are rate-limited per IP and per token to prevent abuse
  • All traffic to and from the MCP endpoint is encrypted using HTTPS/TLS

Revoking AI Client Access:

  • You can revoke any connected AI client at any time from Settings → API, MCP & webhooks. Revocation takes effect immediately and the client's next tool call will fail
  • Revoked token rows are retained with a revoked_at timestamp for audit purposes and are automatically excluded from further authentication
  • For complete removal of all MCP connection data, contact us at [email protected]

Third-Party Service Providers

We use the following third-party services to operate ShortSync. These providers process data on our behalf under contractual obligations to protect your information:

  • Supabase — Authentication and database hosting. Stores your account credentials (email/password hashes), profile data, platform connections, and post metadata. Hosted in the EU (Frankfurt).
  • PostHog — Product analytics. Collects anonymized usage events (pages visited, features used, session duration) to help us improve the service. Hosted in the EU. You can opt out of analytics tracking in your account settings.
  • Stripe — Payment processing. Handles all billing and subscription management. We do not store your credit card details; Stripe retains payment data per their own privacy policy.
  • Amazon Web Services (AWS) — File storage. Uploaded video and image files are stored in AWS S3 and served via CloudFront CDN. Files are encrypted at rest and in transit.
  • Upstash (QStash) — Message scheduling. Handles timed delivery of scheduled posts and queues comment-to-DM messages. For scheduled posts it receives only post identifiers and timestamps, no video content. A queued comment DM carries the commenter's username and the matched keyword, plus the comment text when AI-written messages are on, until it is sent.
  • Amazon SES — Transactional email. Sends account-related emails (verification, password reset, notifications). Receives only your email address and the content of each email.
  • Hetzner — Production application hosting. Our application servers run on Hetzner infrastructure in the EU (Finland).
  • Anthropic — AI writing. Only when you use AI writing in the composer, we send Anthropic's Claude API what it needs to write that field: the field's text, your instruction, the post's other text fields, your workspace's saved writing style, a few of the workspace's recently published posts as style examples, and for alt text or a new caption, one image or video frame from the post. When a comment-to-DM rule uses AI-written messages, we send it the rule's brief, the commenter's username, the matched keyword and the comment text, to write that one message. Processed in the United States. Under Anthropic's commercial terms this data isn't used to train its models, and it's deleted within 30 days unless it must be kept to enforce Anthropic's usage policy or by law.

We do not sell your data to any third party. Data is shared with the providers listed above only to the extent necessary to operate the service.

Data Security and Protection

We use encryption and industry-standard safeguards to protect your data and we have security procedures in place to protect the confidentiality of your data.

While no system is 100% secure, we continuously improve our protections, conduct regular security reviews, and respond to issues promptly to ensure your information remains safe.

Your Rights and Data Deletion

You have several rights regarding your personal data, including the right to request deletion of your information.

How to Request Data Deletion

To delete your account and associated data, you can:

  • In the app: Go to Settings → Account → Delete Account. This permanently removes your account, uploaded content, and associated data
  • By email: Contact us at [email protected] with the subject line “Data Deletion Request”
  • We will process your request within 30 days
  • For platform-specific data deletion, you may also need to revoke access through each social media platform's settings

What Data Can Be Deleted

  • Your account information
  • Video content you uploaded
  • Connections to your social media accounts and content sources
  • Usage analytics and activity logs associated with your account

Data We Cannot Delete

  • Aggregated, anonymized usage statistics that don't identify you personally
  • Transaction records required for tax and accounting purposes
  • Data required to comply with legal obligations or resolve disputes
  • Content already published to social media platforms (you must delete this directly on each platform)

Note: Deleting your ShortSync account will remove your access to the service and delete most associated data. However, content already posted to social media platforms will remain on those platforms until you delete it directly.

Payment Information

If you choose to use our paid services, payment processing is handled by Stripe. We do not store your credit card information on our servers. Please review Stripe's privacy policy for information on how they handle your payment data.

Children's Privacy

ShortSync is not directed at children under the age of 13 (or the applicable age of digital consent in your jurisdiction). We do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has provided us with personal data, please contact us at [email protected] and we will promptly delete it.

International Data Transfers

Night Tech Oy is based in Finland (EU). Your data is primarily stored and processed within the European Union:

  • Database and authentication: Supabase, hosted in the EU (Frankfurt, Germany)
  • Application servers: Hetzner, hosted in the EU (Helsinki, Finland)
  • Analytics: PostHog, hosted in the EU
  • File storage: AWS S3, EU region

Some third-party providers (Stripe, Anthropic for AI writing, social media platform APIs) may process data in the United States or other countries. Where data is transferred outside the EU/EEA, we ensure appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) or the provider's participation in recognized data protection frameworks.

Cookies and Tracking Technologies

Our web application uses the following cookies and similar technologies:

  • Essential cookies: Authentication session cookies required for the service to function. These cannot be disabled.
  • Analytics cookies: PostHog analytics cookies that help us understand how the service is used. These are only set when you accept analytics tracking. You can opt out at any time via your account settings.

Our mobile app does not use cookies. Analytics events in the mobile app are tied to your authenticated account and can be disabled in your account settings.

Contact Information

Your continued use of our website will be regarded as acceptance of our practices around privacy and personal information. If you have any questions about how we handle user data and personal information, feel free to contact us at [email protected].

This policy is effective as of September 22, 2026.

Night Tech Oy, Y-tunnus 3617980-7