Doc 07 — Cookie Notice
| Document | 07 — Cookie Notice |
| Version | 07-cookie-notice-2026-08 (in force on publication) |
| Party / entity | DPW Pte. Ltd. (UEN 202017982R) ("DPW", "we", "us") |
| Audience | All visitors to the website and all Users of the Platform |
1. What this notice covers
1.1 This notice explains how cookies and similar technologies (including browser localStorage) are used on the Platform's website and client portal, what they do, and how you can control them. It applies to two audiences through two bindings: to visitors to the website, for whom it is referenced from Doc 01 — Website Terms of Use; and to Users of the Platform, for whom it is incorporated by reference into Doc 02 — Platform Terms of Service. Read it together with Doc 04 — Privacy Notice.
1.2 "Cookies" here means cookies and similar technologies such as localStorage entries — small pieces of data stored by your browser on your device.
2. What we actually use
2.1 Our use of cookies is deliberately limited to the following:
- (a) Authentication session cookies (strictly necessary). When you sign in to the Platform, our authentication service sets session cookies that keep you signed in securely and protect your account. These are set by the Platform's hosting and authentication infrastructure (functional categories; the providers are listed in Doc 06 — Subprocessor and Service Provider Notice). Without them, the client portal cannot work.
- (b) Consent-management storage (strictly necessary). When you make choices in our consent banner, we store a versioned record of your consent choices in your browser's localStorage so we can honour them on your next visit and evidence what you agreed to. You can change or withdraw these choices at any time (Section 5).
2.2 We do not currently set any third-party analytics or marketing trackers. No advertising pixels, no cross-site tracking, no third-party analytics cookies.
3. Categories in our consent banner
3.1 Our consent banner presents four standard categories:
- Necessary — required for sign-in, security and consent management. Always on; cannot be switched off through the banner.
- Analytics — would cover usage-measurement tools. None are currently set.
- Marketing — would cover advertising and remarketing tools. None are currently set.
- Preferences — would cover cookies remembering optional settings. None are currently set beyond the consent record itself.
3.2 The analytics, marketing and preferences categories exist in the banner for future use only. If we ever introduce a tool in one of these categories, nothing in that category will load unless and until you have given consent for it, and we will update this notice and the cookie table below first (Section 8).
4. Cookie table
| Name / pattern | Purpose | Type | Duration |
|---|---|---|---|
[AUTH SESSION COOKIE NAME(S) — TO BE CONFIRMED FROM PRODUCTION] | Keeps you securely signed in to the client portal; session integrity and token refresh | Strictly necessary (first-party cookie, set by our authentication infrastructure) | [TO VERIFY AT PUBLICATION] |
[SECURITY / ANTI-ABUSE COOKIE NAME(S), IF ANY — TO BE CONFIRMED FROM PRODUCTION] | Protects the website and portal against automated abuse | Strictly necessary (set by our hosting infrastructure) | [TO VERIFY AT PUBLICATION] |
[CONSENT STORAGE KEY — TO BE CONFIRMED FROM PRODUCTION] | Stores your versioned consent choices (which categories you accepted or declined, when, and against which banner version) | Strictly necessary (localStorage, first-party) | [TO VERIFY AT PUBLICATION] — persists until you clear it or withdraw consent |
This table must be verified against the production deployment immediately before publication and re-verified whenever the Platform's cookie behaviour changes.
5. How to change your choices
5.1 Through the banner. You can re-open the consent banner at any time using the cookie-settings control on the website or portal and change or withdraw your choices. Withdrawal takes effect from that point onwards; a fresh versioned consent record is stored.
5.2 Through your browser. You can block or delete cookies and clear localStorage through your browser settings. Browser help pages explain how for each mainstream browser.
6. Consequences of refusing cookies
6.1 Strictly necessary cookies are required for the client portal: if you block authentication session cookies, you will not be able to sign in or use the portal. Blocking the consent-storage entry means the banner will reappear and your choices cannot be remembered.
6.2 Because no analytics, marketing or preference cookies are currently set, declining those categories has no effect on your current experience.
7. Legal basis under the PDPA
7.1 Under the Personal Data Protection Act 2012, to the extent cookies collect personal data: strictly necessary cookies are used to provide the service you have asked for (sign-in, security, honouring your consent choices), and consent may be reasonably regarded as given by your use of those features for that purpose; any future analytics, marketing or preference cookies will be set only with your express opt-in consent through the banner, which you may withdraw at any time. How we handle personal data generally, and your rights, are set out in Doc 04 — Privacy Notice and Doc 19 — DPO / Data Subject Request Procedure ("DSR Procedure").
8. Changes to this notice
8.1 If we change the cookies we use — in particular, if we ever introduce anything in the analytics, marketing or preferences categories — we will update this notice and the cookie table, update the banner version, and seek fresh consent where required before anything non-essential loads. The version date at the top of this notice tells you when it last changed.
8.2 Questions about this notice: contact privacy@csfile.ai (see Doc 04 — Privacy Notice for full contact routes).