Cookie Policy

1. Introduction

This Cookie Policy explains how Ecosys360 (“we”, “us”) uses cookies and similar technologies when you use Ecosys360 Retail & Ops Suite and related websites (the “Service”).

It should be read with our Privacy Policy, which describes how we process personal data more broadly.

Questions: app.flakescapital@gmail.com.

2. What are cookies and similar technologies?

Cookies are small text files placed on your device by a website or app. They often include a unique identifier and can be “session” (deleted when you close the browser) or “persistent” (remaining until they expire or you delete them).

We also use similar technologies such as local storage, session storage, and in-memory tokens. These may store preferences, authentication state, or draft data needed for the Service to function. For simplicity, this policy refers to all of these as “cookies” unless the distinction matters.

3. Why we use cookies

We use cookies to operate the Service securely and reliably, remember settings you choose, and keep certain draft work on your device until you complete or clear it. Categories we use include:

• Strictly necessary — required for login sessions, CSRF and security protections, load balancing, and core navigation; the Service cannot function properly without these
• Functionality / preferences — for example theme (light or dark) and similar UI settings you choose
• Operational device storage — for example a POS cart draft or form drafts stored locally until checkout, save, or clear

4. Cookies and storage we typically use

Exact names may change as we improve the product. Typical uses include:

• Authentication and session cookies or tokens — to recognise you after you sign in and keep your session secure
• Security-related cookies — to help prevent cross-site request forgery and abuse
• Preference keys in local storage — such as colour theme
• Module-specific drafts in local storage — such as unsaved POS cart lines on the device you are using

5. First-party vs third-party

Most cookies and storage used by Ecosys360 are first-party (set by our domains) for authentication and product functionality.

If you use payment providers or other embedded third-party services, those providers may set their own cookies subject to their policies. We do not control third-party cookies.

6. Analytics and marketing

We do not currently rely on third-party advertising cookies for the core application experience.

If we introduce analytics, measurement, or marketing technologies that are not strictly necessary, we will update this Cookie Policy and, where required by law, request your consent before setting those cookies.

7. Legal bases

Where ePrivacy and GDPR rules apply, strictly necessary cookies are used because they are required to provide a service you request (login and core app features).

Non-essential cookies, if introduced later, will be used on the basis of consent where consent is required. You can withdraw consent by changing browser settings or any in-product controls we provide.

8. How long cookies last

Session cookies expire when you end your browser session or sign out (subject to how your browser handles tabs and restores sessions).

Persistent cookies and local storage items remain until they expire, you clear site data, or the application overwrites or removes them. Draft POS or form data on a device may persist until cleared so you do not lose work mid-shift.

9. Managing and deleting cookies

You can control cookies through your browser settings — for example blocking all cookies, blocking third-party cookies, or deleting existing cookies and site data. Steps vary by browser (Chrome, Safari, Firefox, Edge, and others).

You can also clear local storage for our site via browser developer tools or “clear site data” options.

Important: blocking or deleting strictly necessary cookies may prevent you from signing in, staying signed in, or using POS and other core features. Preference cookies, if blocked, may reset theme or similar settings on each visit.

If you use Ecosys360 on a shared device, sign out when finished and avoid leaving draft sales data on the device.

10. Do Not Track

Some browsers offer a “Do Not Track” (DNT) signal. Because there is no consistent industry standard for responding to DNT, our Service may not alter behaviour solely based on DNT signals. We will update this policy if that changes.

11. Changes

We may update this Cookie Policy when our practices or technologies change. The “Last updated” date will reflect revisions. Material changes may also be noted in the Privacy Policy or in-product notices.

Last updated: 29 July 2026.

12. Contact

For questions about cookies or this policy, contact app.flakescapital@gmail.com.