# Refresh tokens a copied database can't use, and sign-ins tied to one browser

23 October 2026. A copy of your database holds no refresh token that works. Every token has one job, and Continue with SSO now finishes only in the browser that started it.

## Added

- **Security:** Refresh tokens, which keep people signed in, are stored only as a one-way hash, so a copy of the database holds none that work. Refresh tokens your app's users already held are cancelled once, right after this release is deployed, so each of them signs in to your app one more time. AI agents' access is untouched.
- **Security:** Every token BuildBase signs says what it is for and which part of the platform it opens, and each part accepts only its own kind. A sign-in token from your hosted page is refused by the console, for example, and a magic link's token works for that link and nothing else.
- **Security:** Sign-in gives nothing away about who has an account. Ten wrong passwords lock any address, username or phone number, with the same answer whether or not an account exists. And a sign-in for an unknown address takes as long as a wrong password.

## Improved

- **Authentication:** Behaviour change: Continue with SSO now finishes only in the browser that started it, as social sign-in and Google One Tap already do. The hosted sign-in page already handles this. A sign-in screen of your own must send a PKCE challenge when it starts, and the matching verifier when it redeems the code, as the docs on sessions and tokens show.

Source: https://www.buildbase.app/changelog/hashed-refresh-tokens-typed-tokens-and-pkce
