Cookies Policy
Dehhani Ltd — Retsu™
Last updated: 17 July 2026
This policy explains how Retsu™ uses cookies and similar technologies, including local storage, session storage, service workers and cache storage. These technologies are covered by the Privacy and Electronic Communications Regulations (PECR) when they store information on, or access information from, a user's device.
1. Our approach
Retsu™ does not deliberately use advertising or cross-site behavioural-tracking cookies, and we do not currently deploy an analytics cookie suite. Core authentication, security and payment technologies fall within the strictly-necessary exception; user-interface preferences fall within the appearance exception; and other storage is used to provide functionality the user has requested. We still explain these technologies below even where PECR does not require consent. Optional third-party content must be held back for consent if its storage does not qualify for an exception.
If we introduce non-essential analytics, advertising or other optional device storage, it will be disabled until the user has received clear information and given any consent required by PECR. Refusing optional storage will not prevent access to the core service.
Separately from cookies, our servers generate operational and diagnostic telemetry (for example performance metrics and error or exception traces, via Microsoft Azure Application Insights / Azure Monitor) to keep the service secure and reliable. This telemetry is generated and processed server-side; it does not store or read information on your device and so falls outside the scope of this policy. It is described in our Privacy Policy and GDPR notice.
2. Cookies and provider technologies
| Name / provider | Purpose | When used | Duration |
|---|---|---|---|
connect.sidRetsu™ |
A signed, opaque identifier for the server-side session. It supports authentication, account security, permissions and requested settings. The cookie does not contain the underlying account data. | When the platform needs a session, which can occur before sign-in for security, registration, CAPTCHA, OAuth or embedded-app state. | Browser session. The corresponding server-side session record may remain for up to 30 days. |
_GRECAPTCHAGoogle reCAPTCHA |
Bot, abuse and fraud prevention. | On registration or another page where reCAPTCHA is requested. | Persistent and controlled by Google. Google may use additional storage under its own terms. |
__stripe_mid, __stripe_sid and related Stripe storage |
Payment processing and fraud prevention. | Only when a user opens the subscription or payment experience that loads Stripe. | Stripe lists approximately one year for __stripe_mid and 30 minutes for __stripe_sid; other payment storage depends on the selected Stripe feature. |
| Google Maps content, address geocoding and provider storage | Displays collection and delivery addresses and, in Client Map mode, sends saved client addresses to Google's browser geocoder so clients can be placed on an interactive map. | On applicable public inbound/client portal pages when an address map is available, or on the authenticated Clients page only after a user selects Map mode. Public map iframes are lazy-loaded as they approach the visible page. | Retsu™ keeps returned coordinates only in current-page memory and does not persist them in browser storage. Google-controlled session or persistent storage may be used; the exact items and duration depend on Google's current service configuration. |
The production session cookie is marked Secure and HttpOnly and uses SameSite=None so authenticated sessions can work in supported embedded commerce contexts. Stripe and Google may act as independent controllers for relevant provider processing; see their privacy, cookie and service information before using those features.
3. First-party browser storage
| Technology | Examples and purpose | Duration |
|---|---|---|
| Local storage | Theme and interface preferences; filters, panel sizes, scanner/completion state and editor/layout settings; Retsu™ Sheets or ProCut workspace settings; and Eris conversation, memory, workflow and feedback-interface state. Some saved workspaces or histories may contain data entered by the user. | Until the preference or conversation is reset, the browser data is cleared, or the application replaces an old value. |
| Session storage | Temporary navigation state, device-list cache and embedded Shopify state such as the shop, host and short-lived identity token. | Normally until the relevant browser tab or session is closed. |
| Service worker and Cache Storage | Same-origin static assets and an offline application shell, used to improve reliability and loading performance. | Until the cache version is replaced, the service worker is removed or the browser data is cleared. |
Currency, language, role and similar account settings may also be held in the server-side session associated with connect.sid. Clearing an Eris conversation in the browser clears its local copy only; server-side assistant logs and feedback are covered by our GDPR and Privacy notices.
4. Integrations, push and external resources
Shopify App Bridge may be loaded in an embedded Shopify context and Shopify may use its own session or device technologies. Retsu™ also stores the temporary Shopify values described above in session storage. Other connected marketplaces open or communicate with the provider selected by the account holder; provider storage is governed by the relevant provider's notice.
If browser notifications are available and a user opts in, the browser creates a push subscription and uses a service worker and the browser vendor's push infrastructure. The subscription is stored server-side so the requested notification can be delivered; it is not an advertising cookie and can be disabled through browser notification settings.
Some pages request fonts, icons or scripts from third-party content-delivery networks. Those providers receive ordinary request data such as IP address, user-agent and referring page. We do not use those requests for Retsu™ advertising or analytics. Provider-controlled technologies remain subject to the provider's own notice and to our obligation not to deploy non-essential storage without any required consent.
5. Email-open monitoring is not a cookie
When an account holder enables open monitoring for a batch email, the emailed link may contain a unique broadcast token. Opening that link can record the recipient/broadcast reference, opening time, browser user-agent and a one-way hash of the IP address. This is link-based server logging rather than a cookie or browser-storage technology. The account holder must have a lawful basis and give recipients appropriate information. The GDPR notice explains the associated data processing.
6. Managing storage
Browser settings can view or delete cookies, site data, local/session storage, cached data, service workers and notification permissions. Blocking connect.sid will prevent sign-in and other session-dependent features. Clearing local storage removes saved preferences and may remove locally held Eris history or workspace state. Clearing session storage can interrupt an embedded Shopify session.
- Google Chrome cookie controls
- Apple Safari cookie controls
- Mozilla Firefox site-data controls
- Microsoft Edge cookie controls
There is no universal “Do Not Track” (DNT) standard, so Retsu™ does not currently make a separate technical response to DNT signals. We do not deliberately deploy advertising or analytics cookies, and DNT does not change the operation of the necessary technologies described above.
7. Provider information, changes and contact
- Google reCAPTCHA cookie information
- Google Maps/Google Earth Additional Terms of Service
- Google cookie information
- Google Privacy Policy
- Stripe cookie information
- Stripe Privacy Policy
We review this policy when our platform or providers change. Material changes will be highlighted in the service or communicated to account holders. Questions can be sent to support@retsu.uk or by post to Dehhani Ltd, 124 City Road, London, England, EC1V 2NX.