1. Applicability and Scope
§1.1This Cookie Policy (the “Policy”) is a supplemental term governing the use of cookies, local storage, pixels, and similar technologies (“Cookies”) by Eto Rides (“Provider”, “Platform”) on its digital properties.
1.2By accessing or using the website, the user (“User”, “Purchaser of Services”) acknowledges that certain “Strictly Necessary” Cookies are required for core functionality, security, and service delivery.
1.3This Policy is intended to support lawful operation and security readiness, including practices oriented toward CERT-In–aligned incident response and auditability where applicable.
Effective Date: ___ / ___ / 2026 (as published in the finalized policy document)
Related pages: Terms of Service, Privacy Policy, Contact, Grievance Redressal.
2. Definitions of Digital Identifiers
§2.1“Cookies” means small text files or data fragments stored on a User’s device to identify session state, preferences, or technical telemetry.
2.2“First-Party Cookies” means identifiers deployed directly by the Provider’s domain.
2.3“Third-Party Cookies” means identifiers deployed by external service providers used by the Platform (including Google and Vercel).
2.4“Consent Banner / Settings” means any on-site consent control (where enabled) used to accept or reject non-essential Cookies.
3. Classification of Cookies
§Cookies used by the Platform are generally classified as follows.
| Category | Legal / Functional Basis | Impact of Disabling |
|---|---|---|
| Strictly Necessary | Essential operations (session management, load balancing, core security). | Critical: may render the service unusable or insecure. |
| Preferences | User interface choices (language, region, interface settings) where enabled. | Minor: defaults may apply; some convenience features may not work. |
| Analytics | Performance monitoring and reliability insights via analytics tooling (where enabled). | None to core: service should remain usable; measurement may be reduced. |
| Security & Compliance | Fraud/abuse detection patterns, incident response readiness, and audit controls. | Moderate: additional verification or reduced security signals may occur. |
Actual Cookies and identifiers may vary by environment (dev/staging/production), features enabled, and provider configuration.
4. Third-Party Provider Integration
§4.1Vercel: Hosting, edge delivery, and operational telemetry required for reliability and performance.
4.2Google: Analytics/measurement and performance insights where enabled, subject to configuration and user controls.
4.3CERT-In: Security/compliance alignment: incident readiness and audit-supporting practices (not a consumer tracking service).
4.4Third-party providers may process limited technical data under their own policies; the Platform configures providers to the extent supported and lawful.
Third-party features may be enabled/disabled based on environment and consent settings where applicable.
5. User Control and Consent Mechanisms
§5.1Browser-level controls: Users may configure their browser/device to reject, delete, or limit Cookies.
5.2Limitation of performance: If a User blocks Strictly Necessary Cookies, core site functions may fail; the Provider is not responsible for nonconforming performance caused by such blocking.
5.3Consent validity: Where a consent banner/settings is shown, any consent for non-essential Cookies remains valid until changed by the User or until the applicable consent record expires per configuration.
Practical controls
- Use browser settings to block or delete Cookies.
- Use consent settings (where shown) to accept/reject non-essential categories.
- Device-level privacy controls may reduce certain tracking/telemetry signals.
6. Data Retention, Technical Logging, and Deletion
§6.1Session Cookies terminate when the browser session ends.
6.2Persistent Cookies remain for a configured period or until deleted by the User.
6.3Analytics retention (where enabled) is governed by tool configuration and may vary over time.
6.4Mandatory technical logs: For cybersecurity readiness, certain system logs (which may include session identifiers, timestamps, IP address, and transaction metadata) may be retained for the minimum period required under applicable directions and policies.
6.5Where CERT-In–aligned logging is required, relevant logs are retained for at least 180 days and stored within India where applicable to the direction’s scope and operational architecture.
Retention is limited to the purpose of security, compliance, and incident response, and is not used for marketing without separate consent where required.
7. Rights, Grievance, and Governing Law
§7.1Withdrawal/updates: Users may change cookie preferences through browser controls and on-site settings (where available). The Provider may update this Policy to reflect technology, legal, or operational changes.
7.2Cross-border processing: Some providers may process limited technical data outside India depending on infrastructure. The Provider aims to implement reasonable safeguards and comply with applicable law and government notifications.
7.3Governing law: This Policy is governed by the laws of India. Disputes, if any, are subject to the jurisdiction of competent courts at Bankura, West Bengal unless otherwise required by applicable law.
7.4Grievance redressal: Cookie/privacy-related concerns should be raised via the Grievance Redressal page and official support channels.
Contact
For questions about this Cookie Policy, contact Eto Rides.
- Support Email: support@etorides.com
- Business Email: business@etorides.com
- Phone / WhatsApp: +91 93393 73154 (or WhatsApp)
Address: Holding No. 276/B/I, Lokepur Kenduadihi, Near Sonar Tori Hotel & Restaurant, Lokepur, Bankura, West Bengal – 722102, India
