Cookie Policy
What Prativani stores in your browser — which is one cookie, a handful of preferences, and no tracking at all.
1. The Short Version
Prativani sets exactly one cookie, and it exists only to keep you signed in to the dashboard. Everything else we remember — your theme, your session, a few layout preferences — is stored in your browser's local storage, which never travels to our servers on its own.
We run no analytics, advertising, or tracking cookies on this website. There is no Google Analytics tag, no advertising pixel and no retargeting script on prativani.com.
2. Cookies and Similar Technologies
Several technologies can store or read information on your device, and data-protection law treats them alike. The ones that matter here:
- Cookies — small text files a website asks your browser to store and send back on later requests.
- Local storage — a browser store that also keeps data on your device, but which the browser never attaches to a request on its own; the page has to read it and decide to use it.
- Pixels and web beacons — tiny images or tracked links embedded in a page or an email that report back when they are loaded or followed. We use these in one place only, described in section 6.
It is worth being equally clear about what we do not use anywhere in Prativani or on this website: no session-replay or screen-recording tools, no device fingerprinting, no advertising or retargeting pixels, no cross-site tracking, and no data brokers or advertising networks.
3. The One Cookie We Set
- refresh_token — issued when you sign in to app.prativani.com. It holds a long-lived credential the dashboard exchanges for a fresh session when your short-lived one expires, so you are not signed out every hour. It is HttpOnly (JavaScript cannot read it), SameSite=Lax, sent only over HTTPS in production, scoped to the single URL that renews sessions, and it expires after 30 days. Signing out deletes it.
This cookie is strictly necessary: without it there is no way to stay signed in, so it is set on the basis of providing a service you asked for, and no consent banner gates it. It is not used to profile you and it carries no advertising identifier.
4. What We Store in Your Browser Instead
This website keeps nothing on your device — no cookies and no local storage.
In the dashboard at app.prativani.com, once you sign in, we also store your current session token — the credential that authenticates each request to our API — along with your theme and a small number of layout preferences, and the browser push registration if you turn on desktop notifications.
All of it is functional: it exists to keep you signed in and to keep the interface the way you left it. None of it is shared with a third party, none of it is used for advertising, and all of it is cleared when you clear the site's data.
5. The Chat Widget on Other Websites
Prativani's chat widget is installed by our customers on their own websites. When you use it, the widget stores the following in your browser on that website's origin, not ours:
- A device identifier — a random value that lets a returning visitor pick up the same conversation and lets an agent see the history rather than starting from nothing. It is not shared between different customers' websites.
- Details you typed — the name and email you entered in the chat form, so you do not have to type them again.
- A consent flag — where the business has switched on a consent notice, whether you accepted it.
- A cached copy of the widget's appearance settings, so it renders quickly.
Alongside that, the widget records the pages you view on that site and derives an approximate location from your IP address, so the business can see the context of your question. The business that installed the widget decides what is collected and is the controller of that data — including whether a consent notice is shown before your details are recorded. Direct any request about it to them; our role is explained in our Privacy Policy.
6. Email Tracking Pixels
Prativani lets businesses send email campaigns. Those campaigns carry a 1×1 transparent image and rewritten links, served by us, so the sender can see in their reports that a message was opened or a link was clicked. No cookie is set and nothing is stored on your device; the request itself is what is recorded.
That tracking belongs to the business that sent the campaign, not to us — they decide to send it and they see the results. Most email clients let you block remote images, which stops open tracking, and every campaign carries an unsubscribe link.
Two things we deliberately do not track: replies in a conversation — support email sent through Prativani goes out with open and click tracking switched off, on every send without exception — and our own mail to you, whether that is a notification, a product update or a password reset.
7. Third-Party Cookies
We do not place third-party advertising or analytics cookies. Two third parties can set their own storage in the course of doing a job you asked for: our payment provider, when you open the payment or billing screens, and Google reCAPTCHA, when it verifies a form submission is not automated. Both are governed by their own privacy policies.
8. Managing What Is Stored
You can clear or block cookies and site data through your browser settings, usually under Privacy or Site Settings. Because everything we store is functional rather than optional, clearing it has visible consequences: you will be signed out of the dashboard, your theme and layout preferences reset to their defaults, and an open chat with a business will no longer be recognised as yours.
We do not show a cookie consent banner, because we set no cookies that would require one. If that ever changes, we will ask for consent before placing them and update this page first.
Do Not Track and Global Privacy Control. These browser signals tell a site not to track you across services or sell your data. We honour them by default and by design: we run no cross-site tracking to switch off, and we neither sell nor share personal information, so there is nothing for the signal to change.
9. Updates
We will update this Cookie Policy if what we store changes. The effective date at the bottom of this page indicates the current version.
10. Questions
Anything about this policy, or about data we hold: [email protected]. How the rest of your data is handled is set out in our Privacy Policy.
Effective Date: September 26, 2026