How we use X (Twitter) data

ShareCount uses X’s public API to verify shares and read follower counts. We never ask your customers for their X password, and we never read DMs, drafts, or anything not visible on a public profile.

What we read

• A handle’s public follower count at the moment of sharing.
• The handle’s recent original tweets (excluding retweets and replies) — only the ones needed to find the tracked share link.
• Public engagement metrics on the verified post: likes, reposts, replies, impressions, bookmarks.

What we never do

• We don’t post on a customer’s behalf.
• We don’t read DMs, drafts, or protected accounts.
• We don’t store the customer’s X access token (we never get one — they post via the X composer themselves).

Why this is safer

Your customers don’t enter X credentials anywhere. They write the post on X itself; we just verify it from public data. That means even if ShareCount were compromised, no X account is at risk.