Steam
Pairing Steam confirms the Steam account is yours. ~Alter reads your SteamID64, checked by Steam's own sign-in, and nothing beyond it. Steam sign-in needs no API key or app registration, and ~alter holds neither. Sign in through the browser ~alter opens, then come back to your client. It finishes the pairing itself once your sign-in is confirmed.
What pairing does not authorise
Pairing this connector is a read commitment, not delegation. Specifically, ~Alter cannot use this pairing to:
- •Make purchases, gift items, or trade anything on your account.
- •Send Steam messages or read existing chat threads.
- •Add, remove, or interact with friends in any way.
- •Change your profile, display name, or any account setting.
- •Post reviews, screenshots, guides, or comments on your behalf.
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 SteamID64, the account identifier Steam confirms belongs to you when you sign in.
- The time the sign-in was verified.
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.
- Your game library, titles, or genres.
- Playtime, session length, or play cadence of any kind.
- Achievements or completion rate.
- Friend list, chat, or any social-graph data.
- Purchase history, wallet balance, or market activity.
- Display name, avatar, or any other profile field.
- Anything from Steam's Web API. Pairing never calls it.
Where it lives
Evidence is stored in ~alter's pairing ledger keyed to your ~handle, encrypted at rest, tier T2 (ownership confirmed by Steam's own signature check). Steam issues no token to hold onto. The pairing refreshes every 180 days.
How to revoke
Revocation is immediate. 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 steamPairing 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.