Privacy
No tracking cookies, on this page or on any book. Here is everything that is stored, and how to turn each part off.
Reader settings, in this browser
Each site remembers your choices in your own browser (local storage): light or dark, text size and width, paragraph numbers, whether margin comments are on, and that you have seen the privacy note. Nothing of it is sent anywhere. To clear it, clear this site's data in your browser's settings; the book's Aa menu changes each setting.
Visitor counts (Plausible)
Pages on the live sites are counted with Plausible Analytics, which sets no cookies and stores nothing that identifies you: only counts of visits, pages, referring sites, countries and device types. Drafts and previews are never counted. The counts are public (Platform statistics below, Book statistics on each book). To stop being counted, block plausible.io with a content blocker.
Margin comments (Hypothes.is)
Margin comments are switched off on the books for now, and Hypothes.is isn't loaded at all. Comments for classes are coming soon. When they come, they will be provided by Hypothes.is, loaded from hypothes.is, which may set its own cookies (when you sign in there to comment, for example), and seen only by the members of your class's group; Aa › Margin comments › off will stop Hypothes.is loading.
The author site: your email address and your name
People who work on a book sign in to the author site with their email address. The author site stores, for each of them:
- Email address: to send sign-in links, invitations to a book, and (unless you switch them off under People) one email for each new reader suggestion on your books. It is never shown to readers, never put in the book or its history, and never in the platform's public records.
- Display name: the name the book credits you by, chosen by you when you join. It appears in the book's credits and in its public history (with any reason you give for declining a reader's suggestion, and any comment you add to one), because the books are published under CC BY-SA and crediting the people who wrote them is part of that licence.
- Sign-in: a cookie that only the author site can read (HttpOnly), for 30 days on that device, or until you sign out; Sign out everywhere ends every one. Sign-in links work once, for 15 minutes; invitations once, within seven days.
- Where you're signed in, and new-sign-in emails: for each browser you sign in on, a second HttpOnly cookie (a random number, kept for 400 days) and, on the author site, the browser and system in words (“Chrome on macOS”, never the full browser details), when it first signed in and when each session was last used. That is how Where you're signed in lists your sessions, and how a sign-in on a browser your account hasn't used before is spotted: you get an email saying when and on what, with This wasn't me to sign out everywhere. A browser not used for 400 days is forgotten.
- What changed on a book's people: who invited, removed or joined, and who published, with the date, shown to the book's people.
Emails are sent by Resend, which processes your address and the email to deliver it, on the platform's behalf. When you are removed from your last book, your email address is deleted from the author site at once; your display name stays in the credits of the books you worked on.
How your contributions are handled
Suggest an edit and Note to the authors
When you send a suggestion or a note, the platform takes the name you give (any name you like), your text and any comment, and which page and paragraph it is about, with that paragraph's text as you saw it. No email address is asked for or kept.
All of it is published openly, straight away: as an issue in the book's public GitHub repository, and on the book's History page. It is published under the book's licence, CC BY-SA 4.0, the same as the book. So only send what you are happy to see published under the name you give.
Following your suggestion
After you send it, you are shown a link: Follow your suggestion. It opens your entry on the book's History page, which says whether it is proposed, being edited, published or declined. The link holds nothing about you; it is the same public entry anyone reading the History page sees. Once the authors decide, their decision, the reason they give and the name of the author who decided are public there too.
Signing in with GitHub to edit a page
Editing a page in the book asks you to sign in with GitHub. GitHub tells the platform your username, your account number and your display name; the platform asks for no permissions and doesn't read your email address. The GitHub token is thrown away at once, and nothing about you is stored on the platform's servers: the browser tab keeps your sign-in for at most eight hours, and a short cookie is used for ten minutes while you sign in.
An edit you propose is published as a pull request in the book's public GitHub repository, saying it was proposed by your GitHub username. Its change is recorded under your display name (or your username) and GitHub's no-reply address for your account, never your own email address. Reading needs no sign-in at all.
Author sign-in by email
Authors sign in with their email address. What that stores, and for how long, is set out under The author site above: in short, the address and display name, sign-in links that work once for 15 minutes, a sign-in of 30 days, and the emails, sent by Resend.
IP addresses
The platform's API (api.confused4now.org) and the author site (author.confused4now.org) limit how often one connection can send or ask for something, for example 100 suggestions an hour, or 20 sign-in links an hour. Neither stores your IP address to do this. Each counts under a code made from the address with a random key of its own, and that key changes at midnight (UTC). The API deletes the old key a few minutes later; the author site deletes it the first time anyone uses it after midnight. While a key exists, the code could in principle be matched to an address by trying every address with that key; once the key is deleted, it can't, and codes from different days can't be linked. Each count is deleted after its hour is over: by the API within about a day, by the author site the first time it is used the next day at the latest.
If a suggestion or edit has to be finished in the background (when the API is busy), only that code is kept with it, never the address. Neither the API nor the author site writes IP addresses to its logs.
Your name in the credits
The names of people who contributed are shown on each book's contributors page and in its History. To have your name hidden from the credits, or the text of a contribution removed, email hello@confused4now.org with the book and the contribution; the book can then leave your name out of its credits. As the books' public GitHub repositories keep their history, text already published there may remain in that history.