Last updated: 3 November 2026 ยท Applies to the Rojgar With Harsh app and website
This policy explains how Rojgar With Harsh uses cookies and similar technologies (local storage, session storage, IndexedDB and a service worker cache) on your device. We do not use advertising or tracking cookies, and we do not run third-party analytics or ad networks. The items below are needed to make the App work.
| Item | Purpose | Type |
|---|---|---|
| Sign-in data (Google Firebase Authentication) | Keeps you signed in on your phone | Strictly necessary |
| Session ID and login check marks (e.g. rwh_sid, rwh_ok) | One-phone-at-a-time rule; opens pages quickly after login | Strictly necessary |
| Cached course list (rwh_paid2) | Loads paid course data fast; refreshed about every 24 hours | Functional |
| Payment history cards and course validity on your phone | Shows your payment status and validity even when the network is slow | Functional |
| Notifications (rwh_n_โฆ) | Keeps your in-app notifications and read/unread state | Functional |
| Login safety counters | Limits wrong-password attempts and repeated account creation | Security |
| Offline PDFs (IndexedDB, encrypted) | Lets you read downloaded PDFs without internet, only inside the App | Functional (you choose to download) |
| Service worker cache | Saves the App's files for fast and offline use | Strictly necessary |
None of these is used to track you across other websites or to show ads.
When you play a video, the App may load the YouTube player, and when you open a file it may use Google Drive. Google may set its own cookies or similar technologies when its content is loaded. We do not control them; please read Google's cookie information. Our hosting and security provider, Cloudflare, may also process technical data and set security-related cookies to protect the site.
We may update this policy; the date at the top shows the latest version. Questions? Write to rwh.contact.team@gmail.com.