Legal

Cookie policy

Last updated: 9 August 2026

A short document, because we use few cookies. This explains what they are, the three kinds we set, why there is no advertising in the list, and how to turn off the ones that are optional.

1. What cookies are

A cookie is a small text file a website asks your browser to store, so that it can recognise the same browser on a later request. Related technologies such as local storage and session storage do a similar job, and this policy covers those too. Cookies can be set by the site you are visiting, or by another service embedded in it.

They are useful for things like keeping you signed in between pages. They are also the standard mechanism behind advertising tracking, which is why they attract as much regulation as they do.

2. The cookies we use

On styleprofile.io and in the StyleProfile dashboard, our cookies fall into three buckets:

Three buckets, no more

Strictly necessary: Session and security cookies that keep you signed in to the dashboard, protect forms against cross-site request forgery, and balance traffic. The site does not work without these, so they are set without consent.
Preferences: Small settings we remember so you do not have to repeat them, such as a dismissed notice or a billing view you last chose. Not used to identify you.
Analytics: Aggregate measurement of which pages are read and which features are used, so we can improve them. Set only with your consent where consent is required, and configured to minimise the data collected.

Where the law requires consent for the analytics bucket, we ask before setting it and we record your answer. Declining leaves the site fully usable: nothing behind a paywall, nothing degraded, no repeated prompt on every page.

3. No advertising cookies

We set no advertising or cross-site tracking cookies today, and we run no retargeting pixels. We are saying that as a statement of current fact rather than a permanent promise. If that ever changes, this page changes with it first, the consent banner changes with it, and we will not switch anything on retrospectively for visits that already happened.

4. The try-on widget on retailer stores

When StyleProfile is embedded in a retailer’s online store, the widget sets only the functional cookies it needs to run a try-on session: keeping the pieces a shopper has selected together, holding the session token that ties an upload to its render, and preventing abuse of the render endpoint.

The widget does not track shoppers across sites. It does not build a profile of a shopper, it does not follow them to another retailer using StyleProfile, and it does not share cookie data with advertisers. The retailer’s own cookies, tag managers and analytics are separate from ours and are governed by that retailer’s cookie notice.

5. Managing cookies

You can change your mind at any time. Every major browser lets you view and delete cookies, block third-party cookies, or block them entirely, under settings usually labelled privacy, security or site data. Browsers also offer private windows that discard cookies when you close them.

Blocking strictly necessary cookies will stop the dashboard and the try-on session from working properly, because those cookies are the mechanism that keeps a session together. Blocking preference and analytics cookies costs you nothing except a slightly less convenient site.

6. Changes to this policy

We update this page when what we set changes, and the date at the top always reflects the current version. Material changes to the analytics or advertising position are announced to account holders by email as well as here.

7. Contact

Questions about cookies or any other data question: privacy@styleprofile.io. How we handle personal data more broadly is set out in our privacy policy.

Bridzia Sdn Bhd, registration 201201018441 (1003954V), Kuala Lumpur, Malaysia.