Privacy
Short version: Postlab keeps what it needs to write, score and publish your posts. Your keys are encrypted, nothing is sold, and nothing goes out on X without your decision.
Last updated November 19, 2026
Who
Postlab is run by Matthieu Audo, in Montréal, Canada. For anything on this page, send a DM to @am56ay on X.
What Postlab keeps
- Your X account: when you sign in with X, X shares your ID, name, username and profile picture. The access X grants for signing in is revoked at once: Postlab keeps no X token, your posts go out through your Treg account. Postlab also keeps your follower counts, to chart your growth.
- Your workspace: what you write in Postlab (drafts, scheduled posts, ideas, saved inspirations), the profile you fill in (product, audience, topics, voice) and the voice profile Postlab builds from your posts.
- Your activity on X, read for you: your posts and their metrics over time, the replies you send through Postlab, the mentions of your account and the accounts you choose to watch.
- Posts from your niche: public posts that did well in your niche, with their author, text and metrics.
- Your keys: your Treg key, and your Claude key if you add one. Postlab takes no other key. Each one is encrypted with AES-256-GCM and bound to your workspace, never sent back to your browser, and only its last 4 characters are shown.
- Usage: the paid calls made for your workspace (X, Treg, Claude, web search) and what they cost, so your spending limits work.
- Claude's answers: the latest answers for your workspace, so a reload does not pay for the same answer twice.
- Your license: the Stripe payment IDs, the amount, the currency, the date and whether it was refunded. Never your card: Stripe handles it.
- Sign-in sessions: a random token in a cookie. Postlab stores only its SHA-256 hash, for 30 days.
Why
To run Postlab for you: show what works in your niche, write and score drafts, publish what you scheduled, track how your posts do and keep spending within your limits. To sell and refund licenses. Nothing else: no advertising, no profiling, no selling of data.
Who else sees it
Each of these services does one job:
- Cloudflare: hosts Postlab and its database.
- X: where your posts go. Signing in with X goes through Postlab's X app.
- Treg: relays your posts and reads to X, and runs Trending and web search, on your own Treg account and balance. Each call carries what it needs: the post to publish, the account or the search to read. Treg's privacy policy covers your Treg account.
- Anthropic: Claude writes and rewrites drafts. It receives the text you ask about, with the context it needs: your profile, your voice, some of your posts and posts from your niche. Under Anthropic's commercial terms, this data is not used to train its models.
- Stripe: payments. Stripe collects your card details and email at checkout, under its own privacy policy.
- Ship or Die: Postlab takes part in the Ship or Die hackathon until December 16, 2026. Its script counts visits (see "Visit counts" below), and TrustMRR, connected to Postlab's Stripe account, verifies the revenue the hackathon reports.
What Postlab never does
- Post, reply, like or follow without your decision. Only the posts you scheduled go out on their own, at the time you set. Morning drafts are suggestions.
- Send your keys or X tokens to your browser, or write them to logs.
- Sell, rent or share your data with anyone not listed above.
Cookies and local storage
Only what signing in needs: a session cookie that lasts 30 days, and two short-lived cookies while you sign in with X. No advertising or tracking cookie.
Your browser also keeps a few things in local storage, under keys that start with "postlab": your unsaved draft and your latest paid results (ideas, analyses), so a reload does not pay for them again. They stay in this browser until you clear them.
Visit counts
While the hackathon runs, the public pages of this site (not the application you use once signed in) load a small script from ship-or-die.com that reports every page view: the path (without the query string), the site you came from (its domain only), the utm_source and utm_medium tags, and whether you arrived from a paid ad. It sets no cookie and keeps no identifier in your browser. Like any web request, it reaches their server with your IP address.
If your browser sends Global Privacy Control, the script sends nothing.
How long
As long as your workspace exists. Disconnecting X in Settings revokes the token at X and deletes it. Removing a key in Settings deletes it.
Your keys and your X token are also deleted, the token revoked at X first, when your license is refunded, and after 6 months without opening Postlab unless a post is scheduled. Your drafts and history stay: add your key and connect X again to pick up where you left off.
Settings, Your data, Delete my workspace: your X connection is revoked, then everything in your workspace is deleted at once. Postlab keeps only your X ID, your license and the amounts spent through Postlab, so your spending limits stay right. Payment records are kept as long as tax law requires.
Your rights
See, correct, export or delete your data, or object to how it is used, under the law of Quebec, the GDPR or any law that applies to you: send a DM to @am56ay on X and it is done within 30 days. You can also complain to your data protection authority.
Much of it you can do yourself: edit or delete drafts, remove keys, disconnect X, export your data or delete your whole workspace in Settings.
Changes
When this page changes, the date at the top changes too. A change that matters is announced in Postlab and on X before it takes effect.