What cookies are
Cookies are small text files a website asks your browser to keep. They let a site remember that you are signed in, or what you chose last time. Browsers also have localStorage and sessionStorage, which do a similar job but are not sent to the server with each request. We list those here too, because from your point of view they are the same thing: data a site keeps in your browser.
Your choice when you first visit
On your first visit, a bar at the bottom of the page offers Accept diagnostics or Decline diagnostics.
- Until you choose, the site stores nothing in your browser apart from what is strictly necessary for something you do, such as signing in. The diagnostics agent does not load.
- If you accept, the diagnostics agent starts and stores two session-only entries (see "Diagnostics" below).
- If you decline, it never starts.
Either way we store your answer in the mait-diagnostics-consent cookie on the mait.sh domain, so one answer covers mait.sh, staff.mait.sh and xCAIO in that browser, and none of them asks again. The cookie lasts 180 days. After that, the bar asks again.
On mait.sh, an explicit acceptance also sends a small acceptance observation to our own server. It contains only accepted, without sign-in cookies, an account or session identifier, or the address of the page you accepted on. We count received observations, including repeated choices; they are not counts of people. Reading an existing choice or reloading a page sends no acceptance observation. We send no observation for a decline, so declined choices are unmeasured and we cannot calculate an acceptance percentage. Requests already sent before withdrawal cannot be recalled.
Cookies and browser storage we use
This is the complete list. Everything is first-party: we set it, for our own sites. We use no advertising cookies, no cross-site tracking cookies and no third-party analytics.
Strictly necessary: mait.sh
These cannot be turned off. The site cannot sign you in or remember your answers without them.
…_0, …_1, …).7 daysaccepted or declined. It is shared by mait.sh, staff.mait.sh and xCAIO, so one answer covers all three. Our pages read it only in your browser. As a cookie, it is also sent to our servers, which do not use it.180 daysdenied. If this entry is missing, click tracking follows your diagnostics choice. Never sent to our servers.Until you clear it…_0, …_1, …).accepted or declined. It is shared by mait.sh, staff.mait.sh and xCAIO, so one answer covers all three. Our pages read it only in your browser. As a cookie, it is also sent to our servers, which do not use it.denied. If this entry is missing, click tracking follows your diagnostics choice. Never sent to our servers.On our internal development channel only, a single sign-in cookie named _oauth2_proxy_htpasswd replaces the three provider cookies. It is limited to that host and never appears on the public sites.
Strictly necessary: staff.mait.sh
The shared mait-diagnostics-consent cookie holds your diagnostics answer here too. The mait.sh sign-in cookies (_oauth2_proxy*) are also sent to staff.mait.sh, which checks that your sign-in is still valid.
Strictly necessary: xCAIO (xcaio.mait.sh)
The shared mait-diagnostics-consent cookie holds your diagnostics answer on xCAIO too. The mait.sh sign-in cookies (_oauth2_proxy*) are also sent to xCAIO, which checks that your sign-in is still valid.
Diagnostics: only after you accept
The diagnostics agent sets no cookies. The diagnostics collector never receives your sign-in cookies: our servers remove cookies from requests to it.
Diagnostics
If you accept diagnostics, our agent (Grafana Faro) sends the following to a collector on our own servers in the EU:
- the pages you open, with their full addresses
- on mait.sh, a coarse category for the referring page when diagnostics start: internal, recognised search engine, recognised social site, other, or direct-or-unavailable. We send no referring address, domain or query with this category. An empty browser referrer can mean a direct visit or that the browser withheld it
- page-load and responsiveness timings
- JavaScript errors, with their stack traces
- console messages at information, warning and error level
- the addresses and timings of requests the page makes to our own servers
- security-policy violation reports from your browser
- your browser, operating system, user-agent string, browser language and window size
- the session identifier listed above
The referring-page category describes this document when you accept diagnostics, which may be partway through a journey. It stays the same during navigation within that document, including a diagnostics session rotation, and is recomputed on a new document load. It does not prove the original source of your visit. It adds no browser-storage entry.
It does not record what you type or enter into forms. It takes no screenshots and does not replay your session. Before diagnostics are buffered for sending, it removes recognised sign-in codes and tokens from web addresses, recognised token-shaped values from text, and values in explicitly sensitive fields. These checks reduce accidental disclosure; they do not recognise every possible secret in arbitrary error or console text.
Click tracking. On mait.sh, if you have accepted diagnostics, we also record when you click a sign-in button (Google, GitHub or Microsoft). We record nothing else about your clicks. You can turn click tracking off below and keep diagnostics on. Turning click tracking off takes effect at once. Turning it back on takes effect from your next visit.
This is not a third-party analytics service. We run both the collector and the storage ourselves on our EU servers. Nothing goes to Grafana Labs, an advertising network or an analytics provider. We keep this data for 7 days. Deriving a country from the connection is not a cookie and does not run in your browser. The privacy policy describes it.
If you are signed in, diagnostics on mait.sh, staff.mait.sh and xCAIO are linked to your MAIT account identifier, never to your sign-in provider's identifier. The privacy policy has the details. Your account page also has switches that turn diagnostics (on all three sites) and click tracking (on mait.sh) off for your account, even in a browser where you accepted.
Event pages add no cookie or browser storage; their campaign tags are part of the page address.
Your choices for this site
The diagnostics switch applies to mait.sh, staff.mait.sh and xCAIO in this browser: staff.mait.sh and xCAIO link here as "Privacy choices". Click tracking only exists on mait.sh. Our command-line tools and other products have their own setting on your account page.
Turning diagnostics off here stops diagnostics on the current mait.sh page immediately, including pending startup. Turning them back on after they have stopped on this page requires a reload. If they have not started on this page yet, accepting starts them immediately. The shared choice applies on the next page load on staff.mait.sh and xCAIO; changing it here does not stop an already-open page on either site.
Third-party cookies
We set no third-party cookies. When you choose to sign in, you go to Google, GitHub or Microsoft. They set their own cookies on their own domains under their own policies. We cannot read those cookies, and we set nothing on their behalf.
Our pages load no fonts, scripts or images from third-party servers, so no one else receives a request from your browser when you view our pages.
How to manage cookies
Every major browser lets you block or delete cookies, usually under Settings, Privacy or Security. The sign-in cookies above are what keep you signed in. If you block them, you cannot sign in.
Deleting cookies does not clear localStorage or sessionStorage. To remove the entries listed above, clear this site's data in your browser settings, or use your browser's developer tools. Deleting the mait-diagnostics-consent cookie makes the diagnostics bar ask you again on all three sites. You can also change your answer with the switch above.
Contact
For questions about cookies, see our privacy policy or write to privacy@mait.sh.
For the existing Google, Microsoft and GitHub sign-in links, consented behavior capture also records a bounded provider navigation intent when you activate the link in the same tab. It uses the existing diagnostics transport and records only the provider category and event time with the existing diagnostics context. It does not record the destination address or query, create another browser-storage record, or prove that a provider received a request, authentication succeeded or an account was created. Diagnostics or behavior decline stops these intent observations on the current Portal page; ordinary diagnostics continue when only behavior is declined.
Last updated
November 8, 2026