Cookies on rakt.org and in RAKT HMS.
What is set, why, for how long, and how to say no. The marketing site measures how people find us; the signed-in application does not.
Version 1.0 · Effective 6 September 2026
This Cookie Policy explains the cookies and similar technologies used by RAKT INNOVATIONS (OPC) PVT. LTD. on the rakt.org website and inside the RAKT HMS application at app.rakt.org, and how you can control them. It supplements our Privacy Policy.
The marketing website measures visits only after you allow optional analytics. Google measurement scripts, advertising tags and session-recording tools are not loaded in the signed-in application. With your analytics permission, the application can send a small set of account milestones through the RAKT server: signup, completed setup and a first completed visit. These events contain an anonymous browser identifier and the milestone name, not patient details, clinical records, organisation names or record URLs.
1. What these technologies are
A cookie is a small text file that a site stores on your device and reads back on later visits. Related technologies do similar jobs: local storage and session storage keep values in the browser, and pixels or tags are small files or scripts loaded from a page to record that something happened. We use the word “cookies” below to cover all of them.
2. Cookies in the RAKT HMS application
Session and security cookies are necessary for the signed-in application to work. If you allow optional analytics, a shared consent cookie and anonymous browser identifier also let the RAKT server associate account milestones with website visits. Declining optional analytics does not prevent you from using the application.
| Name | Purpose | Retention |
|---|---|---|
| sessionid | Keeps you signed in and links your browser to your authenticated session. Without it every page would ask you to log in again. | Session, or until sign-out or expiry |
| csrftoken | Security. Proves that a form submission came from a page we served, which prevents cross-site request forgery. | Up to 1 year |
| Browser storage for interface preferences | Remembers display choices in your browser. Stored on your device and not transmitted to us. | Until cleared, or for the browser session |
Sign-in and sign-up pages may load Google reCAPTCHA to distinguish people from automated abuse; it sets _GRECAPTCHA and processes your IP address and interaction signals. It is treated as strictly necessary. No measurement tag is present once you are inside the application.
3. Cookies on the rakt.org website
3.1 Strictly necessary. WordPress sets cookies required to serve pages and to keep a logged-in editor session working. These are always active.
3.2 Optional analytics. Google Analytics 4 loads on rakt.org only after you choose Allow analytics. Before that choice, and when you decline, this implementation does not load the Google tag or send cookieless measurement pings. Advertising storage and advertising personalisation remain disabled. The website measures page visits, signup links, demo enquiries and report downloads. Account milestones are sent through the RAKT server only with the same permission.
| Provider and cookies | Purpose | Retention |
|---|---|---|
Google Analytics 4. Cookies beginning _ga are set after permission and configured with a six-month lifetime. | Aggregate measurement of how many people visit, which pages they read, and how they arrived, so we can tell which content is useful. | Up to 2 years |
| No Google Ads measurement tag is included in the rakt.org HMS implementation. | Recording whether a visit that came from one of our advertisements resulted in an enquiry. | Up to 90 days |
3.3 Your consent choice. The cookie rakt_hms_analytics records your choice for six months. If you allow analytics, rakt_hms_client stores an anonymous random browser identifier for six months. These cookies are shared between rakt.org and app.rakt.org. They do not contain your name, email or patient details.
4. What we do not do
We do not load analytics, advertising or social-media tracking pixels in the application. We do not sell data collected through cookies, and we do not use patient records for advertising. We do not use cookies to build profiles of patients.
5. How to control cookies
5.1 Through the controls. Choose Allow analytics or Only essential in the banner. Use Analytics preferences in the website footer or the app’s Getting started screen to change your choice. Declining stops milestone measurement and removes this implementation’s analytics identifier cookies. Global Privacy Control is also respected.
5.2 In your browser. Every major browser lets you view, block and delete cookies, and can be set to reject third-party cookies. Blocking strictly necessary cookies will prevent you from signing in to the application. Your browser’s help pages explain the settings for your specific version.
5.3 Google opt-out. Google provides its own browser add-on to prevent Google Analytics measurement across all sites.
6. If you are a patient
The application is used by hospital, laboratory and pharmacy staff. If you have received a link from a hospital to view your own report or to sign in to the patient portal, those pages use only the strictly necessary cookies in Section 2. Questions about your records should go to the hospital that holds them, as explained in our Privacy Policy.
7. Changes
We will update this page when the technologies we use change. Each version carries a version number and effective date at the top. Where a change introduces a new category requiring consent, we will ask for consent again rather than rely on an earlier choice.
Contact
Grievance Officer
RAKT INNOVATIONS (OPC) PVT. LTD.
AN-4D, AN Block, Shalimar Bagh, Delhi 110088, India
CIN: U72900DL2020OPC360414 · GSTIN: 07AAKCR0304B1Z0
Phone: +91 70427 21037, +91 99539 94941
Email: support@rakt.in