Cookie Policy

Last updated: 6 November 2025. This policy explains how ScalaWorld sp. z o.o. uses cookies and similar storage on scalaworld.com. The site is informational and B2B-focused.

1. What cookies are

Cookies are small text files stored on your device. They may hold session identifiers or preferences depending on implementation. We minimise use where we control front-end code.

2. Legal bases

Strictly necessary cookies may rely on legitimate interests or performance of a service. Analytics or marketing tags, if introduced later, will require consent under ePrivacy rules.

3. Types of cookies

In the current static build we do not set named marketing or analytics cookies via ScalaWorld scripts. Hosting infrastructure or the browser may still use technical/session mechanisms as part of delivering pages.

4. localStorage consent key

The informational banner stores your choice in localStorage under cookie_consent so the message is not shown again after acceptance or dismissal. Values: accepted or dismissed. No personal data such as name or email is stored in this key.

5. Retention

We do not manage a named first-party marketing cookie list in this build. The localStorage value persists until you clear site data or we change the logic.

6. Third-party embeds

Embedded maps (e.g. OpenStreetMap) may set their own cookies per provider policies. No ad trackers are included in this static template.

7. Browser controls

You can delete or block cookies in browser settings (Chrome, Firefox, Edge, Safari). Blocking technical cookies may limit functionality.

8. Analytics

By default we do not load Google Analytics or similar tags. If added later, this policy will be updated beforehand.

9. Minimisation

We apply data minimisation and do not merge cookie identifiers with form data without a legal basis.

10. Privacy Policy

Personal data processing, including form submissions, is described in the Privacy Policy.

11. Visitors outside the EEA

If you browse from outside the EEA, local laws may apply; the site is primarily oriented to EU B2B contexts.

12. Updates

Material technology changes will be reflected here before new production code ships.

13. Withdrawal of optional consent

Optional mechanisms can be cleared via browser storage settings; legal bases other than consent (e.g. correspondence archiving) may still apply.

14. Contact

Questions: [email protected]. Include your browser type and a short description of the issue.