Skip to main content

Cookie policy

Version 2026-11-20, last updated 2026-11-20

zdr.sh uses two technical cookies and a few preferences in your browser. No analytics, no advertising, no third-party tracking. This page is part of the privacy policy.

1. The cookies#

CookiePurposeDurationProperties
__Host-rd_sessionkeeps you signed in to the dashboard7 days without use, and never more than 90 days from sign-in; 15 minutes while the second authentication factor is pendingtechnical, first-party, Secure, HttpOnly, SameSite=Lax
__Host-rd_csrfprotects requests that change data from cross-site attacks, with a double-submit tokenuntil the browser is closed__Host- prefix, Secure, SameSite=Strict, readable by the dashboard's own script (not HttpOnly)

A session ends after 7 days without use, and in any case 90 days after you signed in. Using the dashboard keeps a session alive, but never past that absolute life; signing in again starts a new one. You can end a session sooner from the security page of your account, which lists every session and the device it belongs to.

There is no consent cookie: your choices about the response cache and the memory vault are settings of your account, kept on our servers and never in the browser. The website sets no other cookie, and no cookie follows you to other sites.

2. What we keep in your browser#

The dashboard keeps some preferences and temporary values in the browser, needed for the features you use. They are not used to track you.

KeyWherePurposeDuration
themelocalStorageremembers the light or dark themeuntil you clear it
session-endedlocalStoragetells the other tabs of this browser that a session ended, so they sign out toountil you clear it
rackduck.banner.dismissedlocalStorageremembers that you closed the maintenance noticeuntil you clear it
rackduck.cookies.noticelocalStorageremembers that you dismissed the cookies notice, for this browseruntil you clear it
password_reset_noticesessionStorageshows the password reset notice onceuntil the tab is closed or it is first used

3. Why there is no banner#

The two cookies are technical: the site cannot sign you in or accept a form without them, so they need no consent banner. The preferences in section 2 store a setting you chose or remember that you dismissed a notice; they are not used to track you. A top-up is a crypto transfer you send from your own wallet, so no payment page of ours sets a cookie. If we ever added analytics or advertising tools, we would ask for your consent first.

4. The notice on the public pages#

No consent banner is needed and none is shown. The public pages and the dashboard carry a dismissible bar fixed to the bottom of the screen that says what this page says, with a link here. It reads: This site uses only the technical cookies the sign-in and the security need. No analytics, no advertising, no tracking. Dismissing it remembers the dismissal in the rackduck.cookies.notice key of this browser, so the notice stays dismissed until you clear the browser's site data or use another browser. Nothing else is recorded, and dismissing the notice changes no setting.

5. Managing them#

Your browser settings let you see, block and delete cookies and site data. Without the session cookie you are signed out, and without the CSRF cookie the dashboard refuses the requests that change data, so write to support@rackduck.com if you need to close the account or make another change with it blocked; the public pages keep working. Clearing the preferences restores the default theme and language.

6. Contact#

The version and date at the top identify the text in force; material changes are announced by email before they apply. For questions, write to support@rackduck.com.

This site uses only the technical cookies the sign-in and the security need. No analytics, no advertising, no tracking. Cookie policy