Replyburst helps you grow your audience and market your products on X (Twitter) and Threads, by drafting and posting replies and posts in your voice. This policy explains what the Replyburst web app, browser extension and Threads integration collect and how it's used.
What we collect
- Account info: your email (and name/photo if you sign in with Google) to create and secure your account.
- Your settings: niche, tone, target accounts, schedule, and similar preferences you enter.
- X activity you generate through Replyburst: the posts/replies drafted and the ones you choose to publish, plus which posts you reviewed or skipped — so we can show your history and avoid duplicates.
- The extension reads your own logged-in x.com timeline to find relevant posts and to post on your behalf, in your own browser session. It does this only for the X account you connect.
Threads (Meta)
If you connect a Threads account, we additionally process:
- Your Threads profile: your Threads user ID and username, so we can show which account is connected and publish as you.
- Your Threads access token: issued by Meta when you authorize Replyburst. It is encrypted at rest (AES-256-GCM) and used only to act on your behalf.
- Public Threads posts matching your campaign keywords: we store the public text, author username, permalink and post ID of posts our AI evaluates, plus the relevance score and the reason — so you can see why we replied or passed.
- Replies we publish for you: the text sent, the post replied to, and the time, so you have a full audit trail.
- API usage counters: how many searches and replies we made for your account each day, so we stay within Meta's rate limits.
We use Threads data only to operate the features you switched on for your own account. We do not use it to build profiles of other Threads users, do not sell it, do not share it with third parties beyond the AI provider that drafts your replies, and do not use it for advertising.
Deleting Threads data. You can disconnect at any time from Threads (Settings → Website permissions) or from your Replyburst dashboard. Meta notifies us via our deauthorize and data-deletion callbacks, and we delete the stored token together with the campaigns, discovered posts, generated replies and activity logs derived from that Threads account. You can also request deletion at the contact address below.
What we do NOT do
- We do not sell your data.
- We do not store your X password. The extension uses your existing X login in your own browser.
- We do not store your Threads or Instagram password. Threads access is granted by you through Meta's official OAuth flow and can be revoked by you at any time.
- We do not access accounts other than the one you connect.
How it's stored
- Data is stored in our database on our server. Sensitive values (e.g. API keys, any tokens) are encrypted at rest.
- AI drafts are generated via our AI provider (OpenAI / Anthropic) using the post text and your settings. We do not use your data to train models.
Browser extension permissions
The extension requests access to x.com so it can read your timeline and post replies you approve, and access to the Replyburst dashboard so it can sync your account. It does not run on any other site.
Your choices
- You can remove a connected account at any time (Dashboard → account → Remove account), which deletes its config, logs, and history.
- You can delete your account by contacting us.
Contact
Questions: costin.gheorghe@devista.io