PostX Privacy Policy

Effective date: July 7, 2026 · Applies to: PostX Chrome Extension

PostX is an AI writing assistant for Facebook, Threads, and X that lives in your Chrome side panel. This page explains, in plain terms, what information PostX accesses, where it goes, and what stays entirely on your device.

01 The short version

No PostX servers

PostX has no backend. There is no PostX server that your data is sent to.

Stored on your device

Your API key, style profile, and content calendar are saved locally in your browser via chrome.storage.local.

Nothing posts without you

PostX only fills in a draft and clicks Post after you click "Confirm publish" yourself.

We don't sell data

PostX does not sell, rent, or transfer your data to advertisers or third parties.

02 What PostX accesses, and why

PostX's single purpose is to help you draft and publish your own social posts. To do this, it accesses the following, and nothing beyond it:

Data	Why PostX accesses it
Your own past posts	Read from your open Facebook or X tab to build a style profile (cadence, emoji use, tone) so drafts sound like you.
Post metrics you paste in	Used only to classify a post as "diffusion-type" or "deepening-type" and suggest what to adjust. This happens in-session and isn't stored beyond your local calendar/history.
Your AI provider API key	Used to authenticate requests to the AI provider you choose, so PostX can generate drafts and calendars.
The active tab's URL/domain	Used only to confirm you're on Facebook, Threads, or X before inserting a confirmed draft into the composer.

PostX does not access your browsing history, other open tabs, private messages, or any site outside Facebook, Threads, and X.

03 Where your data goes

Stored locally, not on a PostX server

Your API key, style profile, and content calendar are saved using chrome.storage.local, which keeps them on your own device. PostX does not operate a server that collects or stores this information.

Sent to your chosen AI provider

When PostX drafts a post or calendar, the relevant text (e.g., your style profile, your topic, or metrics you're reviewing) is sent directly from your browser to the AI provider whose API key you entered. This request goes straight to that provider — it does not pass through any PostX-operated server.

Because you supply and control the API key, your chosen provider's own privacy policy and terms govern how they handle that request. PostX has no visibility into, or control over, how your provider stores or uses this data.

Sent to Facebook, Threads, or X

When you click "Confirm publish," PostX inserts the approved draft into that platform's own post composer and clicks its native Post button. From that point on, the post is subject to the relevant platform's own privacy policy and terms of service.

04 Your control over publishing

PostX never publishes automatically. Every draft — whether from the style engine, the content calendar, or the diagnose/review feature — is shown to you first. Nothing is inserted into a composer or posted until you explicitly click Confirm publish.

05 Data retention and deletion

Your API key, style profile, and calendar remain in local browser storage until you remove them. You can clear PostX's stored data at any time by:

Using any "reset" or "clear data" option inside PostX's settings panel, or
Removing the extension from Chrome, which deletes its local storage, or
Clearing site/extension data for PostX via Chrome's own settings.

06 Third-party services

PostX integrates with services you choose to connect:

Your AI provider — receives the content described in Section 3 in order to generate drafts. Governed by that provider's policies.
Facebook, Threads, X — PostX reads your own posts (with your active session) and, upon your confirmation, submits posts through the platform's normal interface. Governed by each platform's own policies. PostX is an independent, third-party tool and is not affiliated with or endorsed by Meta, Instagram, or X.

07 Children's privacy

PostX is not directed at children and is not intended for use by anyone under the minimum age required to hold an account on Facebook, Threads, or X in their region.

08 Changes to this policy

If PostX's data practices change, this page will be updated and the effective date above will reflect the most recent revision. Material changes will be noted in the extension's Chrome Web Store listing.

09 Contact

Questions about this policy or how PostX handles your data can be sent to ysqiao30@gmail.com.