Privacy Policy

Thanks for stopping by. We're going to keep this short and sweet. I'm not an attorney or a big corporation. If you're here it's likely because you're one of my sponsors.

Personally Identifying Information

Any personally identifying information we collect about you is kept private and is never shared. So what is it that we do collect? Well in order to handle obvious things like authentication, and get a better idea about who my sponsors are and to be able to connect with you this site will track things from your public GitHub profile like:

  • Your name
  • Your Email (we require this to be provided if this is private on GitHub)
  • Your Company
  • Your GitHub User Id

GitHub Access

Upon logging in for the first time you will be prompted to Authorize Sponsor Connect with access to your GitHub Account. For some this may appear scary as the GitHub permissions allow access to Code, Issues, Pull Requests, Wikis, Settings, Webhooks and services, Deploy Keys, and Collaboration invites for both Public and Private repositories.

Sponsor Connect will NEVER access any of your public or private repos for any reason. However certain functions of Sponsor Connect currently in development and on the road map will Create NEW repositories upon your request. Those repositories will be private. It is for this reason that Sponsor Connect requires the ability to access your private repositories.

It is also important to note that outside of your active session Sponsor Connect does not maintain any knowledge or record of token returned by GitHub. This is never stored by Sponsor Connect to ensure that your GitHub account remains secure at all times.

Emails

We may on occassion send you certain emails. These emails are essential to your use of Sponsor Connect and most are not going to be the sort of thing you can opt-out of. These emails include a welcome message and notifications for expiring, expired, or revoked NuGet Keys. Naturally if you use the contact form through the Sponsor Connect site, you may get a response from me if it is warranted. Any general newsletter style emails you will have the ability to opt-out of.

Other Data

In addition to this we may collect statistics on your package download use through the integrated Sponsors NuGet Feed.

  • The Package Downloaded
  • The request IP
  • The API Key used

Usage information may help to give me an idea of a package's popularity and help drive conversations on tooling that helps you the most. Location based data may eventually be used to provide information I need when making decisions regarding what additional geo-redundancy I may or may not want to provide for people outside the United States.

Beyond that there really isn't anything for me to collect. I did start with I'm not an attorney or a big corporation. I don't have time to deal with lots of data collection about you. Unlike Facebook, Google, Twitter, Microsoft, basically everyone you do business with, I don't give a shit and am not selling your data. Cheers.

Cookies

You get a cookie to maintain your authenticated session. The web needs some way to persist the fact that you've authenticated. Beyond that we dont' save cookies to your computer, we don't add tracking cookies, look for tracking cookies... again this isn't a site from some massive company like Facebook, Google, Microsoft, Twitter that is spying on you... All of that said if you would like to send me some Chocolate Chip Cookies I'm all for it...