Cookie and Similar Technologies Policy
The audited Website uses one first-party localStorage preference and no cookies. This Policy explains how future similar technologies must be handled.
1. Cookies and similar technologies
Cookies are browser-stored values. Similar technologies include localStorage, sessionStorage, IndexedDB, pixels, scripts, SDKs, advertising identifiers and consent records.
2. Strictly necessary technologies
Technologies essential to deliver a requested service may qualify for a consent exemption, but it must be assessed narrowly.
3. Functional technologies
The active theme preference remembers a visitor's light, dark or system choice. It contains no calculator inputs.
4. Preferences
Visitors can change the theme or clear site storage through browser controls.
5. Analytics
No analytics is configured. It must not activate before required consent and documentation are in place.
6. Advertising
No ad technology is configured. Future behavior may depend on region, consent, provider settings, restricted-data-processing settings, and limited or non-personalized ad availability.
7. Consent management
No CMP is installed. A decorative banner or local “accepted” flag is not a suitable consent platform where consent is required.
8. Third-party technologies
No third-party storage entries are active. Future providers must be added using verified names, purposes and durations.
9. Session and persistent duration
Session storage normally ends with a session; persistent storage remains until expiry or deletion. Exact active durations appear below.
10. Requesting consent
Where required, non-essential technologies must remain disabled until a freely given, specific, informed and unambiguous affirmative choice.
11. Withdrawing consent
Future consent-dependent processing must provide an accessible way to change or withdraw choices for the future.
12. Reopening privacy choices
The footer control attempts to open a configured CMP integration and otherwise explains that none is available.
13. Browser controls
Browsers can block or delete storage. Blocking a requested preference may prevent it being remembered.
14. Consequences
Deleting the theme entry resets the visual theme to the system default. Core calculations continue.
15. Current inventory
This table is generated from the verified storage registry.
| Name | Type/category | Purpose | Duration and consent |
|---|---|---|---|
| theme | localStorage; functional; first-party | Remember the visitor's light, dark or system theme preference. | Until the visitor clears site data or changes the stored preference. Consent required: no. |
16. Changes and contact
Update the inventory and version when technologies change. Use the configured privacy channel for questions.
- General support
- admin@goldwavedynamicslimited.com
- Privacy and data rights
- admin@goldwavedynamicslimited.com
- Copyright complaints
- admin@goldwavedynamicslimited.com
- Accessibility feedback
- admin@goldwavedynamicslimited.com
- Security reports
- admin@goldwavedynamicslimited.com
- Advertising and affiliate enquiries
- admin@goldwavedynamicslimited.com