Privacy Policy

1. Scope

Argoseer is a provider data intelligence platform. This policy covers two categories of data: (a) customer data that accountholders give us when they sign up and use the platform, and (b) public-record provider data that we aggregate from CMS NPPES, CMS PECOS, state medical boards, the HHS OIG LEIE, payer FHIR directories, and public practice websites. The handling rules differ; both are described below.

2. Customer Data We Collect

When an accountholder signs up for or uses Argoseer, we collect:

• Name, email, phone, and practice affiliation at signup
• Authentication records (magic-link tokens, session cookies, IP at login)
• Billing information processed by our payment provider (Stripe); Argoseer does not store full card numbers
• Application usage events: pages visited, actions taken, workflow approvals and declines
• Support correspondence and user feedback submitted in-app

3. Public-Record Provider Data We Ingest

Argoseer aggregates provider data from public and semi-public sources. The sources and the way we use each one are documented here for transparency.

• CMS NPPES (weekly delta file): NPI, provider name, address, taxonomy, phone, deactivation status. Ingested from the public NPPES distribution.
• CMS PECOS: Medicare enrollment data including reassignments and specialty. Ingested monthly from the public PECOS extract.
• State medical boards: license status, issue and expiration dates, disciplinary history where published. Texas Medical Board and California Medical Board live today; additional boards added as we expand.
• HHS OIG LEIE: the monthly List of Excluded Individuals / Entities, NPI-matched to roster where possible.
• Payer FHIR directories: directory listings from UnitedHealthcare, Aetna, Cigna, Humana, Blue Cross Blue Shield of Texas and other payers, read on the cadence each payer publishes via the Plan-Net FHIR endpoint or public PDF.
• Public practice websites: a weekly deep crawl of publicly accessible pages to extract provider rosters, accepting-patient claims, payer lists, and compliance disclosures. We respect robots.txt directives and do not bypass authentication.

This data is public by definition. Argoseer does not collect or host protected health information (PHI) about patients as part of provider monitoring. If customers upload supplementary material that could contain PHI, it is handled under the BAA terms of the applicable agreement.

4. How We Use This Information

• To run detection pipelines that compare sources against each other
• To surface mismatches, license drift, disciplinary signals, and OIG exclusions on the dashboard or Monitor surface you subscribed to
• To generate correction packets and workflow tasks
• To provide analytics and history to the practice that owns the account
• To improve detection accuracy in aggregate; individual provider names and NPIs are not used in marketing or outbound sales
• To send service-related email (account, security, billing)

5. Data Accuracy, Confidence, and Limitations

Because Argoseer aggregates public-record data on a schedule, the platform necessarily reflects the state of those sources at the time of the most recent ingest. A few things customers should understand:

• License status is refreshed on the cadence each board publishes. Data may lag the issuing board by 24 to 72 hours. Argoseer is not a primary source verifier and does not issue or certify licenses.
• Disciplinary actions are compiled from state board newsroom feeds and the OIG LEIE monthly file. Pending actions or actions published between our ingest cycles may not yet appear. Confirm with the issuing board before a credentialing, hiring, or privileging decision.
• OIG exclusions are pulled from the LEIE monthly file and NPI-matched where possible. Not every exclusion action is reflected in LEIE, and NPI-to-exclusion matching is probabilistic for records without an NPI on file. Always confirm with oig.hhs.gov/exclusions before a final determination.
• Confidence scores are a statistical match signal, not a legal determination. Low-confidence rows prompt review; they do not document that a provider is or is not associated with a practice.
• Payer directory listings reflect what each payer currently publishes. A mismatch does not by itself indicate a contract dispute or enrollment gap.
• Accepting-patients flags extracted from practice websites reflect public claims and do not guarantee current appointment availability.

6. Data Storage and Security

All customer data and aggregated public-record data is stored on servers located in the United States. We implement industry-standard security measures including encryption at rest and in transit, role-based access controls, and regular security reviews. Our infrastructure is HIPAA-aligned and we are pursuing SOC 2 Type II certification.

7. Data Sharing

We do not sell or rent customer information. We share data only with:

• Service providers essential to operating the platform (hosting, payment processing, transactional email). Each is bound by confidentiality and data-protection terms.
• Legal authorities when required by law or to protect our rights
• Third parties with your explicit consent for specific integrations

8. Your Rights

As a customer you have the right to:

• Access personal data we hold about your account
• Request correction of inaccurate account data
• Request deletion of your account and associated customer data
• Opt out of marketing communications
• Export your practice data in a portable format

Provider-specific public-record data (for example, license status on a public NPI) cannot be removed from Argoseer at a provider's request because it originates from authoritative public sources we do not control. Requests to correct the underlying public record should go to the source of record (for example, the state medical board for license data, or CMS for NPPES data).

9. Cookies and Tracking

We use essential cookies for authentication and session management in the application. You can control cookie preferences in your browser settings.

Our public marketing site uses first-party, cookieless analytics to understand aggregate traffic — page views, referrers, and coarse geography. We run this ourselves, with no third-party analytics or advertising trackers. It sets no tracking cookies, never stores raw IP addresses (only a salted hash), identifies visitors solely by an anonymous hash that rotates daily, and honors your browser's Do-Not-Track and Global Privacy Control signals.

10. Changes to This Policy

We may update this policy from time to time. Material changes will be announced by email or in-app. Continued use of the platform after a change constitutes acceptance.

11. Contact Us

For privacy-related inquiries, contact us at info@argoseer.com or call (512) 273-7205.