TikTok
Pairing TikTok is a verification checkpoint: you sign in through TikTok's own login screen, and ~alter reads back only your display name and avatar. That is the entire scope this connector requests, TikTok's most basic one, and it is the only scope this connector will ever ask for.
What pairing does not authorise
Pairing this connector is a read commitment, not delegation. Specifically, ~Alter cannot use this pairing to:
- •Post, edit, or delete any video on your behalf.
- •Follow, like, comment, or message anyone through your account.
- •Read your video list, watch history, or analytics.
- •Read direct messages or any private account data.
- •Share your TikTok identity with any third party 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 TikTok account id (open_id / union_id).
- Your display name.
- Your avatar image URL.
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.
- Any scope beyond user.info.basic, videos, follower graph, likes, comments, analytics, or messages.
- Anything TikTok's basic scope does not itself return.
Where it lives
The account id, display name, and avatar URL sit in ~alter's pairing ledger keyed to your ~handle. The OAuth token is used once to fetch that profile and is never stored.
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 tiktokPairing 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.