Store information
Cookie and Similar Technologies Policy
Effective date: 2026-10-15
INVENTORY REVIEW AND QUALIFIED LEGAL APPROVAL REQUIRED
1. Technologies used
The application uses a PHP session cookie for session-backed functions such as cart, login and CSRF state. The customer remember-me cookie is named tync_ecommerce_remember; code sets it for up to 365 days, HttpOnly and SameSite=Lax, with Secure conditional on HTTPS. The active consent decision cookie is managed by this site after a visitor chooses preferences. The inventory shown in Cookie Settings lists technologies identified from the current code and database settings; it is not a guarantee that every server, browser, hosting or provider technology has been discovered.
The storefront JavaScript uses first-party localStorage keys for wishlist, recently viewed products, recent searches and recent purchases. Their code has no expiry, so they remain until cleared by the visitor or browser. These optional convenience features are disabled unless Functional storage is accepted. The service worker uses browser Cache Storage for its configured same-origin assets. It is being restricted to safe static resources; its cache is versioned and may remain until the version changes or the visitor clears site data.
2. Categories
Strictly necessary technologies support a service the visitor requests, including session security and remembering cookie choices. Functional technologies save optional preferences such as wishlist/history and, if chosen, persistent sign-in. Analytics and Marketing categories are currently listed for future review; no active analytics or advertising pixel was found in the inspected public storefront code. New optional integrations must be registered and reviewed before activation.
3. Choices and withdrawal
Use Accept all, Reject optional, or Customize. Optional categories are off until chosen. Cookie Settings remains available in the site footer so you can change or withdraw your choice. Changes apply immediately. Clearing browser data removes the saved choice and the banner will appear again. Browser controls can also delete cookies/site data, but do not necessarily remove records held by providers.
4. Third parties and transfers
No public analytics, advertising pixel or third-party embed was identified in the inspected storefront shell. The identity, duration and transfer behavior of hosting, SMTP and any future integrations require provider confirmation. A browser-based scanner cannot see HttpOnly cookies and cannot guarantee detection of every dynamic, server-side or third-party technology.
5. Effective date and review
The consent decision is versioned and configured for a six-month validity by default. A material configuration change can require renewed consent. This inventory must be reviewed whenever scripts, providers, storage purposes or service-worker behavior changes.
Draft effective date: 2026-10-15. This draft is not legal advice and is not approved for final publication.
1. Technologies used
The application uses a PHP session cookie for session-backed functions such as cart, login and CSRF state. The customer remember-me cookie is named tync_ecommerce_remember; code sets it for up to 365 days, HttpOnly and SameSite=Lax, with Secure conditional on HTTPS. The active consent decision cookie is managed by this site after a visitor chooses preferences. The inventory shown in Cookie Settings lists technologies identified from the current code and database settings; it is not a guarantee that every server, browser, hosting or provider technology has been discovered.
The storefront JavaScript uses first-party localStorage keys for wishlist, recently viewed products, recent searches and recent purchases. Their code has no expiry, so they remain until cleared by the visitor or browser. These optional convenience features are disabled unless Functional storage is accepted. The service worker uses browser Cache Storage for its configured same-origin assets. It is being restricted to safe static resources; its cache is versioned and may remain until the version changes or the visitor clears site data.
2. Categories
Strictly necessary technologies support a service the visitor requests, including session security and remembering cookie choices. Functional technologies save optional preferences such as wishlist/history and, if chosen, persistent sign-in. Analytics and Marketing categories are currently listed for future review; no active analytics or advertising pixel was found in the inspected public storefront code. New optional integrations must be registered and reviewed before activation.
3. Choices and withdrawal
Use Accept all, Reject optional, or Customize. Optional categories are off until chosen. Cookie Settings remains available in the site footer so you can change or withdraw your choice. Changes apply immediately. Clearing browser data removes the saved choice and the banner will appear again. Browser controls can also delete cookies/site data, but do not necessarily remove records held by providers.
4. Third parties and transfers
No public analytics, advertising pixel or third-party embed was identified in the inspected storefront shell. The identity, duration and transfer behavior of hosting, SMTP and any future integrations require provider confirmation. A browser-based scanner cannot see HttpOnly cookies and cannot guarantee detection of every dynamic, server-side or third-party technology.
5. Effective date and review
The consent decision is versioned and configured for a six-month validity by default. A material configuration change can require renewed consent. This inventory must be reviewed whenever scripts, providers, storage purposes or service-worker behavior changes.
Draft effective date: 2026-10-15. This draft is not legal advice and is not approved for final publication.