Cookie Policy
Last updated: October 2026
This Cookie Policy explains the browser cookies and similar session technologies used by the Wealth Gullak website and investor portal. It should be read with the Privacy Policy.
6.1 Essential cookies
The platform uses first-party cookies that are necessary for secure sign-in, session management, protection against forged requests, API authentication, single sign-on, account/tenant context and basic interface preferences. Blocking essential cookies may prevent sign-in or core platform functions.
| Purpose | Examples used by the Wylth platform | Treatment |
|---|---|---|
| Session and sign-in | ASP.NET_SessionId, AccessToken, session, SSO/session identifiers | Essential. Used to maintain authenticated sessions and access. |
| Security | RequestVerificationToken and related security/session controls | Essential. Used to prevent misuse such as forged requests and to protect sessions. |
| Account / portal context | User/account and white-label partner context identifiers | Essential or functional where needed to show the correct authorised account/tenant. |
| Preferences | Language, menu/sidebar and theme preferences | Functional. Used to remember limited interface choices. |
6.2 Optional analytics or similar technologies
We do not intend to activate non-essential analytics, advertising or similar tracking technologies unless the relevant provider, purpose and category have first been disclosed and the user choice required by applicable law has been implemented. Until then, such technologies should remain disabled in the Wealth Gullak production build.
6.3 Your choices
Where optional cookies are used, the cookie interface will allow users to accept or reject them and later change their choice. Browser settings can also be used to block cookies, although blocking essential cookies may affect sign-in and platform functionality.
6.4 Mobile app
Mobile applications may use secure local/session storage and platform notification tokens for core functionality. App permissions are requested separately at the time a feature requires them. See the Privacy Policy for the current permission categories.