Privacy Policy

1. Information We Collect

Medicare Claims Data (via CMS Blue Button)

When you choose to connect your Medicare account, we collect from the Centers for Medicare & Medicaid Services (CMS) Blue Button 2.0 API:

• Claims History (ExplanationOfBenefit): service dates, healthcare provider information, diagnosis codes (ICD-10), procedure codes (CPT, HCPCS), medication codes (NDC, RxNorm), claim amounts, and claim types.
• Coverage Information: Medicare plan name, member ID, coverage effective dates, and coverage type (Part A, Part B, Part D).
• Patient Demographics: name, date of birth, Medicare Beneficiary Identifier, and gender.

Account & Site Information

Email address (for sign-in and notifications), device information (for security and session management), account creation date, and last sign-in timestamp. When you submit our marketing-site sign-up form, we collect what you provide (name, email, optionally organization and role) through Formspree.

Usage Information

Pages visited, features used (timeline views, provider-sharing actions), error logs (no claims data included). We do not deploy first-party analytics cookies, tracking pixels, or retargeting scripts on this site.

2. How We Use Your Information

We use your Medicare claims data to:

• Visit preparation: display your medication history, procedures, and care timeline to help you prepare for appointments.
• Provider sharing: let you share selected claims with your healthcare providers — only when you explicitly choose to share.
• Account management: maintain your Medicare connection and sync updates to your claims history.
• Service improvement: analyze de-identified usage patterns. Never individual claims.

We do not:

• Sell your Medicare data to third parties
• Use your claims data for advertising or marketing
• Share your data with anyone without your explicit permission
• Train artificial-intelligence or machine-learning models on your claims data

3. How GetPreCare's Architecture Protects You

Most health apps store your data on their servers and run their own AI on it. GetPreCare is built differently. Privacy here is not a promise — it is the topology of the system.

Your vault, your data

Your Medicare claims and any other records you connect live in a vault that is encrypted with keys that require your authentication to unlock. We host the vault. You own the contents.

Engines run on demand, then forget

When you ask for a coordination summary, a coverage analysis, or insights from one of our partner tools, the tool processes your data inside your authenticated vault session and returns a result. The raw data does not leave the vault. The tool does not retain a copy.

No training on your data

Because the data stays in your vault, no model — ours or anyone else's — can train on it as a side effect of using GetPreCare. This is enforced by the architecture, not by policy alone.

Optional research, on your terms

If you choose to contribute to research in the future, your data still does not leave your vault. Instead, your vault computes a small mathematical update that helps improve a model without exposing your records. This is called federated learning. It is always opt-in, per project, with the right to withdraw at any time.

A marketplace of patient-chosen tools

Over time, GetPreCare will let you choose which tools run in your vault. You decide which ones you trust. Each tool declares, in advance, exactly what data it needs to do its job, and the system enforces those limits.

4. Data Sharing

With Your Healthcare Providers (Patient-Controlled)

You can share specific portions of your Medicare claims data with your healthcare providers. You control what is shared, who can see it, and how long. You can revoke provider access at any time.

With Service Providers

We work with a small number of trusted processors. Each receives only the data necessary for their function:

• Database hosting: encrypted claims data stored on US-based, SOC 2 Type II–certified infrastructure.
• Authentication: email and authentication credentials managed by our identity provider.
• Formspree (forms.formspree.io) — receives marketing-form submissions and securely delivers them to us.
• Calendly (calendly.com) — receives your name and email when you schedule a call.
• Vercel (vercel.com) — hosts this site and may log IP, user-agent, and request timestamps for security and analytics.
• Google Fonts (fonts.googleapis.com) — serves the Inter typeface; receives your IP and browser info.

Never Shared

We never share your Medicare claims data with advertisers, data brokers, third-party marketers, insurance companies (unless you explicitly request it via provider sharing), or employers. We do not sell personal data, ever.

5. Active Opt-In Requirement

6. Data Retention

While Your Account is Active

Claims data is retained while your account is active and your Medicare connection is maintained. OAuth tokens are retained until expired or you disconnect Medicare.

When You Disconnect Medicare

• Default: claims data retained for 90 days, then permanently deleted.
• Immediate deletion option: deletion completed within 24 hours of your request.
• OAuth tokens: revoked at CMS and deleted from our systems immediately on disconnect.

When You Close Your Account

Medicare connection disconnected and tokens revoked immediately. All claims, coverage, and account data deleted within 30 days. Backups purged within 90 days.

7. Your Right to Disconnect and Revoke

Sign in to GetPreCare, open Settings > Connected Accounts, find "Medicare," and click "Disconnect." Choose 90-day retention or immediate deletion. You can also revoke GetPreCare's access directly through MyMedicare.gov.

8. Dormant Account Policy

An account is considered dormant after 18 consecutive months of no sign-in activity. We notify you at 15 months and 17 months by email; at 18 months your Medicare connection is automatically disconnected and a 60-day grace period begins. After the grace period expires, all claims data is permanently deleted.

9. Security & Breach Notification

How We Protect Your Data

• Encryption in transit: HTTPS (TLS 1.2+) on all communication
• Encryption at rest: tokens encrypted with AES-256-GCM; database encrypted at rest
• Access controls: Row-Level Security in our database, JWT-based authentication, RLS-violation logging
• Audit logging: every data access tracked in an internal audit table
• Architectural privacy: the vault model means we cannot read your data without your authenticated session

Breach Notification

In the event of a breach affecting your Medicare claims data, we will notify you within 72 hours by email and in-app, notify CMS Blue Button API support per developer terms, and file regulatory notifications if required by law.

10. State-Specific Rights and Other Provisions

• California (CCPA): right to know, request deletion, and opt out of any "sale" of personal information. We do not sell personal information.
• Other states: we honor comparable rights in Virginia, Colorado, Connecticut, Utah, and other states with consumer privacy laws.
• Children's privacy: GetPreCare is not intended for users under 18.
• International users: services are operated from the United States.
• Do Not Track: we do not currently respond to browser DNT signals. We do not engage in cross-site tracking.

11. Changes to This Privacy Policy

For material changes affecting how we handle Medicare data, we notify you at least 30 days before changes take effect (email and in-app), and obtain CMS approval before deployment as required by CMS Developer Terms. Changes do not apply retroactively.

12. Contact Us

• Privacy questions: privacy@getprecare.com
• Security concerns: security@getprecare.com
• General support: support@getprecare.com
• CMS Blue Button: bluebutton.cms.gov

Mailing Address:
Continuum Health Systems LLC
30 N Gould St Ste R
Sheridan, Wyoming 82801