Signing In with Google or Microsoft

What information is — and isn’t — shared when you link your account

The short version

When you sign in with Google or Microsoft and link it to your TEC record, information flows one direction only: a little bit of basic profile information comes from Google or Microsoft to us. Nothing about you or your TEC record is ever sent back to them. Linking your account does not give Google or Microsoft any new information about you, your family, or your involvement with TEC.

What Google or Microsoft share with us

When you choose to sign in, and only after you approve it on their screen, they tell us three things:

  • Your name
  • Your email address
  • A unique account ID (a long string of characters that simply lets us recognize your account next time)

We use these to find your existing TEC record and connect it to your sign-in, so you don’t need to remember a separate password.

What they do not receive

Google and Microsoft never see anything from our records. They do not receive:

  • Your TEC history, the teams you’ve served on, or any weekend information
  • Which TEC record you were matched to
  • Any health, registration, family, or contact details we keep
  • Anything you do on this site after you sign in

What we store

All we keep is a simple connection between your Google or Microsoft account ID and your TEC record — essentially a note that says “this account belongs to this person.” That connection lets you sign in without a password. You can ask us to remove it at any time.

What Google or Microsoft can see on their side

The only thing they know is that you chose to sign in to “Southern Minnesota TEC” — the same record they keep any time you use your account to sign in to a website. That record contains nothing about TEC itself.

We also request read-only access to your basic profile only. We never request access to your email inbox, calendar, contacts, files, or anything else in your account.

Technical details

Show technical details

For the technically inclined, here is exactly what happens:

  • We use standard OAuth 2.0 / OpenID Connect sign-in.
  • Google is requested with the scopes openid email profile.
  • Microsoft is requested with the scopes openid email profile User.Read (read-only profile).
  • After you consent, we call the provider’s userinfo endpoint and read back only your subject/account ID, email, and display name. No write scopes are requested, so there is no path by which we could send data into your Google or Microsoft account.
  • Matching to your TEC record happens entirely on our own server. The result is a single stored row linking your account ID to your TEC record. Nothing about that record leaves our database.

Questions?

If you have any concerns about how your information is handled, please reach out to the council. We’re glad to talk it through.