Appearance
Privacy Policy
Effective Date: May 6, 2026 Last Updated: May 6, 2026
SaveHealth is an MCP (Model Context Protocol) server that retrieves real-time drug pricing and discount coupon information. This policy describes what data is processed, how it is used, and what controls are available.
Data Collected
SaveHealth processes the following data when you use its tools:
- Drug search queries — drug names you type (e.g., "Ozempic", "atorvastatin")
- Drug selection parameters — drug slug, NDC (National Drug Code), dosage, quantity, and form selected during the workflow
No Personal Information Collected
SaveHealth does not collect or require:
- Names, emails, passwords, or addresses
- Phone numbers or device identifiers
- Social Security numbers or government IDs
- Health insurance information or policy numbers
- Prescription history or medical records
- Location data, IP addresses, or tracking cookies
No account or authentication is needed to use SaveHealth.
Purpose
All data processed by SaveHealth is used solely to retrieve drug pricing and discount coupon information:
| Action | Purpose |
|---|---|
| Search queries sent to search index | Find matching drugs |
| NDC and quantity parameters sent to pricing APIs | Retrieve pharmacy-specific prices |
| Price keys sent to details API | Retrieve discount coupon fields (BIN, PCN, Group ID, Member ID) |
Data is not used for profiling, advertising, analytics, or any purpose beyond fulfilling the immediate pricing request.
Third-Party Recipients
| Recipient | What It Receives | Purpose |
|---|---|---|
| SaveHealth APIs | Drug search queries, NDC/quantity parameters, price keys | Process drug search, pricing, and coupon requests |
| Algolia | Drug name search queries | Fuzzy drug name matching |
No data is sold, shared with advertisers, or provided to any other third parties.
Data Retention
SaveHealth is completely stateless:
| Aspect | Detail |
|---|---|
| Databases | None — no user data is stored between requests |
| Cookies / Local storage | None — no client-side persistence |
| Session tracking | None — each request is independent |
| Server logs | Operational logs may temporarily contain drug search queries for debugging; logs are automatically rotated and do not contain user identifiers |
| Algolia | Search queries are not retained beyond the request |
User Controls
- No account exists — there is nothing to delete
- No data is stored — there is nothing to request or export
- Stop at any time — disconnect or stop using the server with no residual data
Tool Inputs and Outputs
SaveHealth exposes 4 drug pricing tools and 4 informational content tools. Here is exactly what each pricing tool accepts and returns:
1. search_drug
- Input: drug name (string), result limit (number)
- Output: list of matching drugs, each with: display name, slug identifier, brand name, generic name
2. get_drug_options
- Input: drug slug (string)
- Output: available options, each with: drug name, dosage, form, quantity, quantities available, NDC, type (Brand/Generic), default flag
3. get_drug_prices
- Input: NDC (string), quantity (number)
- Output: list of pharmacy prices, each with: pharmacy name, pharmacy chain, price (USD), price key (opaque identifier for coupon retrieval)
4. get_coupon
- Input: price key (string, from get_drug_prices)
- Output: pharmacy name, discounted price, coupon code, pharmacy processing fields (BIN, PCN, Group ID, Member ID), source attribution
Coupon Fields
BIN, PCN, Group ID, and Member ID are generic discount card processing fields used by pharmacies to apply the discount. They are not user identifiers or personal information.
The 4 informational content tools (drug side effects, safety information, drug interactions, and drug overview) accept a drug slug and return publicly available drug information text.
What Is NOT Collected
To be explicit, SaveHealth does not collect:
- Personally identifiable information (PII)
- Health insurance or coverage information
- Prescription history or medication adherence data
- Location data or geolocation
- Device identifiers, fingerprints, or tracking cookies
- Behavioral analytics or usage patterns tied to individuals
Security
- All API communication uses HTTPS/TLS encryption
- The server operates in read-only mode — it cannot modify any external data
- No authentication tokens or credentials are collected from users
Contact
For privacy questions or concerns:
| Channel | Details |
|---|---|
| Website | savehealth.com |
| support@savehealth.com |
This privacy policy applies to the SaveHealth MCP server. SaveHealth is not insurance.