Cookie Policy

1. Cookies and similar technologies

Cookies are small files stored by a website in the browser. RW may also use similar technologies, including local storage, session storage, application caches and service workers, for authentication, security, language, preferences, navigation continuity and operation during poor connectivity. These technologies do not all have the same duration or purpose.

2. Current configuration

As of the last update, RW public pages and web applications use technical cookies and storage that are necessary or functional to the service. No global profiling tools, Meta Pixel, Google Analytics or cross-site advertising trackers have been identified on the public website. The first-party operational events described below are not used to follow users across third-party websites.

This technical-only configuration does not require a prior-consent banner. If non-essential technologies are enabled in the future, they will be blocked until the user makes the applicable choice and this policy will be updated.

3. Cookies used

Cookies use protections appropriate to the service, including HttpOnly, Secure in production and SameSite=Lax. The session name may only be changed through controlled server configuration.

4. Local storage in web applications

RW Suite and RW MyWatch may keep web-app session identifiers, theme, visual settings, inventory view and other preferences needed to restore the selected experience. Keys are separated by product and account where applicable. Data remains until the user clears it, logs out where applicable, or the application invalidates it after an update.

In native applications, credentials are stored in secure device storage where available; non-sensitive preferences use the application preference system.

5. Session storage

Per-tab session storage may temporarily preserve menu position and prefill data for a user-initiated flow. Prefill data is removed after it is read; other data normally ends with the tab or browser session.

6. Cache, service workers and offline operation

Applications may use browser caches and service workers to load static resources faster, present the interface during temporary outages and distribute updates consistently. Caches are versioned and may be invalidated by the application. They are not used for advertising profiling.

7. First-party operational measurement

RW may record minimised technical and product events on its own backend, such as opening a feature, request outcome, error or app version, for security, support, reliability and aggregate analysis. These events do not necessarily require a dedicated cookie and exclude full serials, documents, passwords, tokens, addresses and free-form messages. Optional analytics features remain subject to configuration and the applicable legal basis.

8. Third-party services triggered on request

The administrative WhatsApp setup module may load Meta technologies only when an authorised administrator starts that flow; they are not loaded globally on public pages. Push notifications, payment and other providers are involved only when the relevant feature is enabled. Before introducing non-essential browser technologies, RW carries out a review and obtains consent where required.

9. Managing or deleting technologies

Users can clear cookies, site data and caches through browser or device settings. Blocking rw_session prevents login and restricted areas; removing rw_locale restores the default language; clearing local storage may reset themes, preferences and offline data without deleting records stored in the RW database.

10. Updates and periodic review

RW periodically reviews cookies, SDKs and similar technologies. Introducing non-essential analytics, marketing or profiling requires an update to this policy, including classification, duration, provider and the applicable consent or objection mechanism. The review date appears above.

11. Controller and contact

The controller is PINDORO S.R.L.S. UNIPERSONALE.

For further information about personal data, see the Privacy Policy.