Sign in with GitHub, and a privacy policy update

There is now a Continue with GitHub button above the sign-in and sign-up forms. If your GitHub account uses the same address as your BounceShift account, it connects to the account you already have — it does not create a second one, and your password keeps working. If you have two-factor authentication switched on, we deliberately do not let a social sign-in skip it; you will be asked to sign in with your password instead.

A change to our privacy policy

We also updated our privacy policy, and this part is worth reading rather than skimming.

Once your own account address has been confirmed as real — because you clicked our verification email, or because you signed in with a provider that had already confirmed it — we now record it in our reputation database as evidence that the mailbox exists.

That database is what makes validation accurate. It is shared across all BounceShift customers, and it stores addresses only as one-way SHA-256 hashes, never as the address itself. Nothing about that storage changed. What changed is where a record can come from: previously only from email service provider webhooks, and now also from a confirmed account address.

What this means in practice

• Your address is stored as a hash, not as text. The same as every other record in that database.
• It is shared across customers. If another customer validates your address, the hash may be matched. That is how the database improves accuracy for everyone.
• You can have it removed. Email [email protected] and we delete it. We also delete it automatically if you close your account or change your address.
• It does not currently affect any validation result. These records accumulate; they do not yet influence the verdict the engine returns.

We are telling you because our privacy policy commits us to announcing material changes, and a new source of data about you is a material change. If you would rather your address was not included, email us and it will be gone.