Cookies, and the things that are not cookies
A cookie is a small file a site asks your browser to keep and send back on the next request. PrakWay also uses local storage, which stays in your browser and is never sent to a server. Both are covered here, because from where you sit the distinction hardly matters.
We use as few of these as the product can work with. There is no consent banner because there is nothing on this page that would need one: no advertising, no analytics profile, and no cross-site tracking.
What we store
This is the complete list.
- Session cookie — signs you in and keeps you signed in. It is HTTP-only, so page scripts cannot read it. Strictly necessary; blocking it means you cannot sign in.
- Refresh token cookie — lets your session continue without asking for your password again. It rotates on each use, so a stolen one can be detected and the whole family revoked. Strictly necessary.
- Cross-site request protection — a value checked on requests that change something, so that another site cannot act as you. Strictly necessary.
- Language preference — remembers whether you read PrakWay in English, Hindi or Telugu, so you do not have to switch on every visit.
- Theme preference — stored in local storage rather than a cookie, under the key pw-theme. It remembers whether you chose light, dark or system, is read before the page paints so you never see a flash of the wrong background, and never leaves your browser.
- Rate limiting and abuse prevention — short-lived records held on our servers, keyed to your address and session, used to stop credential stuffing and scraping. Nothing is stored in your browser for this.
What we do not put in your browser
This is the list of what is absent, and we would like to keep it that way.
No advertising cookies, no retargeting, no conversion pixels, no social media trackers, and nothing sold or shared with an advertising network.
No cross-site profile of what you browse. Product usage is measured as aggregate counts that are not tied to an advertising identity.
Third parties that see a request
Two third parties are involved in loading or paying for the product. Both are named here rather than hidden.
- Google Fonts — the typefaces, including the Devanagari and Telugu faces that the Hindi and Telugu editions need, load from Google font servers. That request tells Google your address and browser. Google states that it sets no cookies for font requests.
- Razorpay — when you open the checkout to pay, Razorpay sets its own cookies to run and secure the payment. Those are governed by Razorpay own privacy policy, and they load only on the checkout, never on the rest of the site.
How to control them
Nothing here needs our permission to remove. Everything is under your browser controls.
- Every browser lets you view, block and delete cookies and site data, usually under its privacy settings. Deleting PrakWay cookies signs you out; nothing else is lost.
- Blocking cookies for PrakWay entirely means sign-in cannot work, because the session is the cookie. The public pages — roles, companies, profiles and these policies — still work.
- Clearing local storage resets your theme choice to follow your system setting. Nothing else is kept there.
- You can sign out a session from Settings, which revokes the refresh token family on the server rather than only clearing the cookie on this device.
Changes
If we ever add something that tracks you across sites, we will ask for your consent before it loads rather than after, and this page and its version string will change first.
