Amazon
Coming soonPairing Amazon is a verification checkpoint, not a data pull. The act of connecting the Amazon account you already use every day is itself what gets recognised. ~Alter reads only your basic Amazon profile: no orders, no wishlists, no Prime Video, no Alexa.
Coming soon
Pairing Amazon 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:
- •Read your order history, wishlists, saved addresses, or payment methods.
- •Read your Prime Video, Amazon Music, Kindle, or Alexa activity.
- •Place orders, cancel orders, or act on your Amazon account in any way.
- •See anything beyond the basic profile fields the profile scope returns.
- •Share your Amazon-derived 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 Amazon customer ID, name, and email address, exactly as Amazon's profile endpoint returns them.
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.
- Order history, purchase history, or wishlists.
- Postal code or any address field. This connector never requests that scope.
- Prime Video, Amazon Music, Kindle library, or Alexa activity.
- Payment methods or any billing information.
Where it lives
Evidence is stored in ~alter's pairing ledger keyed to your ~handle, encrypted at rest. Login with Amazon does not issue a signed identity token the way Google does; identity comes from a direct, server-to-server profile call using the access token Amazon's own token endpoint issued, over TLS, to this connector alone.
How to revoke
Nothing to revoke yet, since Amazon 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 amazonPairing 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.