1. At a glance
Xholic runs X accounts for founders, teams and agencies, so it is built to never need more access than the job takes. In short:
- You sign in with X's official sign-in. Xholic never sees or stores your X password.
- Your X access tokens are encrypted before they are stored.
- Posts and DMs go through the official X API, only when you publish, schedule, approve or set up an automation.
- Roles for teammates are checked on our servers on every request, including from the Chrome extension.
- Every change made through the API, MCP server or CLI is logged, and can be undone where X allows.
- Payments are handled by Dodo Payments. We never receive your full card number.
- We don't use your content to train AI models.
We don't hold security certifications such as SOC 2 or ISO 27001 today. If your company needs a security questionnaire answered, email sales@xholic.ai.
2. Signing in with X
Xholic has no passwords of its own. You sign in through X's official OAuth 2.0 sign-in on x.com, and X asks you to approve what Xholic may do. Xholic never sees or stores your X password, and connecting another X account to your plan works the same way.
Xholic asks X for these permissions, each for a feature you can use:
- Read posts and your profile (
tweet.read,users.read,users.email) for analytics, your voice and your account email; - Post and upload media (
tweet.write,media.write) for posts you publish or schedule; - Read bookmarks (
bookmark.read) so Xholic can learn from what you save; - Direct messages (
dm.read,dm.write) for DM campaigns and replies you send; - Stay signed in (
offline.access) so scheduled posts go out while you're away.
You can revoke Xholic's access at any time in X under Settings and privacy, Security and account access, Apps and sessions, Connected apps. Features that need it stop until you sign in again.
3. Actions on your X account
Posts, threads, media uploads and direct messages are sent through the official X API with your authorization. Xholic doesn't like posts or follow accounts for you.
Xholic acts only when you tell it to: a post you publish or schedule, a draft you approve, a DM campaign you launch or an automation you set up. Workers, Signals agents and Ask Xholic prepare drafts for your review; they don't publish on their own. The full list is in our Privacy Policy.
4. Encryption and storage
- In transit: the website, the app and the API are served only over HTTPS (TLS). The app also sends HTTP Strict Transport Security, so browsers refuse plain HTTP. Cloudflare provides our network delivery and protection.
- X tokens at rest: the access and refresh tokens that let Xholic act on your X account are encrypted with XChaCha20-Poly1305 authenticated encryption before they are written to the database. The key is held only on our servers.
- API keys: we store only a SHA-256 hash of each API key, never the key itself. You see the full key once, when you create it.
- Media: images and videos you upload are kept in private storage and opened through links that expire after a short time. Media for scheduled posts is deleted 72 hours after it is published.
- Backups: the production database is backed up every night, and each backup is checked before it is kept.
5. Team access and roles
You can let someone work in your account without sharing a password: share access with another Xholic user by their X handle, or invite a teammate to a team seat by email. You choose their role, and you can change or revoke it at any time. Permissions are checked on our servers for every request, so the same rules apply in the app, the Chrome extension and the API.
| Role | Can | Can't |
|---|---|---|
| Owner | Everything, including billing, connected accounts and sharing | Nothing |
| Full access | Run the account: posts, replies, DMs, Signals, contacts, memory, settings and automations | Billing, connected accounts and sharing |
| Editor | Write, schedule and publish posts, reply, write X Articles and use Ask Xholic (limited) | DMs, Signals, contacts, AI context and voice, settings, automations, post share links, billing and sharing |
More detail is on the Teams page.
6. API, MCP and CLI access
- Scoped credentials: each API key or connected AI app gets only the scopes (Read, Write, Publish) and X accounts you choose. A call outside them is refused.
- OAuth for AI apps: Claude, ChatGPT and other MCP clients connect with OAuth 2.1 and PKCE. You see a consent screen every time, and each refresh token works only once.
- No browser sessions: the API never accepts a Xholic sign-in cookie, so a session copied out of a browser can't drive it.
- Idle connections switch off: a key or app that makes no calls for 90 days stops working. Revoking one takes effect within seconds.
- Activity log and undo: every change made through the API, MCP server or CLI is logged with the connection that made it, the account it acted on and the result, and has an Undo button where X allows it.
Details: Authentication and Activity log and undo in the developer docs.
7. Payments
Checkout, payments, taxes and invoices are handled by Dodo Payments, our merchant of record. You enter card details on Dodo's checkout, and Xholic never receives or stores your full card number.
8. AI providers
AI features send the content they need to OpenAI and Anthropic through their APIs. We don't use your content to train AI models, and we don't opt it into provider training. Providers may keep data for a limited time, typically up to 30 days, for abuse monitoring under their API terms. Every company that processes data for us is listed on the subprocessors page.
9. Data retention and deletion
To delete your account and its data, email hello@xholic.ai from the address on your account. Ending a subscription doesn't delete anything by itself. Copies may remain in backups for a limited time until they are overwritten. Retention periods for each kind of data are in our Privacy Policy, and business customers can ask for our Data Processing Addendum.
10. Reporting a security issue
If you think you've found a security issue in Xholic, email support@xholic.ai with the steps to reproduce it. Please give us a reasonable time to fix it before sharing it publicly, and don't access or change other people's data while testing. We'll confirm we got your report and keep you updated.