Your history. Your control.

Privacy notice for the account owner testing this deployment. This PoC is not open for public customer signup.

What Clearpost processes

X provides your account ID, handle, name, avatar, post count, and OAuth tokens when you connect. Tokens are encrypted on the server. Your X password is never requested or stored.

Archive files are parsed in your browser. Only the selected post IDs, text, and dates are submitted for your preview. Full archive files, DMs, and contacts are not uploaded.

Why the information is stored

The database stores your connection, preview, selected posts, job progress, and operation status so the cleanup can resume. OAuth tokens are never passed into workflow inputs or outputs. X receives API requests to load or delete the posts you select. Vercel and the configured database provider process the hosted application data.

After a cleanup

Post text is removed from Clearpost’s job records after confirmed deletion or an unavailable response. Post IDs and operation counts remain for audit and progress reporting. Cancelling a preview does not itself erase its database records. During the PoC, the deployment owner must remove unused preview records and revoke X app access when testing is complete.

Your choices

You can stop a cleanup and revoke this app’s permissions in X’s connected-app settings. Revocation prevents future authorized API calls; it cannot restore already deleted posts. To remove the private test data, contact the owner of this deployment through your existing communication channel.

Demo mode

The demo uses fictional posts in browser memory. It does not connect to X or persist uploaded archive data on the server.

Before a public launch

A public service will need an identified operator, a support contact, a defined retention policy and deletion process, and privacy terms appropriate to its providers and customers.