Privacy Policy
This page describes categories of information processed in supported desktop publishing workflows.
1. Data categories
Depending on the features you use, TMD AUTO POST may process: (a) connected account identifiers and profile or Page names made available through platform permissions; (b) authorization tokens needed to perform authorized actions; (c) videos, local file references, cover images, captions and schedules; (d) upload identifiers, publishing outcomes, error details and diagnostic logs; and (e) support messages or licensing information you choose to provide. This public website itself does not ask you to upload videos or sign in.
2. How information is used
Information is used to connect accounts on request, prepare or schedule publications, transfer content to your selected platform, show results, troubleshoot errors, and respond to support or deletion requests. Publishing access is limited by the permissions you authorize and the platform’s API.
3. Connected services
When you request publishing, relevant videos, metadata and account authorization data are transmitted to the selected service (for example, YouTube, Facebook Page or TikTok) under that service’s own rules. Optional device notifications may use a user-configured notification provider. Cloudflare may process ordinary website access information to serve this website.
4. Storage and retention
The desktop product may store local application preferences, project metadata, video paths, publishing records and authorization information needed for its functions. Connected platform data may remain on those platforms under their retention rules. The specific retention period depends on the feature and the applicable settings; contact support to request review and deletion of data controlled by the TMD product operator. Removing local files does not automatically delete third-party posts.
5. Security and limitations
We aim to protect account authorization information and limit access to its intended workflows. No system can guarantee absolute security. Do not share access tokens, API secrets or login screenshots with third parties. Revoke a compromised connection promptly on the relevant platform.
6. Your choices and rights
You can choose not to connect an account, revoke app access in the corresponding platform settings, stop scheduled jobs using the product controls available to you, and request access, correction or deletion of operator-controlled personal data where applicable. To remove an already-published post, use the corresponding platform’s controls.
7. Children and international use
Use is intended for people who meet the age, location and eligibility requirements of their respective platforms. Data may be processed by the connected third-party platforms under their international terms and privacy rules.
8. Requests and contact
For privacy questions or deletion requests, follow the Data Deletion Guide or email minhduy.ts92@gmail.com. The operator will review the request and explain which data can be removed locally or from operator-controlled systems, and which must be handled by a third-party platform.
9. YouTube API Services & Google user data
API disclosure. TMD AUTO POST uses YouTube API Services to connect a channel that you choose, identify that channel, upload video files you select, set upload titles/descriptions and a cover image where supported, and report the result. Use of these features is subject to your Google authorization and YouTube's available permissions. The current macOS beta uploads to YouTube with Private visibility; we do not claim approved automated public YouTube posting.
Data requested. Google OAuth may grant the youtube.upload and youtube.readonly permissions. These are used to upload a selected video and identify or verify the authorized channel. The desktop app may process your Google channel identifier/name, upload results and video IDs, user-entered titles/descriptions, thumbnail selections, scheduled job records and OAuth access/refresh tokens. TMD does not ask for or receive your Google account password.
Purpose, storage and sharing. On the inspected beta build, OAuth credentials are stored in your device's operating-system keyring, while channel associations and publishing records are kept in the app's local database. Video files and related metadata are transmitted to YouTube when you request or explicitly authorize an upload or a schedule. YouTube/Google handle data they receive under their own terms and policies. This informational website does not offer a Google login or upload form. See Google Privacy Policy.
Control and withdrawal of access. You can stop the YouTube upload queue and disconnect an authorized channel in the desktop app. You can also revoke the app's Google access at Google Account – Third-party access. Removing a credential locally and revoking Google's authorization are distinct steps. To request deletion of account-related records or other data controlled by TMD, follow the YouTube deletion and revocation instructions or email minhduy.ts92@gmail.com. Do not send passwords or OAuth tokens.
Retention and deletion. TMD retains local records only for the workflows and troubleshooting described above. Records retrieved through YouTube API Services are subject to YouTube's storage, refresh and deletion requirements. Contact TMD to request review and deletion of stored account-related records. Disconnecting does not delete videos already hosted by YouTube; delete those from YouTube Studio if desired. Existing local scheduled history may require a separate deletion request.
Third-party policies. Your use of connected YouTube features is also subject to the YouTube Terms of Service and the Google Privacy Policy. See also TMD's YouTube-related terms.