1. Scope and contact
This notice covers the MultiPost Windows application, this product website, and any product-owned HTTPS services deployed for its connected-platform flow. The identified project operator is TIGO. Questions about this current project can be sent to TIGO at ovtom22@gmail.com. Before public release, the legal seller identity, privacy contact, legal basis, and applicable jurisdiction must be confirmed on this page.
2. Information used by the application
Depending on what the creator chooses to do, MultiPost can use:
- Connected-account display information and identifiers supplied by an authorized platform.
- Access credentials or refresh credentials supplied after the creator authorizes a connected platform.
- Selected local media, file metadata, prepared delivery variants, cover selections, captions, titles, schedules, and publishing results.
- TikTok-specific review values such as the currently available audience choices, interaction settings, disclosures, and recorded posting consent.
- Local app settings, local job history, and diagnostic information supplied voluntarily to support.
- For a future commercial release, a device identifier and limited product-session or entitlement data used to control access to the paid product service.
3. How information is used
MultiPost uses this information to connect the account selected by the creator, prepare and review content, make the platform request the creator approves, track the result of that request, operate local scheduling, maintain product access when a commercial release exists, and respond to support requests.
MultiPost does not use connected-account data to sell advertising, build an audience profile for advertising, or sell personal data.
4. Local storage and account controls
The desktop application stores working data in the Windows user profile, including drafts, captions, schedules, history, and connection material needed for the creator's authorized workflow. The creator can disconnect an account through the app and can remove all local app data after closing the app by removing the MultiPost application data folder from the Windows user profile. Content already posted to a third-party platform must be managed on that platform.
5. Connected platforms and other processors
When the creator connects or publishes to a platform, the selected content and relevant post settings are sent to that platform under the creator's direction. The current commercial scope is being prepared for TikTok, Meta services such as Facebook Pages, Instagram professional accounts and Threads, and Pinterest. The final public notice will identify every released integration and the applicable provider policies.
If the creator configures an optional AI writing service, the title, caption, prompt text, platform context, and other text needed for that request can be sent to that service. The creator should not submit sensitive information to an optional AI service.
The separate legacy personal developer build can upload eligible media to GitHub Pages or Litterbox as a temporary public-fetch fallback when a destination requires a public URL. That fallback is not part of the planned commercial runtime. Do not use it for confidential media.
6. Commercial service architecture
The commercial source design uses a product-owned HTTPS authorization broker so that provider application secrets are not placed in the distributed Windows application. The broker is intended to receive an authorization response from a connected platform and deliver a short-lived result to the local app. It is not a social-posting dashboard or a public account database.
Some platforms can require a video to be available from a URL they can fetch. For those cases, the commercial design uses a controlled temporary media relay. It is intended to hold an expiring copy only for the necessary platform transfer window, rather than use a permanent public media library. A product-session issuer is intended to authorize that relay for an eligible product installation.
The services are not deployed in this local source stage. Before go-live, this notice must name the actual hosting providers, storage location, log retention period, media expiry and deletion behavior, security contact, and the process for any cross-border transfer.
7. Sharing and retention
In the planned commercial runtime, information is shared only with the connected platform, an optional AI service selected by the creator, or the product service needed to perform the requested action. The separate legacy personal build can also share eligible media with GitHub Pages or Litterbox in the temporary public-fetch fallback described above. Retention is currently governed by the creator's local application data until it is disconnected or deleted. No commercial server-side retention schedule is asserted until production infrastructure is configured and reviewed.
8. Website technologies
The current static site source contains no analytics script, advertising script, payment form, visitor account registration, or embedded tracking widget. If these are added for a public release, this notice and any required consent mechanism must be updated before they are used.
9. Security
MultiPost is designed to limit credential exposure by using official platform authorization flows and by keeping provider application secrets outside the distributed commercial desktop build. No storage or transmission method can be guaranteed completely secure. Creators should keep their Windows account and connected-platform account protected.
10. Children, rights, and changes
MultiPost is not directed to children. Before public release, this notice must be completed with the applicable privacy-rights process, deletion-request contact, response periods, and legal basis. The current date at the top of this page will be updated whenever the notice changes.