This tutorial uses two kinds of cookies:
This tutorial uses the
express-session module to store variables from one page to another. These variables are stored in memory
on the Glitch server that hosts this tutorial, and there's a cookie on your browser
that's used to look up these variables. Examples of variables include your application
identifier (id), application secret, the OAuth scopes that you select, the authorization code,
and other data that are required to implement this tutorial. If you want to see all of the
variables and exactly how they're used, look in the server.js and api.js
files in the
nodejs code that implements this tutorial.
We're data-oriented developers who follow a typical agile engineering process. That means we're really interested in whether you're finding this tutorial useful, so that we can figure out how to make it better. While we encourage you to send us feedback, we realize that you're probably too busy to drop us a note. So, we use Google Analytics to answer questions about how well this tutorial is working. Is anyone using this tutorial at all? Are developers getting stuck at a specific point? Are there parts of the tutorial that are more popular than others?
To answer these questions, we do not need any personally identifiable information (PII) from you. We'll do our very best to ensure that this tutorial isn't sending any PII to Google or storing any PII itself. If you (as a developer who may know more about these things that we do) find anything in the code that seems to be contrary to this commitment, please let us know.
And if you want to prevent Google Analytics from capturing any information, please have a look at this Google support page to learn how to opt-out. Or you can use the "Remix Project" capability on Glitch to create your own copy of this tutorial, which will disable Google Analytics.