← All updates

A verified Google or GitHub sign-in now reclaims an unverified account

If someone pre-registered your email — with a password, or through a provider that never verified it — signing in with Google or GitHub on that verified address now gets you in, links the provider, and shuts down everything they set up.

accountssign-insecurity

Signing in with Google or GitHub has always linked the provider to an existing makesPDF account with the same address — but only when that account had a verified email. If someone else had pre-registered your address and never verified it, you were refused and locked out of an account that was not really theirs.

Someone can pre-register your address without ever proving they own it: register it here with a password, or sign in with a Google or GitHub account that lists your address but has not verified it. Either way the account looked like yours from the outside and blocked you from it.

That is now a claim. When Google or GitHub reports your address as verified and the existing makesPDF account on it is unverified, the sign-in goes through and the account becomes yours: the provider is linked, your address is marked verified, and everything the previous holder set up is shut down. Whoever pre-registered the address — with a password or through a provider that had not verified it — loses access: their password or provider sign-in is removed, their sessions are signed out, their API keys are revoked, any MCP client they had authorized is disconnected (its refresh tokens are revoked and its consent removed), any CLI or device login they had approved is expired, any wallet they had linked is unlinked, and automatic top-up is switched off with their saved card removed from it.

If that earlier sign-up was yours — you registered your own address with a password, or through a provider before it had verified the address — the same shutdown applies to you: you will need to reconnect that provider, create new API keys, sign in to the CLI again, re-link any wallet, and buy credits once to save your card before switching automatic top-up back on.

A browser that was already signed in with that account can keep using the site for up to five minutes, until its cached session expires. It cannot use that time to get back in: creating an API key, approving a CLI login, linking a wallet or starting a payment is refused straight away. API keys also stop working immediately, so anything already using one is refused. An MCP client that was already connected may keep working until the access token it holds expires — at most an hour — but it cannot renew itself: its refresh token is revoked and its consent is removed, so it has to be authorized again.

If your account's email was already verified, nothing changes: the provider is linked as before and your password keeps working. And a provider that reports your address as unverified still cannot link to an account that already exists on it — that refusal is what stops someone attaching an address they do not own. The sign-in error now points at the provider's verification rather than telling you to use a verification email from us.