Cookie Policy

Effective date: 2026-07-09 Last updated: 2026-07-09

1. Introduction

This Cookie Policy explains how Alphaservus Consulting Services Ltd., trading as "tradesense technologies" ("Tradesense", "we", "us") uses cookies and similar technologies on the Tradesense service at app.tradesense.tech (the "Service"). It should be read together with our Privacy Policy. This Policy is drafted with reference to the EU ePrivacy Directive and the GDPR/UK GDPR.

2. What Are Cookies?

Cookies are small text files that a website stores on your device (computer, phone, or tablet) when you visit. They are widely used to make websites work, or work more efficiently, and to provide information to the site's operators. Similar technologies include local storage, session storage, and pixels; this Policy uses "cookies" to refer to all of them.

Cookies may be set by us ("first-party cookies") or by third parties whose services we use ("third-party cookies"). They may be "session cookies" (deleted when you close your browser) or "persistent cookies" (remaining until they expire or you delete them).

3. How We Use Cookies

We use cookies in the following categories:

3.1 Strictly necessary

These cookies are essential for the Service to function and cannot be switched off. They are usually set only in response to actions you take (such as logging in or setting your preferences). Examples:

• Authentication session token — a JSON Web Token issued by our authentication system and stored in an HTTP-only cookie so that you stay logged in across pages.
• CSRF protection — a token used to protect against cross-site request forgery, where applicable.
• UI preferences — small first-party cookies or local-storage entries used to remember your theme (light/dark) and similar interface choices.

3.2 Functional

These cookies enable enhanced functionality and personalisation. If you disable them, some parts of the Service may not work as expected. Examples:

• Language preference.
• Saved layout preferences on your dashboard.

3.3 Analytics

We do not use third-party analytics cookies during the beta phase. Aggregated usage insights are derived from server-side event logs rather than from cookies set in your browser.

No web analytics, tag manager, or session-replay tools are currently used during the beta phase. If Tradesense introduces any such tool later, this Cookie Policy will be updated and, where required, additional consent will be sought via the cookie banner.

3.4 Marketing

We do not use marketing or advertising cookies.

3.5 Third-party cookies

Sentry, which we use for error monitoring, may in some configurations set a cookie or local-storage entry to help correlate error events. We minimise such data and configure Sentry to avoid capturing unnecessary personal information. See our Privacy Policy for more on third-party processors.

4. Managing Your Cookies

When you first visit the Service, a consent banner will inform you of the cookies we use and ask you to accept or reject non-essential cookies where applicable. Strictly necessary cookies do not require consent. Your choice is remembered for subsequent visits and may be changed at any time via the cookie-preferences link in the footer of the Service.

You can also control cookies through your browser settings. Most browsers allow you to block or delete cookies; instructions are typically available in the browser's help menu. Blocking strictly necessary cookies will prevent you from logging in or using core features.

5. Changes to This Policy

We may update this Policy from time to time to reflect changes to the cookies we use or to legal requirements. The "Last updated" date at the top indicates when the Policy was most recently revised. Material changes will be notified via an in-app banner.

6. Contact

Questions about this Policy may be sent to support@tradesense.tech.

NOTE — Placeholders to fill in

• Alphaservus Consulting Services Ltd. — registered legal name of the Tradesense entity
• support@tradesense.tech — e.g., legal@tradesense.tech
• 2026-07-09 — publication date of this Policy

NOTE — Open questions flagged in the draft

1. Confirm whether any analytics tool will be added during or after beta (Section 3.3) and update the cookie table accordingly.
2. Verify whether Sentry's current configuration actually sets a cookie/local-storage entry (Section 3.5); refine the wording once confirmed.