Cookies and browser storage

How this site remembers your choices.

ResourceHive uses a small amount of browser storage to keep sign-in secure, remember your interface preferences, and complete account flows.

Last updated 27 September 2026

Authentication and sign-in cookies

The authenticated application uses HTTP-only cookies to maintain your ResourceHive session and protect account access. During Google sign-in or account linking, a short-lived flow cookie helps validate the sign-in request and is removed when the flow finishes or expires. These cookies are needed for the sign-in features you choose to use.

Interface preference

The application stores a first-party cookie named sidebar_state for up to seven days to remember whether you collapsed or expanded the dashboard sidebar. It does not contain your account credentials.

Signup browser storage

The application may use local or session storage to remember the email address and basic registration status needed to complete email verification and show the right signup feedback on your device. This storage is not an authentication credential. You can clear it through your browser settings; clearing it may mean you need to re-enter your email or restart the verification flow.

Browser notifications

Browser push is optional. If you enable it, your browser asks for permission and the application registers a push subscription so notifications can reach that browser. You can revoke permission in your browser and remove the subscription in ResourceHive notification settings. The browser may store its own service-worker and push data to provide this feature.

Website analytics

The marketing website and authenticated application use Vercel Web Analytics when deployed on Vercel. Vercel states that Web Analytics does not use cookies and uses a daily-reset visitor hash; it may process page paths, referrers, device and browser details, and general location for aggregated reporting.

Your controls

You can block or clear cookies and local storage using your browser settings. Blocking authentication cookies may prevent sign-in from working. Push permission can be changed in browser settings. This notice will be updated if ResourceHive adds other browser storage or analytics technologies.