Signing in with Google, GitHub or Microsoft
Sign in to CertWatchr with a Google, GitHub or Microsoft account, and what we store from it: your e-mail address, nothing else.
Where it is offered, the sign-in and sign-up pages show Continue with Google, Continue with GitHub or Continue with Microsoft under the password form. Click one, approve the request at the provider, and you are signed in. No password to choose, no confirmation e-mail to wait for.
What we do with the data
The provider tells us one thing: your verified e-mail address. That is all we take, and it is used only to find or create your CertWatchr account:
- If an account with that address already exists, you are signed into it. Nothing is duplicated; your domains, alerts and settings are where you left them.
- If not, an account is created with that address, on the Free plan, exactly as a password sign-up would be.
We do not store your provider profile, contacts, repositories, calendar or any other data, and we keep no access to your Google, GitHub or Microsoft account after sign-in. Nothing is posted or read on your behalf. The only place your e-mail address is used afterwards is the same as for any account: signing in, and the alerts you asked for.
We only accept an address the provider confirms is verified. If it cannot, the sign-in is refused and you will see an error — use a different provider, or register with a password.
Using a password as well
An account created this way has no password, and does not need one. If you would also like to sign in with a password, use Forgot password? on the sign-in page and set one; both ways then work.
Two-factor authentication
If you have two-factor authentication switched on, the code is still asked for after a social sign-in.
Deleting the account
Account → Delete account works the same way. An account without a password only asks you to
type DELETE to confirm.