DEPTHUB

Loading platform...

Skip to content
← Back to DeptHub

COOKIES & BROWSER STORAGE

A clearer view of browser storage.

How cookies, saved preferences and cached files help DeptHub work—and the controls available in your browser.

Updated 9 November 2026 Fourah Bay College

You stay in control of your browser

You can clear site data, change notification permissions and remove an installed app. Clearing authentication cookies signs you out; removing saved files can affect offline loading.

1. What browser storage does

Cookies are small pieces of information stored by your browser and sent with relevant requests. Local storage, session storage, IndexedDB and browser caches can hold preferences or application data on your device. These technologies serve different purposes; not every saved item is a tracking cookie.

DeptHub uses browser storage for account sessions, interface preferences and app functionality. The precise items present depend on the deployment, whether you are signed in, and which features you use.

2. Storage used by the service

PurposeWhat it doesYour control
Authentication & securityCookies support sign-in, session renewal and security checks. Supabase authentication uses session cookies in the current deployment.Sign out or clear site cookies. Blocking essential cookies can prevent sign-in.
PreferencesSaved settings can remember your chosen appearance and other interface preferences.Change settings in the app where available, or clear site storage.
App files & cachesA service worker can cache public interface files and an offline page. This does not make private academic or financial records generally available offline.Clear cached site data, remove the installed app or manage service workers in browser settings.
NotificationsIf you enable browser notifications, browser permissions and a subscription support delivery to that browser.Disable the permission in your browser and use account notification controls where available.
Hosting & enabled servicesHosting/security services and an enabled external payment flow may process their own request information or use storage under their notices.Review the relevant provider notice and browser permissions.

Optional tracking that requires consent should identify its purpose and offer applicable choices before it is enabled. Operational request logs are described in the privacy policy.

3. Your browser controls

  • Open your browser’s settings for this site to review cookies, storage and permissions.
  • Clear site data to remove stored sessions, preferences and cached files on that device.
  • Block or allow notifications separately from cookies.
  • Use browser privacy settings to control third-party storage or clear data when the browser closes.

Browser settings affect this device or profile. They do not delete institutional records held on the server, reverse a payment or close your account. Private-browsing modes may restrict saved preferences or installation features.

4. Shared devices & payments

Sign out before leaving a shared device, avoid saving credentials there and remove sensitive downloaded files. Signing out ends your account session but may leave general preferences or public app files in the browser.

Do not assume a browser cookie, screenshot or cached page proves that a payment has settled. Use the current payment status in your account and contact Finance with your reference if a result is unclear. Never share a wallet PIN or one-time code.

5. Updates & questions

The date at the top of this page identifies the latest update. For help with browser access, contact ICT Support. For platform privacy or storage questions, contact Lion Code Innovation. Read the privacy policy and terms of service for information handling and service responsibilities.