The information collected amounts to about same level of detail as services like npm or github would collect (maybe even less as we don't track a user id). To store this TSD uses Google Analytics in the excellent universal-analytics package.
We might at some point publish some anonymised aggregate stats to the Definitely Typed website.
The optional Github OAuth token is only used to authenticate with the Github API.
The token is not stored anywhere but the local machine. Using an OAuth token with additional scope is , even though it could make TSD work with private repositories.
If you need some more then a scope-limited Github OAuth token can be used to boost the limit to 5000.
If TSD is used in a way that needs many unique API calls in a short period (like using variable (see tsdrc-section).
Yes, and no (and later yes again) There is basic support for parsing semver-postfixes from the definition file names, and you can filter on this using semver ranges with the option: Try it with the 'node' definitions.
The CLI tool tracks some usage statistics about what definitions are installed though TSD in Google Analytics (using universal-analytics).
There is also a update-notifier service to check for TSD updates. The official plugin is grunt-tsd, and the community created gulp-tsd.
TSD is a package manager to search and install Type Script definition files directly from the community driven Definitely Typed repository.