Privacy information

This page says what Assayon keeps in the browser and where it processes data.

The assayon-locale cookie remembers the language of the screens for a year from when it was last written. The language switch writes it; without the switch being pressed, signing in, signing out and the button on the page a link from an email opens may write it too.

The assayon-locale-pending cookie holds a language chosen without being signed in until signing in saves it to the account, for a day at most.

A script on the page can read both cookies; they hold nothing but the language’s code.

Signing in and the button on the page a link from an email opens write the sign-in session cookies, whose names begin with sb-; they let the application know who is signed in. A request to reset the password writes one more such cookie, tied to that request. When signing in, checking a link from an email and requesting a password reset, the application passes the person’s IP address to Supabase Auth, so that the limit on attempts counts for that person.

After a password is set, the browser keeps one marker in the tab’s session storage, assayon:password-saved. The dashboard reads it once, says the password was saved and removes it.

When a page is reloaded or left, the browser keeps in the tab’s session storage, under the name assayon:scroll with the screen’s path, how far the screen was scrolled, so that a reload or a return with Back comes back to the same place; the entry is removed once the screen has read it, and at the latest when the tab is closed.

Assayon uses no analytics and no tracking tools, and keeps nothing in the browser’s local storage.

The application’s server functions run on Vercel’s servers in Frankfurt, and the database with accounts and assessments is with Supabase in the same region. Emails with an invitation or a link to change the password are sent by the home.pl mail server.

For questions about privacy, write to office@assayon.com.