Privacy notice

Omni-Media Master · Zhenbai.ONE
Updated: September 30, 2026 · Contact: xttsaber@gmail.com

This notice describes the currently implemented desktop development version. A platform entry or successful developer configuration does not mean public publishing approval or a completed live publishing test.

Data and purpose

• Your Zhenbai passport email, authentication session, account status, wallet balance and order records are used for sign-in and existing wallet services. The desktop does not retain your passport password after sign-in. Implemented development tools are currently free; there is no automatic subscription charge.
• Local account labels, original content, selected files, drafts, publishing tasks and result links are stored in your desktop workspace. Browser-assisted account sessions are stored in separate local browser profiles. These sessions are not the same as official API authorization.
• If you actively authorize an official platform connection, we use the approved token and account/channel identifiers to show the connected identity, renew authorization where permitted, publish the content you explicitly confirm, and check its result. YouTube uses upload and read-only scopes; TikTok requests basic identity and direct publishing; Instagram requests professional-account identity and content publishing. Additional platforms require their own authorization.

Storage and recipients

Passport sessions and official platform tokens retained on the desktop are encrypted using the operating system credential protection supported by Electron. Your original content and ordinary workspace records are not an encrypted backup. Protect your computer and any exports you create.

Passport, wallet, Meta authorization exchange and temporary media transfer use our Supabase-backed services. YouTube and TikTok desktop authorization exchanges and API publishing communicate with the respective official platform services. Instagram, Threads and Facebook authorization use a server-side broker; application secrets remain on the server. For selected Meta media publishing, temporary private storage supplies a time-limited media URL so the destination platform can retrieve the file. The destination platform receives the content, metadata and identity needed for the publication you confirm. Visiting the official website also sends ordinary request information to our Cloudflare hosting service.

We do not sell data obtained through these platform APIs, use it for advertising, or use it to train general-purpose AI models. Use of Google data follows the Google API Services User Data Policy, including its Limited Use requirements. This publishing workflow does not send platform credentials to an AI service.

Retention, disconnect and deletion

Local drafts and labels remain until you remove them or uninstall/remove your workspace. Platform grants can expire or be revoked; renewal cannot guarantee permanent access. You can revoke access through the destination platform's account settings. The software stops using revoked grants and processes supported Meta revocation/deletion notices when online. Offline computers complete local credential cleanup after they reconnect. This cleanup does not delete posts already published on the destination platform or copies you manually exported.

Authorization handoff flows are short-lived (15 minutes). Temporary media is scheduled for cleanup after its 24-hour expiry; an hourly cleanup job retries failures, so expiry is not a guarantee of instantaneous physical deletion. Protected hashed identifiers and cleanup receipts support revocation, deletion tracking and prevention of stale grants being restored. Passport and wallet records belong to the existing Zhenbai account service, and are separate from disconnecting a social account.

For access, correction or deletion requests about this product, contact the address above and identify the relevant passport account and platform. Never email your password, verification code or access token. Platform-owned posts and accounts are managed through that platform's own settings.

Your control

You choose the original work, target account and supported visibility before publishing. Preparation and preview do not authorize a public post. You can decline authorization or disconnect accounts. Browser login checks, multi-factor authentication, platform eligibility, quotas and app review may require your own action. Third-party platforms and hosting services also process data under their own policies.