You did not grant access — that is a legitimate answer. Nothing was connected and nothing was stored. Crux has no account for you, and this page is the only thing that happened.
We could not reach X. The authorisation request timed out before X answered. This is on the connection between us and X, not on your account — nothing was changed at either end.
Your connection to X expired. Scanning paused four hours ago, so Today has not refreshed. Nothing was posted and nothing was lost — your drafts, scores and voice model are exactly where you left them.
One button. No password.
Reconnect @marouane
No account was created.
X did not answer.
Crux runs on your X account, so connecting it is the sign-up. If you have been here before, the same button signs you back in.
X access tokens expire periodically. Reconnecting takes one click and resumes scanning from where it stopped.
If you cancelled to read the permissions properly first, they are on the right — the same list, unchanged. If you decided against it, closing this tab is the whole of it.
Nothing to fix on your side. Try again in a moment; if it keeps failing, X may be having an incident.
Continue with XReconnect with XTry connecting againTry againSigning in and signing up are the same button.
Or go back to the site — no hard feelings, and no follow-up email, because we never got your address.
Last attempt timed out after 10 seconds.
You will land on X’s own authorisation screen, and you can revoke Crux from your X settings at any time. Continuing means you accept the Terms and the Privacy Policy.
Before you click
Exactly what Crux asks X for.
Most products bury this in a policy page. Since the whole product is about telling you things you would rather know, here it is before the button, not after.
What it can do
- Read your published posts
The only source your voice model is built from. Public posts only — the same ones anyone visiting your profile can read.
- Read public posts in your niche
This is what momentum and crowding are measured from, and the only thing that costs money — X bills per read, passed through at cost.
- Post — one approval at a time
X grants this as a single permission, so Crux holds it. It is used only when you approve a specific post in the queue. There is no autopilot to switch on.
What it never touches
- Direct messages, in either direction
Crux does not request the scope, so it cannot read them even by mistake.
- Your X password
The connection is OAuth. Your password is never sent to us and never stored.
- Following, liking or reposting on your behalf
No engagement automation exists in the product, so the permissions behind it are never requested.
- Training a shared model
Your posts train your voice model and nobody else’s. Your drafts train nothing at all.