Twitch
Coming soonPairing Twitch is a verification checkpoint, not a data stream. Completing the OAuth round-trip proves you hold a live Twitch account; nothing about your channel, follows, or subscriptions is read.
Coming soon
Pairing Twitch isn't live yet. This page documents what ~Alter will read once it is, published ahead of launch so you can see exactly what it will and won't touch before you ever pair it. The pairing button stays disabled until this connector goes live.
What pairing does not authorise
Pairing this connector is a read commitment, not delegation. Specifically, ~Alter cannot use this pairing to:
- •Post, stream, or chat on your behalf on Twitch.
- •Read your subscriptions, follows, or the channels you watch.
- •Read chat messages, whispers, or moderation actions in any channel.
- •Change your channel settings, stream key, or account settings.
- •Surface your Twitch identity to other ~alter members, agents, or organisations without a separate consent row scoped to that recipient.
The OAuth or attestation scope we request is the minimum required to recognise the pattern described in What we read. Anything beyond that is structurally refused at the connector boundary, not promised by trust. How pairing works.
What we read
- Your Twitch user id and login name, as the OAuth provider returns them.
- Your Twitch display name.
What we don't read
~Alter explicitly refuses these fields even when the OAuth scope or API permits them. Every refusal is enforced at the connector boundary, not by trust.
- Channel, stream, or VOD data.
- Follows, subscriptions, or the channels you watch.
- Chat messages or moderation history.
- Email address tied to the Twitch account.
- Any signal beyond the account existing and belonging to you.
Where it lives
The verified account identifier and display name are stored in ~alter's pairing ledger keyed to your ~handle, encrypted at rest, refreshed on each successful re-auth. No channel or activity data is collected, so none can appear in matching, recognition, or any external query.
How to revoke
Nothing to revoke yet, since Twitch cannot be paired. This is the revocation you will get when it goes live, published now so you can see the way out before you ever choose the way in. Revocation will be immediate. You will ask the AI client you paired through to revoke this connector, or revoke it from your consent surface over the same connection. Either path revokes the provider token, stops all further reads, and purges the derived signals this connector fed into your identity vector. An audit row records the revocation.
One thing is kept on purpose. The connector retains a record that this account was paired and when it was disconnected, so the same account cannot be unpaired and re-paired in quick succession to churn your identity vector. That cooldown record holds the raw profile snapshot until the window passes. It is never read into a new signal while disconnected, and it is not shared with anyone.
Prefer the command line? The CLI is the optional deeper path and revokes the same connector:
CLI (optional)
alter unpair twitchPairing this connector does not enrol you in any matching, ranking, or matching surface. Every downstream use requires its own consent row. See the consent model.