Cookie Policy
Last updated: 16 September 2026
This Cookie Policy explains how Rechlio by Replova Labs Private Limiteduses cookies, local storage, and similar technologies when you use our platform.
1. What Are Cookies?
Cookies are small text files stored on your device by your web browser. Local storage is a similar browser-based mechanism that stores data as key-value pairs. Both are used to remember information about your session and preferences.
2. How We Use Cookies & Local Storage
Rechlio uses browser storage for account access, preferences and first-party product analytics. Advertising measurement on public pages runs unless you turn it off, and you can do that at any time.
2.1 Essential (Required)
| Name | Type | Purpose | Duration |
|---|---|---|---|
| replov_token | Local Storage | Stores your Rechlio authentication token (JWT) to keep you signed in | Until logout |
| offline_access | Local Storage | Flags when you choose Local Test Mode (offline access) | Until reconnection |
2.2 Functional
| Name | Type | Purpose | Duration |
|---|---|---|---|
| sidebar_state | Local Storage | Remembers whether the sidebar is expanded or collapsed on mobile | Persistent |
| wa_billing_ack | Local Storage | Remembers that you dismissed the WhatsApp "add a payment method" reminder | Persistent |
| auth_redirects | Session Storage | Short-lived counter that prevents an authentication redirect loop | Cleared on sign-in / tab close |
2.3 Analytics & Tracking
First-party analytics record product events and session attribution, including the landing path and standard campaign parameters. Session storage entries rechlio_session_id and rechlio_attribution last for the browser session.
Unless you turn it off, Meta Pixel measures visits to our public website and signup page. Meta receives page URLs, browser and device information, network information such as your IP address, and advertising identifiers. Meta may set _fbp and _fbc cookies, generally for up to 90 days, subject to browser limits. This helps us measure and improve advertising on Facebook and Instagram. We do not intentionally send account fields, contact lists or message content through the Pixel. We do not send Pixel PageViews from the application dashboard or authentication callback routes.
Some of the same events are also sent to Meta from our servers rather than from your browser, using Meta’s Conversions API. This covers page views on our public pages, account registration and payment. A server-sent event carries the same identifier as the matching browser event so that Meta counts the two as one, and it carries the same categories of information described above: the page URL, your IP address, your browser’s user agent string, the _fbp and _fbc advertising identifiers where they exist, and — for registration and payment only — an irreversible hash of your email address and of your account identifier. We do not send your email address itself, your name, your contact lists or your message content.
Server-sent events follow the same choice as the Pixel: turning advertising measurement off stops both. They do not depend on the Pixel script running, so they are still sent if a browser extension, tracking protection or a network filter blocks that script — turning measurement off using Ad privacy is what stops them, and blocking the script by itself is not.
The Pixel script loads on public pages unless you have turned advertising measurement off, and it stops loading as soon as you do. Turning it off does not prevent you from using Rechlio. Your choice is stored as rechlio_ad_consent_v1 in local storage until you change it or clear browser data; if you clear it, measurement resumes until you turn it off again. Use Ad privacy on public pages to change your choice at any time. Withdrawal stops future Pixel and server-sent events; it does not erase information already received by Meta. You can clear existing cookies in your browser. See Meta’s Privacy Policy for Meta’s handling of that information.
3. Third-Party Cookies
If you choose to sign in with Google or GitHub (OAuth), those providers may set their own cookies during the authentication process, governed by their respective privacy policies. When you make a payment, our gateway Razorpay may also set cookies required to process the transaction securely.
4. Managing Cookies
You can clear local storage and cookies through your browser settings. Note that clearing the replov_token entry will sign you out and require re-authentication.
Common browser instructions:
- Chrome: Settings → Privacy and Security → Clear Browsing Data
- Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data
- Safari: Preferences → Privacy → Manage Website Data
- Edge: Settings → Privacy, Search, and Services → Clear Browsing Data
5. Changes
If we introduce new cookies or tracking mechanisms, we will update this policy and notify you through the application.
6. Contact
- Email: support@rechlio.com
- Entity: Replova Labs Private Limited (CIN: U62012PN2026PTC255232)
- Registered address: H. No. 1152, Wangdari, Shrigonda, Ahmadnagar - 413726, Maharashtra, India