Cookie policy
A clear account of the browser storage used by this website, and how to manage it.
What the application uses
The application does not set HTTP cookies through its own code. Its sample portal uses localStorage to retain the workspace you choose to explore. Local storage is a browser technology distinct from a cookie, and is included in this notice because it stores information on your device.
No advertising cookies, tracking pixels or third-party analytics scripts are integrated into the application. There are no embedded third-party videos or remotely hosted fonts. This describes the application, rather than every possible setting in a hosting account.
The local storage inventory
The table below identifies the storage currently used by the application. The workspace is created when the sample portal is opened, rather than when a visitor reads a public article or policy page. It supports keeping sample records between visits; it is not used to build advertising audiences.
Search text, Journal filters and travel-fee inputs are held in temporary component state. They are not stored in a cookie or localStorage by this application.
| Name | bank-of-sanjay.workspace.v1 |
|---|---|
| Technology | First-party localStorage |
| Purpose | Retain the sample accounts, activity, goals, budgets, card preferences and family records in the selected browser profile. |
| When used | On opening and changing the sample portal. Public policy pages do not initialise it. |
| Duration | No application expiry. Remains until removed by browser controls or replaced by a workspace reset. |
| Server transmission | The application does not transmit this workspace to a remote account service. |
Cloudflare security technologies
Cloudflare features can set security or traffic-management cookies depending on the features enabled. For example, Cloudflare documents cookies used by bot-management, challenge and some rate-limiting settings. This is not confirmation that any particular cookie is enabled on Bank of Sanjay.
The hosting layer may use security cookies separately from the application’s local storage. Cloudflare’s documentation describes their purposes and durations; this notice does not claim that every hosting configuration is cookie-free.
Your choices
You can block or remove this website’s storage using your browser’s site-data settings. If localStorage is unavailable, the portal keeps changes in memory for the current session only. Clearing storage removes the saved workspace; returning to the portal creates the original sample records again.
Reset workspace replaces your custom entries with the initial sample state. To remove the site’s storage entirely, use browser controls. No optional advertising or analytics category is currently exposed by the application, so there is no simulated Accept all button or unused consent preference.
If new technologies are introduced
New storage or tracking purposes must be assessed before deployment. Where consent is required, the technology must wait for a valid choice, and refusal and withdrawal must be available. Where an exception applies, its particular conditions still need to be satisfied.
The operator must keep this inventory aligned with the actual application and hosting settings. A future account service, analytics tool or marketing integration would need its own accurate disclosure and controls.