Cookie Policy

1. Summary

We do not currently use non-essential analytics or advertising cookies (no Google Analytics, Meta Pixel, or similar trackers were found in the Wasl Cart marketing or application front ends at the time this policy was written). Because we only use essential cookies on the application, we do not show an “Accept all” marketing consent banner that would imply optional analytics exist.

2. Marketing website (waslcart.online)

The marketing site is primarily static PHP pages. It does not set first-party analytics cookies. It may load fonts from Google Fonts (third-party network requests) for typography; those requests are controlled by Google and are not used by Wasl Cart as an analytics product integration.

3. SaaS application cookies (app.waslcart.online)

The Laravel-based application uses essential cookies required for security and signed-in operation, including typically:

• Session cookie (name derived from the application name, e.g. a *-session cookie) — maintains your logged-in session.
• XSRF-TOKEN — helps protect forms and state-changing requests against cross-site request forgery (CSRF).

These cookies are necessary for the service to function for authenticated users. They are not used to advertise products to you across third-party sites.

API clients may also use Sanctum bearer tokens stored by the client application; those tokens are not browser cookies set by the marketing site.

4. Why we use them

Essential cookies authenticate users, keep sessions secure, and prevent CSRF attacks. Without them, login and dashboard features cannot operate reliably.

5. Managing cookies (Cookie settings)

Because only essential cookies are used on the app, there is no optional analytics category to toggle off while remaining logged in. You can delete cookies in your browser settings; doing so will sign you out of the Wasl Cart app. Blocking essential cookies will break login and dashboard use.

If we add non-essential analytics in the future, we will update this policy and, where required, implement a consent mechanism before setting those cookies.

6. Changes

We may update this Cookie Policy when our cookie practices change. The “Last updated” date at the top will change accordingly. See also our Privacy Policy.

Internal note for operators: do not add analytics scripts without updating this policy and implementing an appropriate consent banner.