connections
Accounts you have linked. A linked token lets CoolFace read the repositories you already have access to — nothing more.
Hugging Face
Not connected. CoolFace already reads public models, datasets and apps from the Hub without any token. Linking one only adds the gated and private repositories that you have already been granted.
How a linked token is handled
AES-256-GCM ciphertext, with a per-record nonce
the server, versioned so it can be rotated
inside the request that uses it, never before
never — there is no endpoint that can
never; the value is redacted before any log line
your requests only, never anyone else's
A gate is a decision by the publisher. A linked token lets CoolFace act as you where you already have access; it is never used to see something you have not been granted.
Sign-in providers
Auth.js is wired with the Prisma adapter and database sessions. The browser holds one opaque, HTTP-only cookie; no token is ever placed in localStorage or shipped to the client bundle. Provider credentials are server environment variables only.
API tokens