Cookies & Tracking Policy
This policy details how Pharmogram utilizes cookies and local browser storage strictly for authenticated sessions, security verification, and performance reliability. You maintain full authority to manage or disable optional cookies.
Last Updated: 15 December 2024
See Privacy Policy →
Tracking Architecture
Pharmogram Privacy Controls
ZERO MONETIZATION
Strictly Essential First
Session verification, CSRF security & encrypted cart state management
Zero Data Monetization
We never sell, broker, or auction personal health browsing records
Granular User Authority
Full browser-level controls to delete, inspect, or block optional trackers
DPDP Act 2023 Aligned
Operating strictly under Indian statutory digital privacy mandates
100% Transparent Telemetry
ISO 27001 Certified
Clear, practical explanation
This summary outlines why cookies exist and how tracking technologies are purposefully deployed across Pharmogram’s secure healthcare ecosystem.
Essential + security
Some cookies are required for safe operation and authenticated session integrity.
Performance analytics
Aggregated telemetry helps diagnose latency, improve stability, and streamline UX.
Preferences
Remember client-side settings, location presets, and display choices for convenience.
Minimal & purposeful
We minimize telemetry footprints and reject unnecessary cross-domain trackers.
No data selling
We do not monetize, rent, or sell telemetry data to third-party ad exchanges or brokers.
Support-friendly
Session diagnostics facilitate real-time customer care and order resolution tracking.
Types of cookies we may use
Below is the comprehensive operational taxonomy of cookie classifications deployed across Pharmogram. Precise identifiers reflect your active feature set.
Detect anomalous traffic patterns, brute-force intrusions, and abusive behavior
Protect user and chemist accounts from unauthorized cross-site token hijacking
Mitigate automated bot abuse and replay attacks across critical workflows
Governance Rationale
Security cookies safeguard users, clinical data channels, and internal infrastructure from threat actors.
Measure aggregate route performance, network latency, and interface load times
Identify feature usage trends through anonymized, privacy-first telemetry
Improve system reliability, layout responsiveness, and accessibility barriers
Governance Rationale
Analytics data is purely aggregated to improve platform performance; it is never used to build behavioral ad profiles.
Remember interface choices (such as theme modes and localized display units)
Retain user-selected preferences between browser reloads for effortless navigation
Reduce redundant form inputs and streamline repetitive checkout interactions
Governance Rationale
Preference cookies are non-essential and serve strictly to heighten convenience and personalized usability.
Facilitate transactional alert banners and critical system outage notices
Prevent duplicate modal popups, redundant alerts, and repeated confirmation prompts
Preserve real-time notification states across multi-tab customer support sessions
Governance Rationale
These trackers are strictly bounded to operational messaging and do not syndicate information to advertising networks.
How to control and manage cookies
You hold total autonomy over your local browser storage. Review the step-by-step mechanisms below to calibrate cookie permissions to your privacy standards.
Universal browser settings
Nearly all modern web browsers empower you to inspect, filter, block, or delete cookies on a domain-by-domain basis.
Disable third-party tracking cookies across all external origins
Selectively clear cached cookies and storage specifically for the Pharmogram domain
Enforce whitelist-only permissions for strictly essential healthcare applications
Mobile browser controls
Manage tracking and persistent identifiers directly within your iOS or Android mobile system privacy settings.
Safari (iOS): Settings → Apps → Safari → Advanced → Block All Cookies
Chrome (Android): Chrome Settings → Site Settings → Cookies & On-device Data
Purge mobile browsing storage periodically to reset ephemeral tracking states
Desktop granular storage management
Desktop clients offer deep inspection of partition keys, cookie expiry timestamps, and local storage buckets.
Google Chrome: Settings → Privacy and Security → Third-Party Cookies
Microsoft Edge: Settings → Cookies and Site Permissions → Manage Cookies
Mozilla Firefox: Settings → Privacy & Security → Enhanced Tracking Protection
Private & Incognito browsing
Incognito windows sandbox all session cookies, preventing persistent tracking and purging local storage upon exit.
All temporary session tokens are purged immediately upon closing private tabs
Prevents persistent history logs and client caching on shared pharmacy workstations
May necessitate re-authenticating MFA credentials upon opening fresh sessions
Operational impact of blanket cookie blocking
Completely disabling first-party essential cookies will disrupt critical workflows such as multi-factor authentication sessions, order basket state, and encrypted payment verification. We recommend leaving essential cookies permitted.
Third-party services & partner cookies
Integrated infrastructure partners (payment gateways, encrypted analytics, and support consoles) may deploy specialized telemetry under their respective privacy protocols.
| Partner Domain | Operational Purpose | Telemetry Identifier | Governing Duration |
|---|---|---|---|
Payment Gateway Partner | Secure checkout processing, 3DS authentication & anti-fraud verification | Transaction tokens & fraud risk telemetry (provider-managed) | Per regulatory/PCI-DSS standards |
Platform Analytics Suite | Core Web Vitals monitoring & aggregate traffic diagnostics | First-party proxied session telemetry (anonymized IP) | Rolling 30 days to 14 months |
Customer Support Desk | Real-time support ticket resolution & customer concierge messaging | Support conversation ID & agent dispatch tokens | Duration of active support ticket |
Third-party vendor audits & privacy governance
Third-party cookies remain governed by the respective providers. Pharmogram routinely evaluates and re-audits every technology partner for HIPAA/GDPR alignment, encryption efficacy, and strict operational necessity before granting telemetry rights.
Informational taxonomy disclosure
Third-party cookie identifiers and technical keys evolve periodically in line with downstream provider infrastructure upgrades. We keep this registry synchronized with major vendor revisions.
Cookie duration & lifecycle management
Lifecycles are strictly governed by functional necessity. Ephemeral session tokens vanish immediately, while persistent tokens adhere to deterministic expiration timers.
Ephemeral session cookies
Maintained strictly within your volatile browser RAM and automatically expunged the moment you close your active window or log out.
Persistent configuration cookies
Stored on your local disk with strict TTL expiries (typically 30 to 365 days) to preserve selected UI languages, theme modes, and delivery preferences.
Security & fraud mitigation state
Encrypted tokens persisted temporarily across consecutive sessions to authenticate trusted devices, block brute-force attempts, and safeguard transactions.
Autonomous user purges
You maintain absolute jurisdiction over your local storage. Clear site cookies, indexed DB caches, and local telemetry at any moment via your browser.
Lifecycle adaptability & security revisions
Retention intervals may undergo tightening in response to elevated security protocols, zero-day threat mitigations, or regional regulatory privacy revisions.
Common cookie questions
For more details, visit our Privacy Policy.
Need help understanding cookies?
Our privacy governance team is available for cookie and data-handling inquiries. For comprehensive data practices, review the Privacy Policy and Terms.
© 2026 Pharmogram. Cookies are deployed strictly for platform reliability, security, and service integrity.