Findoly Provider portal Provider login
Findoly Solutions LLP

Cookie and Storage Notice

Details of essential authentication cookies, security tokens and browser-storage preferences used by the Provider Portal.

Effective and last updated: 30 July 2026

On this page
  1. Purpose of this notice
  2. What cookies and browser storage are
  3. Provider authentication cookie
  4. CSRF security cookie
  5. Local storage
  6. Session storage
  7. Third-party checkout and external services
  8. Browser controls and consequences
  9. Retention and updates
  10. Questions

1. Purpose of this notice

This notice explains the cookies and browser-storage technologies used by the Findoly Provider Portal. It should be read with the Privacy Policy. The Portal currently uses these technologies mainly for authentication, security and interface preferences, not for third-party behavioural advertising.

Back to contents

2. What cookies and browser storage are

Cookies are small values stored by a browser and sent with requests to the relevant website. Local storage keeps data in the browser until removed. Session storage normally lasts for the current browser tab or session. These technologies do not by themselves read unrelated files from your device.

Back to contents

3. Provider authentication cookie

After successful OTP verification, the Portal sets a signed provider authentication cookie. It identifies the authorised Provider session. The cookie is HTTP-only so ordinary browser scripts cannot read it. In production it is transmitted only over HTTPS and uses same-site and priority controls. Its configured duration is generally based on the account session setting, and logout clears it.

Back to contents

4. CSRF security cookie

The Portal sets a separate cross-site request forgery token cookie. Browser code reads this random token and sends it with state-changing requests so the server can reject forged requests. In production the cookie is secure, uses strict same-site protection and normally expires after approximately one day.

Back to contents

5. Local storage

The lead marketplace may store the Provider’s selected list or card view preference in local storage. This lets the browser remember the chosen presentation. The theme bootstrap removes an older theme preference so the approved Findoly theme remains consistent.

Local storage is not used by the current Portal code to store OTPs, payment credentials or full customer records.

Back to contents

6. Session storage

The dashboard may use session storage to remember that the Provider dismissed a pending-outcome reminder during the current browser session. This prevents the same reminder reopening repeatedly in that session.

Back to contents

7. Third-party checkout and external services

Razorpay checkout is loaded on payment-enabled pages and may use its own cookies or storage under its policies to provide secure payment functionality and fraud prevention. Opening WhatsApp or another external link transfers you to that service, which may use its own technologies.

Findoly does not control third-party cookies set on third-party domains.

Back to contents

8. Browser controls and consequences

You can clear or block cookies and storage through browser settings. Blocking essential cookies will prevent login, session security or payment-related functions from operating correctly. Clearing local or session storage may reset interface preferences and reminders but should not delete server-side transaction records.

Back to contents

9. Retention and updates

Cookie duration is controlled by the relevant configuration and browser behaviour. Local storage remains until cleared by the user or application; session storage expires according to browser rules. We may update this notice if technologies or vendors change.

Back to contents

10. Questions

Send cookie or storage questions to support@findoly.com.

Back to contents
Policies and support
Terms Privacy Refund policy Digital delivery Lead data use Marketplace disclaimer Cookies Intellectual property Grievances Contact Help & support
© 2026 Findoly Solutions LLP support@findoly.com