THE COLLEGE OF MAASIN · STUDENT CLEARANCE
Cookie & Browser Storage Policy
This page explains the browser storage used by this application and why it is needed. It must be revisited when production hosting or third-party integrations change.
The application explicitly sets an authentication session cookie. I did not find advertising or analytics-cookie code in the supplied application source. This source review does not establish what a hosting platform, reverse proxy, security service or later-added third-party script may set; production network traffic still needs checking.
1. What the application uses
| Name / technology | Purpose | Lifetime / settings |
|---|---|---|
CMCLEAR session cookie | Maintains the server-side session used for sign-in state and session-bound form-protection data. | Session cookie (the application sets no persistent expiry); path scoped to the app; HttpOnly; SameSite=Lax; Secure when the request uses HTTPS. Logout, security invalidation or configured server session limits may end the session sooner. |
| Service-worker Cache API | Caches selected same-origin app-shell resources such as stylesheets, JavaScript, logo, fonts and the offline page to help the app load. | Browser-managed cache, not an HTTP cookie. The service-worker version clears older app-shell caches when the new version activates. |
| Privacy notice dismissal | Remembers that the user dismissed the inline information notice during the current tab/session. | First-party sessionStorage only; no account identifier is stored. It clears when that tab’s session ends or browser storage is cleared. |
2. Why the session cookie is essential
Authentication and form protection use a server-side session. Blocking the session cookie may prevent sign-in, invalidate forms or make protected workflows unavailable. The application configures the cookie as HttpOnly so page scripts cannot read it, SameSite=Lax to limit cross-site sending in common cases, and Secure when served over HTTPS. Production should use HTTPS throughout.
3. Optional analytics and advertising
No analytics or advertising-cookie integration was identified in the application source reviewed. The current notice therefore informs users about essential storage; it does not show a misleading “Accept all” button or imply tracking is present. If non-essential analytics, advertising, embedded third-party media or other tracking is introduced, the College must assess the legal basis and applicable consent requirements, document each vendor and purpose, and ensure optional tags do not run before any required opt-in.
4. Third parties and server logs
Production browser network tools and hosting configuration should be checked for cookies or identifiers set by a CDN, web application firewall, reverse proxy, hosting platform, monitoring tool or embedded service. Server access logs are separate from browser cookies but may contain IP addresses, user agents, requested paths and timestamps. The final policy must match the actual production environment and provider contracts.
5. Managing storage
You can clear cookies and site data in your browser settings. Clearing the session cookie may sign you out, and blocking it can prevent the application from working. The privacy notice may be dismissed without accepting optional tracking; policy links remain available in page footers. Its dismissal state is session-scoped.
6. Change control
Before adding a cookie, local-storage item, SDK, analytics tag or embedded vendor, the application owner should record its name, provider, purpose, duration, data collected and whether it is essential. Review the Privacy Notice and this policy, and add a preference manager if non-essential storage requires opt-in.