Privacy

Who this is for

SocialEddie is a hosted tool that schedules and publishes posts to X and Threads. People sign in with an X account and work inside workspaces. A workspace has one owner and may have other members with a role (admin, member or viewer); one person may belong to several workspaces. Whether new people can create a workspace is a setting of this deployment; when it is closed, only invited people can join.

What it stores, and about whom

• Your sign-in identity. The account id and handle of each platform account you signed in with, so a later sign-in resolves to you. The handle is display only.
• Which version of these terms you accepted, and when.
• Platform credentials. The OAuth grant issued when a workspace connects an X or Threads account, encrypted at rest with a key supplied only through the deployment's environment. It is used to publish that workspace's posts, to refresh itself, and — on X, for the reads listed below — for nothing else.
• Posts written in a workspace — their text, scheduled times, the accounts they target, and the platform post ids returned once published.
• Media attached to posts, stored under a content hash on the deployment's object store. Location metadata (EXIF) is stripped from every image before it is stored.
• Session and access tokens for the dashboard and for the MCP tooling, stored as hashes rather than as the values themselves.
• An activity log per workspace: who invited, joined, left, changed a role, changed a setting, and what the deployment's operator did to the workspace. It holds ids, roles and names — never a credential or a token.
• Spend records: the cost this deployment incurred with X for each publish and each read, attributed to the workspace that caused it, so plans can be enforced.
• Billing records for a workspace on a paid plan: the plan, the period, the card's brand and last four digits, and invoices. Payments on this deployment are emulated: no card is charged and no card number is ever stored.
• Notification settings a workspace chooses: a webhook URL, stored encrypted, and optionally an email address.

What it sends, and where

To X and to Threads, to publish what a workspace scheduled — the post text (on X, also an Article’s title, body and banner), any attached media, and the credential that authorises it — and, on X, to perform the reads a workspace's members ask for through the MCP tooling: profiles, posts by id (an X Article included, through its post), an account's own posts, conversations, lists, communities, recent search, trends, and the connected account's own mentions, post metrics, bookmarks and bookmark folders. It never reads a home timeline, likes, blocks, mutes or direct messages, and it stores no analytics about anyone.

Attached images are served from this deployment's media host so Threads can fetch them, which makes those files publicly reachable by URL for as long as a post references them.

When a publish fails, the workspace's own notification channel is told — its webhook, or its email address if it set one. Invitation links are emailed only if an address was given and the deployment has an email sender configured.

When a member asks for an X Article as Markdown, SocialEddie's separate reader service — which holds no credentials — sends the post's link (https://x.com/i/status/<id>, nothing else) to xtomd.com, an independent free service that fetches the post through FxTwitter, not through X's API. xtomd.com records the link, the request's approximate location and this service's name. Nothing it returns is kept; the workspace records only the time of the read, and for 15 minutes after it, posts queued from Claude are held for a person to review, then publish on their own schedule. Nothing else is sent to any other third party.

It performs no likes, follows, reposts or unprompted replies on any platform. A reply to somebody else's post is published automatically only where that person addressed the connected account; otherwise it is held as a draft for a person to post by hand.

Who can see what

Members of a workspace see that workspace's posts, media, connections, members and activity — never another workspace's. The deployment's operator can see each workspace's name, plan, billing state, member and account counts and spend, can suspend a workspace and can change its plan; the operator cannot read a workspace's credentials or its posts from the console, and every such action is written to that workspace's activity log.

How long it keeps things

Posts and their history are kept until a member deletes them or the workspace is deleted. Stored media is removed once no post references it. Disconnecting a platform destroys the stored credential for it immediately. Activity log rows are removed after the retention period set in this deployment's configuration.

Deleting your data

A workspace owner can delete the workspace from its Settings screen by typing its name: every row of the workspace goes at once, and its stored media files are removed unless another workspace holds the same file. Any signed-in person can delete their account from the Account screen: their identities, memberships, sessions and tokens are removed, and a later sign-in with the same account creates a new, empty one. Account deletion is refused while the person owns a workspace, until they transfer or delete it.

Contact

Enquiries go to whoever operates this deployment at https://socialeddie.com.