Skip to content
PostPulse

Privacy policy

Last updated October 11, 2026

PostPulse is run by j3rah_, an individual developer in Colorado (“we”). This page explains what PostPulse collects when you use it, why, who else handles it, and what you can do about it. Questions go to support@postpulse.app.

What we collect

  • Your X account. When you connect, X gives us your account ID, username, display name, profile picture and follower count.
  • Your posts. For the analysis, we read your latest 20 original posts and their public numbers (likes, replies, reposts, quotes, bookmarks and views) from X, and keep your latest analysis and the posts it was written from.
  • What you write in PostPulse. Drafts, articles you paste into Pull quotes and replies you draft are sent to the services that score and rewrite them (listed below). We don't save them to our database, except posts you schedule and your score history (the last 100 drafts you scored, with their scores), which you can clear from the History panel.
  • Posts you publish through PostPulse. We keep the text, its score at the moment it went out and its numbers from X (views, likes, replies, reposts, quotes, bookmarks and, for 30 days, profile visits, which only you can see), so we can show you how it did. Replies aren't kept.
  • Your X sign-in. Kept in an encrypted cookie in your browser. If you publish or schedule posts through PostPulse, it's kept encrypted on our server instead, so scheduled posts can go out while you're away and your results stay up to date.
  • Usage. Counts of what each account uses (posts, feed loads, tool requests) to apply the plan's limits and show you your usage.
  • Billing. If you subscribe, Stripe handles your payment details. We never see your card. We keep your Stripe customer and subscription IDs and your subscription status.
  • Site analytics. Pages viewed, time on page, the referring site and campaign tags, approximate location (country, region, city), and device, browser and operating system. Visitors are counted with a hash of IP address and browser that changes every day, without cookies, so we can't follow anyone from one day to the next. Once you sign in, your visits are linked to your X account.
  • Security logs. Rejected requests (for example too many requests, or a failed sign-in) are logged so we can spot abuse.

Cookies and browser storage

  • Sign-in cookie. Keeps you signed in. PostPulse doesn't work without it.
  • Google Analytics cookies. Set only if you press Accept on the cookie banner. If you press Deny, or don't answer, Google Analytics sets no cookies.
  • Browser storage. Your drafts and cached results are kept in your browser, not on our server. They're cleared when you disconnect or a different account signs in on the same browser. Your theme and a few other preferences stay.

How we use it

To run PostPulse: score and rewrite your drafts, write your analysis, post and schedule for you, apply the plan's limits, bill you, keep the service secure, and understand which parts get used so we can improve them. We don't sell your information or use it for advertising.

Who else handles it

These services process data for us, each under its own privacy policy:

  • X: your account, your posts, and anything you post or schedule through PostPulse.
  • TypeSafe: scores drafts, posts and pull quotes.
  • OpenAI: writes explanations, rewrites, suggested posts, openers, reply drafts and the analysis.
  • Anthropic: writes suggested posts and reply drafts when you pick Claude.
  • Stripe: payments and billing.
  • Vercel (hosting), Neon (database) and Render (sends scheduled posts on time).
  • Google Analytics: site usage, only if you accept its cookies.

Your data is never used to train AI models. We don't train models on it, and we send it to these services only to get a result back for you.

We may also share information if the law requires it.

How long we keep it

We keep your account's data while you use PostPulse. A scheduled post you delete before it goes out is deleted. When you delete your account, everything above that's tied to it is deleted, except:

  • counters with no content (free runs used, posts sent this month, whether each had a link) and your Stripe IDs and subscription status, so limits and billing still work if you come back;
  • a number that keeps old sign-in cookies from working again;
  • scores saved against a one-way fingerprint of a draft, which hold no text and aren't tied to any account;
  • site analytics, with your X account unlinked from it;
  • what Stripe keeps about past payments, under its own policy.

Your choices

  • Disconnect from PostPulse at any time. You can also remove PostPulse's access in your X account settings.
  • Decline Google Analytics cookies on the cookie banner.
  • Delete your account yourself on Your account (click “Connected as” at the top of any page). It cancels your plan, deletes your data and signs you out everywhere.
  • Email support@postpulse.app to see or correct the data we hold about you. You may have further rights where you live, and we'll honor them.

Children

PostPulse isn't for anyone under 13, and X requires its users to be at least 13.

Changes

If this policy changes, we'll update it here and change the date at the top.