Privacy Policy

Public Thread Exporter v0 is designed for transient, one-at-a-time public thread exports. Submitted URLs are used to generate the requested export and generated exports are not persistently stored in v0.

Optional Google sign-in, when configured, uses the basic account information needed for sign-in and account management, such as your Google account identifier, email address, and basic profile information returned by Google. We do not request Gmail, Drive, Contacts, or unrelated Google service access for this feature.

If you sign in, a secure session cookie is used to keep you signed in and protect the account session. You can sign out at any time and request account deletion by emailing support@xthreadexport.co from the email associated with your account.

To request deletion of account data created through optional Google sign-in, contact us at support@xthreadexport.co from the email associated with your account. We will delete or de-identify account data we are not required to keep for security, abuse prevention, or legal reasons.

Image exports are generated from the public/exportable content shown to you and the formatting options you choose. Unless a saved-history feature is clearly offered and selected, generated images are prepared for the current request and are not kept as permanent account history.

We use a Plausible Analytics deployment served from plausible.shipsolo.io to understand aggregate use of our pages and product. We configure analytics to send only the page hostname and path without query strings or fragments, an origin-only referrer when available, controlled event names, and coarse allow-listed product properties such as export format, result status, stable error code, and duration bucket. Analytics requests necessarily expose your IP address and browser user-agent to the analytics service, which may use them to produce aggregate device and location statistics.

We do not send submitted X/Twitter URLs, handles, post IDs, post text, generated export content or images, Google account data, email addresses, Stripe customer or subscription identifiers, checkout session identifiers, or payment details to analytics. We do not use analytics for advertising or cross-site profiling. We retain analytics records only for as long as needed to operate and improve the Service, subject to the retention controls of the configured analytics deployment.

Temporary operational storage, if introduced by backend implementation, should use short TTLs and private no-store cache controls.

Important boundaries

Public content only. No private, protected, deleted, restricted, login-gated, or bypassed content. Attribution and source URLs should remain attached to exports.