Legal and policies
Cookie Policy
A plain-language explanation of cookies and similar technologies used by HealthRam and the choices available to users.
Draft under legal review. This policy is not yet final.
Effective date: [Insert before launch] • Last updated: [Insert date]
1. What cookies are
Cookies are small files or similar browser/device technologies used to remember settings, maintain sessions, protect accounts and understand how digital services perform. Similar technologies may include local storage, software development kits, pixels or comparable tools.
2. Cookie categories
- Strictly necessary: authentication, security, fraud prevention, load balancing, consent storage and core service functionality. These cannot generally be disabled through the HealthRam consent tool where required to provide the requested service.
- Preferences: language, accessibility and other settings that improve usability.
- Analytics/performance: aggregated or pseudonymous information used to understand page performance, errors and user journeys. These should be optional where consent is required.
- Marketing/advertising: technologies used for promotional measurement or audience activity. HealthRam should keep these off by default unless explicitly approved and valid consent is obtained.
3. Health-data protection rule
HealthRam must not intentionally place prescription details, medicine names, diagnostic results, patient identifiers or other sensitive health information into advertising pixels, analytics event names, page URLs, third-party tracking parameters, session-replay payloads or error-monitoring metadata. Before release, analytics, advertising, logging and monitoring implementations must minimize data and pass documented privacy/security review.
4. Consent and controls
Where required, users should be shown a clear cookie notice that allows optional categories to be accepted or rejected without pre-ticked choices. Users should be able to reopen Cookie Settings from the footer and change non-essential preferences at any time. Withdrawal should be as easy as giving consent.
5. Third-party technologies
Some approved technology, payment, security, support or analytics providers may set or read cookies when their functionality is used. HealthRam should maintain a production cookie inventory identifying the provider, purpose, category and retention period. The live Cookie Settings interface should reflect the technologies actually deployed rather than relying only on this policy text.
6. Browser/device controls
Users may also use browser or device controls to block or delete cookies. Blocking necessary cookies may prevent sign-in, security validation, preference retention or other core features from working correctly.
7. Retention and updates
Cookie durations should be limited to what is necessary for each stated purpose. HealthRam may update this policy when technology or legal requirements change. Material changes to optional tracking should be reflected in the consent interface and, where required, renewed consent should be obtained.