# Privacy Policy Statuz is made by Intenseloop ("we"). This covers the Statuz CLI, the Mac app, Statuz Cloud (statuz.cloud) and statuz.app. ## In short - Local: your posts, media and tokens stay on your computer. - Cloud: we hold what we need to publish. Payments go through Stripe. - Usage counts: never your content. Anonymous until you sign in to Cloud or join the newsletter. - Release news: if you leave your email when downloading, in `statuz init` or in the Mac app, and for customers (Statuz 1 buyers, anyone who paid us, Statuz Cloud accounts). Unsubscribe from any email. ## 1. On your computer - Posts, drafts, media and settings: `~/.statuz`. - Tokens and app secrets: your OS keychain (Keychain on macOS, libsecret on Linux). - Publishing goes straight to the platforms, not through our servers. - Sign-in happens on each platform's page and returns to `127.0.0.1`. We never see passwords. - No account with us. Your own X or LinkedIn developer app is between you and that platform. ## 2. Statuz Cloud We store: - Your email, name, orgs and teams. - Platform tokens, encrypted. - Posts, threads, direct messages sent through Statuz, media and publishing results. - API keys, as a hash and short prefix only. - Billing records: deposits, spending, credit expiry. Payments are processed by Stripe. We never receive or store card numbers ([stripe.com/privacy ](https://stripe.com/privacy)). We keep payment records as the law requires. If you bought Statuz 1, we check your sign-in email against our Statuz 1 license records when you save a card or add credits, to add your thank-you credit once. Our analytics (UserPath, section 3) learn who you are from Statuz Cloud's server: your Cloud account id, email, name and profile picture when you sign in (on the browser you signed in from too, so its earlier visits to statuz.app and statuz.cloud become yours), whether it was a sign-up or a sign-in and with which provider, each deposit or auto-reload (amount and currency) as a purchase, and each payment that fails: where it failed, Stripe's reason codes and message, the currency and the card's country, never the card itself. Never your posts, accounts or tokens. Some businesses run Statuz Cloud for their own customers. If you connect an account through one of them, we hold it as this section describes, on their behalf, and tell them what happens to the posts and sign-ins they manage. For those accounts we read only the replies and direct messages in conversations that business started through Statuz, never the rest of the account's inbox, and pass each one on to them: who sent it, its text and link. Their privacy policy covers what they do with it. We use Cloud data only to run the service. We don't sell it or use it for advertising. ## 3. Usage counts The CLI, MCP server, daemon, Mac app and Statuz Cloud send usage counts to our analytics (UserPath). Each event carries only: - Commands: name, surface (CLI, MCP, relay, daemon; on Cloud: web, Mac app, API key), local or Cloud, success. - Publishing: platform, local or Cloud, scheduled or not, thread length, media counts, whether it replies to someone, error code on failure. - Messages and searches: platform, local or Cloud, whether a direct message went out, whether a message or reply would reach someone, how many posts a search or reply lookup found. - Scheduling: number of platforms and accounts, media counts. - Accounts: platform connected or removed, a sign-in's health changing. - Posts: a published post taken down, and by whom (moderator, automated, the platform, or deleted on purpose). - Reddit (beta): which of its two endpoints (flairs, subreddit requirements) replied in a shape we didn't expect. - Daemon: OS, service manager (launchd, systemd or none), why it refused to start. - Setup: that `statuz init` ran. - Feedback: that it was sent, its kind, how (signed in or not), the client and agent, the command it is about, and whether a screenshot came along. Never post text, account names or handles, media, links or tokens. Each computer sends them under a random id kept in `~/.statuz`, never with your name or email. When that computer's CLI calls Statuz Cloud, it sends that id along, and Statuz Cloud links the computer's counts to your Cloud account (section 2). Counts from Statuz Cloud itself carry your Cloud account id. There is no opt-out. If you don't want them sent, don't use Statuz. ## 4. This website statuz.app and statuz.cloud count page views and downloads with UserPath, as one site: following a link from one to the other keeps the same anonymous id. When Stripe's payment form on statuz.cloud refuses a card, it also records the reason the form gave. No ad pixels or trackers. Our server sees your IP and browser details to serve the page, not to identify you. ### Newsletter Downloading the Mac app asks, optionally, for your name and email; `statuz init` and the Mac app ask for an email. If you leave your email: - It goes to UserPath (section 3), which sends our release news, with your name (if given) and when you joined. We don't sell or share it. Older versions of the app send it to Statuz Cloud, which keeps it and passes it on to UserPath. - The signup carries this browser's or computer's anonymous UserPath id, so we can see which pages brought you. - Every newsletter email has an unsubscribe link. To have your email, name and that visit history deleted, write to us (below). Leave the email empty, or choose "Just download", and nothing is stored. Customers get release news too, at the email they bought or signed in with: Statuz 1 buyers, anyone who paid through Stripe, and Statuz Cloud account holders. For that, Statuz Cloud shares each account's id, email and name with UserPath. Unsubscribing from any email stops it, and an account keeps working either way. ## 5. The platforms Published posts go to X, Bluesky, Mastodon, LinkedIn or Reddit under their own privacy policies. Reddit is a beta: Statuz connects it through the Statuz browser extension instead of Reddit's own sign-in. The extension reads your reddit.com cookies only when you click Allow in its window, and only to connect the account you chose. Statuz never sees your Reddit password. The session it hands over is kept like every other platform's sign-in (section 1 locally, section 2 on Cloud). ## 6. Keeping and deleting - Local: `statuz accounts remove` deletes an account's tokens. Removing `~/.statuz` deletes the rest. - Cloud: delete posts, media, API keys and accounts anytime. Email us to delete your Cloud account. Billing records are kept as tax law requires. - Newsletter: unsubscribe from any email, or email us to delete your signup and the visits linked to it. - Feedback: what you send with `statuz feedback`, from statuz.cloud or the Mac app (the text, an optional screenshot, the app and page details listed with it) goes to our team and is kept to answer it. Email us to delete it. - Usage counts are kept in aggregate. ## 7. Security Tokens are in the keychain locally and encrypted on Cloud. All traffic uses TLS. If a breach affects you, we'll tell you. ## 8. Your rights Ask for a copy of your data, a correction or deletion. We answer within 30 days. ## 9. Changes We update this page and its date. Significant changes for Cloud users also go out by email. ## 10. Contact [support@statuz.app](mailto:support@statuz.app) [ ](/) Schedule posts from your terminal or your agent. LightDarkAuto© 2026 [Intenseloop, Inc.](https://intenseloop.com) Featured on[Product Hunt](https://www.producthunt.com/products/statuz)[ ](https://x.com/intent/follow?screen_name=stewones)