1. Overview
MultiPost Studio is a Windows desktop application that helps users upload and schedule videos they own or are authorized to publish. This policy explains what information the application and this website process and the choices available to its users.
2. Information processed
The application may process the following information when you choose to connect and use a supported platform:
- Platform account identifiers, display names, profile information, and authorization status.
- OAuth access tokens, refresh tokens, or Page access tokens required to perform authorized actions.
- Videos, thumbnails, captions, privacy choices, scheduling information, and publishing status.
- Local diagnostic information needed to display errors and prevent accidental duplicate uploads.
3. How information is used
Information is used only to connect the accounts you select, validate the destination, upload or publish content according to your instructions, display publishing status, refresh authorization, and troubleshoot failed jobs. MultiPost Studio does not use platform data for advertising, profiling, or sale.
4. Local storage and security
MultiPost Studio never receives or stores platform passwords; authentication takes place in the user's browser. OAuth tokens, refresh tokens, Page tokens, and API client secrets supplied locally are encrypted with Windows Data Protection API for the signed-in Windows account. Publishing metadata and job history are stored locally in configuration and SQLite files and are not separately encrypted by MultiPost Studio; they rely on Windows account and filesystem protections.
5. Sharing and third-party platforms
The application has no developer-operated analytics, advertising, telemetry, crash-reporting, or content-storage backend. Network requests are sent directly from the user's PC to the selected platform's authorization, API, and platform-provided upload endpoints. Those services process information under their own privacy policies and terms. We do not sell or rent personal information.
6. Retention and deletion
Disconnecting an account removes its locally stored authorization token and, where supported, first attempts to revoke that token with the platform. Disconnecting does not delete job history or content already uploaded or published. Removing only the program files also does not remove the application's Local App Data folder. Follow the Data Deletion Instructions to remove all locally stored configuration, tokens, logs, and job history. Published content must be managed on the destination platform.
7. User choices
Users decide which accounts to connect, which platforms receive a video, whether a TikTok item is uploaded as a draft or submitted through an available direct-post flow, and when a scheduled job should run. A user can cancel queued jobs or disconnect an account from the application.
8. Children's privacy
MultiPost Studio is not directed to children. Users must satisfy the minimum age and account requirements of every connected platform.
9. TikTok data and permissions
user.info.basicidentifies and displays the authorized creator account.video.uploadtransfers a user-selected video to the creator's TikTok Inbox as a draft.video.publishis used only when Direct Post is enabled and the client, account, and requested settings are eligible.
MultiPost Studio does not request TikTok contacts, follower lists, direct messages, or access to a creator's existing video library.
10. Website privacy
This static website does not use first-party analytics, advertising trackers, contact forms, or application cookies. GitHub Pages may process standard access logs under GitHub's own privacy terms.
11. Changes to this policy
This policy may be updated when the application's features or platform requirements change. The effective date at the top of this page identifies the current version.
12. Contact
Questions or deletion requests can be submitted through the MultiPost Studio support page.