PostChorus
Privacy Policy
Last updated September 19, 2026
The short version
PostChorus helps you create, schedule, and publish content to the social networks you choose. PostChorus does not sell personal information, build advertising profiles, or use post contents for advertising. Optional AI assistance is activated only when you explicitly request it.
Information PostChorus handles
PostChorus may handle account identifiers, email addresses, connected-account labels, drafts and attached media, hashtag shortcuts, scheduled posts, preferences, public post history, subscription and entitlement status, X Credit balances and activity, support requests, and technical records needed to operate and secure the service. Social-service credentials are kept in Apple Keychain, Windows Credential Manager, or encrypted Bridge storage as appropriate for the platform and service.
The PostChorus Bridge
The Bridge handles Bluesky, Mastodon, Threads, LinkedIn, Pinterest, Tumblr, Nostr, and X connections and publishing when those services are enabled and provisioned for an account. X publishing may use PostChorus-managed posting credits or another supported configuration. The Bridge may also synchronize hashtag shortcuts, drafts, draft media, scheduled posts, preferences, and public post history when those features are enabled.
Nostr uses remote signing, so PostChorus does not receive the user’s Nostr private key. Social-service credentials stored by the Bridge are encrypted and are not returned to the browser. Traffic is encrypted in transit, and sensitive Bridge records and saved draft media are encrypted at rest. Bridge-synchronized drafts are not currently end-to-end encrypted, which means the running Bridge must be able to process readable draft data to provide synchronization and publishing features.
Account access and authentication
PostChorus may use supported identity providers, including Google, Apple, Microsoft, and Facebook, to authenticate users. These providers may supply basic identifying information, such as an email address, name, or provider-specific account identifier, according to the permissions shown during sign-in. PostChorus uses this information to authenticate the user, associate sign-in methods with the correct PostChorus account, and protect access to account data. PostChorus may also support passkeys and device-specific authentication methods.
Cookies and browser storage
PostChorus uses essential cookies and browser storage to maintain secure access, remember requested settings such as appearance and selected destinations, and provide features such as recently used emoji. PostChorus does not use advertising cookies, cross-site behavioral tracking, or behavioral advertising.
Publishing, scheduling, and media
Post contents, attached images, GIFs, videos, alt text, selected destinations, and scheduled delivery times are processed to perform the publishing actions you request. Content is sent only to the social networks you select. Some connected services may need to retrieve media from a temporary, unguessable Bridge URL. Temporary publishing files expire automatically. Draft media is retained only to support saved drafts and is subject to applicable storage and retention limits.
Optional AI assistance
PostChorus offers optional writing and alt-text assistance. Nothing is sent to an external AI service merely because you type in the composer, attach media, save a draft, or publish a post.
When you explicitly request Gemini writing assistance, PostChorus sends your instruction and the current composer text to Google’s Gemini API. When you explicitly request Gemini-assisted alt text through a supported PostChorus interface, PostChorus may send the selected image and limited composer context needed to generate a relevant description. On supported Apple devices, some alt-text assistance may instead be performed on the device without sending the image to the PostChorus Bridge or Gemini.
AI-generated suggestions are never published automatically. You decide whether to use, edit, or discard each suggestion before completing the normal PostChorus publishing process.
Data handling by Gemini depends on the service tier used by PostChorus. Google states that content submitted through unpaid Gemini API services may be used to provide, improve, and develop Google products and may be reviewed by humans after privacy protections are applied. Google states that prompts and responses submitted through paid Gemini API services are not used to improve its products, subject to its applicable terms and abuse-monitoring practices. Do not submit sensitive, confidential, legally protected, or otherwise private information through an AI-assistance feature. Additional information is available in the Gemini API Additional Terms and Gemini API pricing and data-use documentation.
URL shortening
If PostChorus Short Links is enabled, PostChorus processes the original destination URL, generated short code, creation time, activation status, and basic visit information needed to operate and manage the short link. If you connect a Custom YOURLS service, PostChorus encrypts the supplied API credential and transmits eligible URLs to that service when you choose to use it. Your use of a Custom YOURLS installation remains subject to the policies of its operator and hosting provider.
X Credits and billing records
X charges PostChorus for API activity, so X publishing may require prepaid X Credits sold separately. PostChorus retains credit balances, estimates, reservations, completed deductions, purchase references, and limited post information needed to display credit activity and prevent overspending. PostChorus does not store complete payment-card details.
Support requests
When you contact PostChorus support, PostChorus processes your email address, ticket category, subject, message, platform and app-version information, replies, ticket status, and any screenshot or PDF you choose to attach. Support records are available to authorized staff according to assigned administrative roles. Do not include social passwords, app tokens, recovery keys, Bridge encryption keys, or complete payment-card numbers in a support request.
Security and abuse prevention
Cloudflare may process IP addresses, browser and device information, request metadata, routing information, and security signals to deliver and protect PostChorus. The public support form uses Cloudflare Turnstile to help distinguish legitimate requests from automated abuse. Turnstile may process technical information according to Cloudflare’s applicable privacy terms.
Transactional email
PostChorus uses an email-delivery provider, which may include ZeptoMail or a successor provider, to send service-related messages such as account notices, security notifications, purchase or subscription messages, support-ticket confirmations and replies, publishing-failure alerts, and other transactional communications. The provider receives the recipient address, message contents, and delivery metadata needed to send and troubleshoot those emails. Marketing messages, if offered, are controlled separately from essential transactional communications.
Other third-party services
Publishing sends information to the social networks you select under their respective terms and privacy policies. Optional Gemini requests send the material described above to Google. GIF searches send search terms to GIPHY. Cloudflare may process routing and security information. Stripe and Apple may process subscription, add-on, or X Credit purchases made through their respective payment systems. PostChorus retains transaction identifiers, entitlements, credit balances, and purchase or subscription status rather than complete payment-card details.
Retention and deletion
Public post history is retained for ten days by default unless another available retention period is selected. Users can delete drafts, remove managed short links, disconnect connected accounts, and submit an account-data deletion request through Settings. Support, security, billing, audit, fraud-prevention, and transaction records may be retained for a reasonable period or as required by law. Some limited records may remain after account deletion when needed for legal compliance, security, fraud prevention, dispute resolution, or financial recordkeeping.
Administrators
Authorized administrators may view service health, account identifiers, connection status, entitlement and usage information, support requests, billing status, and sanitized errors according to their assigned roles. The administrator dashboard does not display social-service credentials, recovery keys, or draft contents. Administrative actions are logged.
Changes to this policy
This policy may be updated as PostChorus adds features, integrations, or service providers. The date above will be revised when changes are published. Material changes will be communicated when required by applicable law.
Contact
Privacy and support requests can be submitted through the PostChorus support page. PostChorus generally targets an initial support response within 48 business hours, Monday through Friday, 9 AM–5 PM Eastern, excluding U.S. federal holidays.