RustViz usage logging and privacy
Applies to the RustViz playground and the RustViz tutorial when usage logging is turned on. Last updated: [date].
[Placeholder for the research-study paragraph: the study's name, who runs it (principal investigator), the purpose, the IRB determination and number if any, and a contact address. To be written by the maintainer / IRB.]
Why we record
RustViz is a research project at the University of Michigan. We record how people use the tutorial and the playground to learn how people come to understand Rust's ownership and borrowing, and to find out what RustViz explains badly or cannot draw.
What is recorded
- Which pages you open, how long they are in front of you (and in use), and how far you scroll.
- Which RustViz diagrams you look at, which parts of a diagram you point at (for example the arrow showing that
sis moved) and for how long, and the path of your pointer over a diagram, sampled ten times a second. - In the playground: which examples you pick, how much you edit, and each run's result, for example the rustc error codes (such as E0382) or that RustViz could not draw the program. The text of the programs you run in the playground, and of what you are editing (at most once every ten seconds), is recorded too: each distinct program once.
- Your screen size (rounded to 100 pixels), your browser's language setting and your time zone offset, and the website you came from (its host name only).
- Three random IDs: one for this page view, one for this visit (it changes after 30 minutes without activity), and one kept in your browser's local storage so that visits from the same browser can be linked. They are random numbers, not derived from anything about you.
What is not recorded
- No name, e-mail address or account. We never ask who you are.
- No IP address: our event collector does not record it, and its request logs are excluded from storage. [Maintainer: confirm once deployed. Google Cloud, which hosts the collector and the playground's compile service, processes your IP address to deliver requests; the compile service's own request logs are kept by Google Cloud Logging for N days. State that here, or exclude those logs too.]
- No cookies and no third-party analytics or advertising scripts.
- Nothing you type outside the playground's editor. The tutorial's own example programs are not sent: a diagram is identified by a fingerprint of its program.
Turning it off
- Use the Turn off button in Your data below. It applies to the whole site (the playground and the tutorial), in this browser. Recording stops, the random ID is deleted from your browser, and we receive one last message saying that logging was turned off (with the ID that is being deleted). Pages you already have open stop recording too. Turn on starts it again, with a new ID.
- We do not treat the browser signals Global Privacy Control and Do Not Track as a request to stop, because RustViz never sells or shares this data. Turn off above is how to stop it.
- Clearing this site's data in your browser also removes the ID.
Your data
This section needs JavaScript to show whether recording is on.
To have what was recorded with your ID deleted, e-mail your ID to comar@umich.edu. We cannot find your data without it, and we cannot tell who you are from it.
How the data is kept and used
[Placeholder: where the data is stored (Google BigQuery, project
rustviz-playground), who can access it (named researchers), how long it is kept, how deletion requests are handled and how fast, and what is published (aggregate results and de-identified excerpts only). To be written by the maintainer / IRB.]Contact
Questions, and requests to delete data: comar@umich.edu.