Cookie Policy
We use cookies sparingly. No advertising, no pixels. Four categories: strictly necessary, functional, analytics, security.
- Last reviewed ·
- 26 April 2026
- Effective ·
- 26 April 2026
1. What cookies are
Cookies are small text files that a website stores in your browser. They are used to make sites work, remember preferences, and measure what is helpful. SellerSaarthi uses cookies sparingly and does not use advertising cookies.
2. Cookies we use, by category
Strictly necessary (always on)
Required to run the site. Cannot be disabled. Examples: session management, CSRF protection, load balancing.
Functional (preferences, language)
Remember your chosen UI language, cookie-consent decision, and simple UI preferences. Opt-in.
Analytics
Vercel Web Analytics counts page views and the buttons pressed on this site. It sets no cookie and stores no IP address or identifier of yours; what it holds is a daily hash it cannot reverse. The product (app.sellersaarthi.com) uses no analytics service.
Security (anti-CSRF)
Used to protect forms from cross-site request forgery. Strictly necessary.
3. Third-party cookies
| Service | Purpose | Controlled by |
|---|---|---|
| Clerk | Authentication session | Clerk Inc. |
We do not embed advertising tags, Meta Pixel, Google Ads conversion tags, or similar. If this changes, we will update this policy and re-ask for consent.
4. How to control cookies
The only cookies we set are the ones the site needs to run, so there is nothing to opt in to. You may also block cookies via browser settings; some functionality may stop working.
5. Changes, effective date, contact
We will update this page when we add or remove cookie uses. For questions: privacy@sellersaarthi.com.
Effective date: 26 April 2026.
Revised 13 October 2026: removed PostHog and the analytics category. We do not use an analytics service, and no data has been sent to one.
Revised 17 October 2026: corrected the Analytics section. This site has carried Vercel Web Analytics since June 2026; the 13 October revision said we used no analytics service, which was wrong for the site. It sets no cookie, so the cookie tables above were and are correct.