Cookie and Storage Notice

This notice explains how BinaryBias uses cookies, browser localStorage, session storage, and similar technologies in the BinaryBias web application. These technologies may store information on the user's device or read information that is already stored on that device.

BinaryBias is a paid SaaS product for non-personalised FX probability analytics. The service does not use cookies or local storage to provide personalised investment advice.

BinaryBias may use strictly necessary cookies and storage where they are needed to provide the service requested by the user. This includes technologies required for account access, authentication, subscription status, fraud prevention, security, load balancing, realtime session operation, and remembering choices that are essential to the requested service.

These technologies are not used for advertising. They are not optional where disabling them would prevent BinaryBias from signing the user in, verifying access, securing the service, or delivering the requested application session.

BinaryBias may save local preferences in the user's browser so the interface works consistently on the same device. These values are stored locally and are intended to support product usability rather than cross-site tracking.

Current examples include binarybias.modelOutputOverlayPosition, which may remember the position of a chart or model-output overlay, and binarybias.riskDisclosureDismissedUntil, which may remember that a user has dismissed a risk disclosure until a stated time.

BinaryBias may rely on specialist providers for authentication, customer identity, subscription access, billing, or payment workflows. For example, authentication and subscription-related cookies may be set by providers such as Clerk, and payment or billing providers may set their own necessary cookies when their services are used.

Provider cookies may be first-party or third-party cookies depending on the technical setup. Provider cookie names, purposes, domains, and durations may change as providers update their services or as BinaryBias changes its configuration.

The current known storage categories are:

• Authentication and session. Used to sign users in, maintain a secure session, protect accounts, and verify access to the paid service. Expected duration depends on the authentication provider, user settings, and security controls.
• Subscription and billing. Used to confirm that an account has access to paid features and to support billing or payment flows. Expected duration depends on the subscription or payment provider.
• Application security. Used for fraud prevention, abuse prevention, request protection, rate limiting, or similar service protection purposes. Expected duration depends on the security purpose.
• Realtime service operation. Used where needed to deliver realtime application updates and maintain the user's active service session. Expected duration is generally limited to the active session unless a provider requires a longer technical duration.
• Local interface preferences. Used to remember product choices on the same device, including binarybias.modelOutputOverlayPosition and binarybias.riskDisclosureDismissedUntil. Expected duration lasts until the value expires, is replaced, or is deleted by the user or the browser.

BinaryBias does not use non-essential analytics, advertising, retargeting, affiliate tracking, or marketing cookies unless the user has been given the required information and consent choice.

If non-essential analytics or marketing technologies are introduced, BinaryBias will update this notice, identify the relevant providers and purposes, and request consent before those technologies are used where consent is required.

Strictly necessary technologies are used because they are needed to provide the BinaryBias service requested by the user. Non-essential technologies, such as optional analytics or marketing technologies, remain disabled unless the user has been given clear information and has made a consent choice through an appropriate consent-management flow.

Where consent is required, refusing consent does not block access to the paid service unless the relevant technology is strictly necessary for that specific service function.

BinaryBias does not currently describe an in-app cookie preference centre on this page. If a consent-management flow is implemented, this section will be updated with a clear control that allows users to change or withdraw non-essential consent.

Users can also clear cookies and local storage through their browser. Doing so may sign the user out, reset local preferences, or require the user to repeat account, subscription, or risk-disclosure steps.

Most browsers allow users to block, delete, or limit cookies and other site data. Browser controls are separate from any BinaryBias consent flow and may affect all websites or only selected websites depending on the user's browser settings.

Blocking all cookies or site storage may prevent BinaryBias from functioning correctly, including sign-in, paid access checks, realtime updates, and local interface preferences.

Storage duration depends on the purpose and provider. Session technologies may expire when the browser session ends. Authentication, subscription, security, and provider cookies may last longer where needed for account access, fraud prevention, billing, or security. Local preferences may remain until the browser deletes them, the user deletes them, or BinaryBias replaces or expires the stored value.

BinaryBias does not intentionally keep non-essential device storage for longer than needed for the stated purpose.

Third-party providers may process cookie or storage information when they provide authentication, subscription, payment, hosting, security, realtime infrastructure, or support services to BinaryBias. These providers may apply their own technical identifiers and retention periods.

BinaryBias reviews provider storage as part of ordinary service operation and updates this notice when provider storage materially changes.

This notice explains device storage technologies. The BinaryBias Privacy Notice explains how personal data is collected, used, shared, and retained more generally. A technology can be covered by this notice even if the stored information is not personal data. If cookie or storage information is linked to an identifiable user, it is also handled under the Privacy Notice.

BinaryBias may update this notice when the product, providers, technical storage, consent flow, or legal requirements change. Material changes are reflected by updating the date at the top of this page and, where required, requesting a new consent choice before using new non-essential technologies.