1. What cookies do here
Cookies are small values stored by a browser and sent with matching website requests. WealthLens uses them for your cookie decision, requested financial record keeping, onboarding and tutorial progress, and optional preferences. Cookies containing financial records are transmitted to the Next.js server; they are not device-only storage.
2. Purpose-based categories
The necessary decision record remembers your cookie choice. Requested-service storage is activated when you deliberately start the finance application or a tutorial; the finance application needs its ledger cookies to persist records. Public information does not require financial storage.
Optional preferences remember appearance, language and the sidebar between visits. They are disabled until accepted. No analytics or marketing integration is installed, so there are no analytics or marketing categories to enable. Refusing optional preferences does not block the finance application.
3. Actual cookie inventory
The following inventory follows the application's cookie definitions. Maximum lifetime describes the configured expiry, not a guarantee that a browser will retain the value for that period. All listed cookies belong to WealthLens; no third-party tracking cookies are created by the application.
| Cookie | Purpose & category | Maximum lifetime | Access |
|---|---|---|---|
| wl_consent | Necessary decision record Versioned cookie choices and the time of your decision. | 180 days | Client-readable |
| wl_demo | Requested finance application Records your deliberate activation of cookie-backed finance functionality. | 180 days | Client-readable |
| wl_d0..wl_d2 | Requested finance application Profile and financial records, compressed into up to three cookie chunks. | 365 days | Server-managed (HttpOnly) |
| wl_draft | Requested finance application Short-lived onboarding draft, including entered profile and account details, to preserve progress during a language reload. | 1 hour | Client-readable |
| wl_theme | Optional preferences Remembers your selected light, dark or system appearance. | 365 days | Client-readable |
| NEXT_LOCALE | Optional preferences Remembers your selected language. | 365 days | Client-readable |
| sidebar_state | Optional preferences Remembers whether the desktop sidebar is expanded. | 7 days | Client-readable |
| wl_tour | Requested tutorial Remembers completed or skipped tutorials and their versions. | 180 days | Client-readable |
All cookies listed here are first-party and use Path=/. SameSite=Lax limits cross-site delivery; Secure is set on HTTPS deployments. HttpOnly financial cookies cannot be read by application JavaScript. Browser expiry policies can shorten these lifetimes. Successful financial writes renew ledger-cookie expiry. Compression is not encryption.
4. Manage your preferences
Use Cookie Preferences from the footer, legal pages or Settings. Accept All permits the optional preference category; Reject Optional Cookies leaves it disabled. Customize lets you make and save that choice explicitly. Continued browsing is not treated as acceptance.
Starting persistent finance functionality is a separate deliberate action after its storage disclosure. If you do not activate it, public pages remain available and financial persistence is not silently enabled.
5. Withdrawal, reset & financial records
You can withdraw optional preferences by saving them as disabled. The application stops their persistence and clears the preference cookies it controls. Theme changes can still apply during the current session, and the language can still be selected through its URL.
Changing or resetting cookie preferences does not silently delete financial records. Use the separate confirmed data-reset controls in Settings to remove finance data. To remove every site cookie, use your browser's site-data controls. Exported backup files must be removed separately.
6. Browser controls & storage limitations
Your browser can block, inspect or delete this site's cookies. Blocking required finance storage prevents reliable persistence; clearing it may permanently remove records. Private browsing and browser retention policies may shorten availability.
Ledger storage is limited to three cookie chunks, each with a value cap of 3,800 characters. Oversized writes are rejected and retain the previous saved document. Cookies are not a substitute for durable financial records or secure backup storage.
7. Policy changes
When cookie purposes materially change, the policy version must be updated and choices requested again. This inventory must be reviewed alongside code changes and the actual deployed host. No third-party cookie-clearing limitation is claimed because no third-party cookie integration exists in this application.
Contact & questions
The following developer contact is configured for this project. For a privacy question or accessibility issue, describe the issue without including financial records, cookie contents or backup files. A verified legal entity, registered address and governing jurisdiction have not been established for this application.
Phan Hoàng Quốc Tú
tuphan694@gmail.com