Cookie notice

What cookies are

Cookies are small files a website asks your browser to keep and send back on later visits. Websites also keep information in your browser’s own storage, which works in a similar way but is not sent back automatically.

Rehumanize sets no cookies

None: not on this website, not on the research dashboard, not in the extension and not in the app. There is no analytics, advertising, social media or tracking code on our pages. Our pages may load files only from our own server, apart from the typeface described below.

What is kept in your browser instead

On this website:

• Your light or dark theme (rh_theme, in the browser’s local storage), kept only once you use the theme switch, until you clear it. It is never sent to us.

On the research dashboard, which only the research team and the people it gives access to can sign in to, and which anyone can open in demo mode:

• The dashboard’s theme (rh_dash_theme), the period shown (rh_admin_days), the build Explore, Rows, Live and Real articles show (rh_explore_build, rh_rows_build, rh_live_build, rh_articles_build), the columns you chose on Rows (rh_rows_cols_public, rh_rows_cols_private) and how far you got in the dashboard’s guided tour (rh_tour), in local storage, until you clear them. The dashboard asks our server for the data these choices pick out, such as the period and the build, but the stored entries themselves stay in your browser.
• Your sign-in (rh_admin_token, in local storage): the session that a password sign-in gives you, or the access key you typed, until you sign out or the server stops accepting it. The dashboard sends it to our server with each of its requests for study data, so that the server knows you may see the data. In demo mode it holds the demo key you typed (demo), which the dashboard never sends.
• A note that this visit’s opening was recorded (rh_opened, in session storage), so that the dashboard’s audit log records one opening per browser session. It goes when you sign out, or when your browser ends the session.

In demo mode, the real-articles example set is read from our server one page at a time. Those requests carry no sign-in and no cookie, and the dashboard keeps nothing about them in your browser’s storage.

In the extension and the app, your switches, your choices and the random install ID are kept on your device until you remove the extension or the app. The install ID is pseudonymous personal data: our server also keeps it with your answer to the research question, so that you can change or withdraw that answer, and never puts it on research records. In Rehumanize Research they also keep your participant code and study group, and the study extension keeps your country while research is on. In the extension, the random code for the current sitting, this sitting’s figures, counts waiting to be sent, the last mark you clicked and the list of posts already seen in the sitting are held in the browser’s memory and cleared when the browser closes. The privacy policy says which of these are sent to our server and why.

The typeface

The website and the dashboard ask your browser to fetch their typeface from a web-font service, which receives your IP address when it does. We do not control what that service records. The extension and the app do not use it.

Your choices

• Your browser’s settings let you see and clear what a website keeps in its storage. If you clear it, this website forgets your theme and the dashboard signs you out.
• If you block the web-font service, the pages still work and use one of your device’s own typefaces.
• Removing the extension or the app removes what it kept on your device.

Changes and questions

If what we keep in your browser changes, this notice changes with it. [To be completed by the operator: the date the notice takes effect.] Questions: rehumanize-project@tuta.com.