Raoul Duke
Founder of HelperX and long-time X power user.
Focused on practical account warm-up, safe reply automation, and multi-account isolation. Public writing covers shadow bans, cadence, and what actually breaks when you automate carelessly.
We build tools for people
who actually use X
HelperX is a focused product: an account warm-up and scheduling assistant for X, built by an operator who got tired of doing the same five things by hand every morning.
Founder
Who builds HelperX
Built by someone who runs X accounts for real — not a faceless “team” byline.
Our stance
What HelperX does not do
Fake engagement
No buying followers, likes, or impressions.
Follow-back loops
No mass-follow / mass-unfollow to game follow-back rates.
Private data scraping
No scraping of private DMs or non-public data.
Coordinated amplification
No multi-account engagement on the same post.
Rate-limit bypass
No bypass of X's anti-abuse systems or rate limits.
Credential resale
No resale of customer tokens, credentials, or proxy traffic.
Infrastructure
Security posture
X auth tokens are the most sensitive thing customers entrust to HelperX. We treat them accordingly.
At-rest encryption
Tokens are AES-256-GCM encrypted before they touch the database. The key is held in environment configuration, never in the database.
Slot isolation
Each X account lives in its own slot with independent settings, proxy, work-time window, and daily caps. No cross-slot bleed by design.
Plan-based caps
Daily action limits are enforced server-side per slot. The UI cannot raise them past the plan ceiling.
Residential proxies
A proxy per slot is required. Datacenter IPs get flagged by X's anti-abuse stack — we recommend residential or mobile.
Encrypted DMs
Welcome DMs use X's encrypted-DM endpoint (XChat). All outgoing messages are end-to-end encrypted.
Audit logs
Every action a module takes (reply, repost, DM, follow, unfollow) is logged with timestamp, target ID, and module.
On AI-generated content
Several modules support AI-generated replies and posts. That is a feature, not a free pass: the operator is still responsible for the output. HelperX gives you templates, an AI prompt per query/list, and a daily cap — but if the content is wrong, off-brand, or annoying, the responsibility sits with the account owner. We document this expectation in the Acceptable Use Policy.
X Terms of Service
You are responsible for using HelperX in a way that respects X's Terms of Service. HelperX provides controls — daily caps, delays, work-time windows, blacklists — to let you stay well inside reasonable use; how you configure them is up to you.
Contact
Questions about the product, security, or partnerships: see the contact page.
Last updated: 2026-07-19