Home / Privacy

Privacy

How Pacific Clinical Solutions LLC handles information about visitors, account holders and the providers in the data.

Pacific Clinical Solutions LLC · effective November 2, 2026. This text is in effect and has not yet been reviewed by outside counsel. Any change after that review will be posted here with a new effective date.

In short

Providers in the data

Provider pages show what CMS publishes about each NPI in its Medicare Part B public use files and its Doctors and Clinicians data: name, credentials, specialty, practice location on claims, affiliations and billing statistics. We add calculations (work RVU totals, percentiles, ranks) described on the methodology page. Street addresses are not shown unless the provider turns them on. Providers can ask for a correction (Corrections) and claim their page (Claim your page).

What we collect, and why

WhatWhyKept
Email address; sign-in link and session records (stored as one-way hashes)Your account and signing inUntil the account is deleted; sign-in links expire in 15 minutes, sessions after 30 days unused
Purchases: product, what it covers, price and price version, any report credit applied, tax, date, data years included, the version of the Terms and refund policy you accepted and when, delivery records (when the report was first and last opened or downloaded, when the confirmation was sent), Stripe customer and payment idsGiving you access, receipts, report credits, support and refunds, and showing what was delivered if a charge is questionedWhile the account exists. At deletion the purchase is unlinked from you and what it unlocked is removed, along with the physician or market it covered; its product, price and policy versions, amount, tax, date, data years, delivery times and Stripe payment ids stay as an accounting record for tax purposes. Unused report credits end with the account. We do not delete your Stripe customer record: Stripe keeps its customer and payment records under its own retention policy
Support requests: the reason, the purchase, your message, your email address, our answer and the outcomeAnswering duplicate charges, access or delivery problems and refund requests3 years after the request closes, with your email address removed if you delete the account
Event log: the name of a step (for example search, sample report viewed, checkout started, payment completed, report opened), the time, the product and price version, the physician or market of the page, and a visitor key: a keyed one-way hash of the IP address and browser that changes every day; the IP address and browser themselves are not stored. No cookie is set for it, nothing about any figure is recorded, and no key is kept when your browser sends Do Not Track or Global Privacy Control. Signed-in steps also carry your account idCounting how many visitors with usable data buy a report, whether reports are delivered and opened, and how many need support, by price version13 months, then deleted. Revenue is counted from purchases, not from this log
A verified NPI: the number, entity type, the qualifying taxonomy code, the time of the checkClaiming a page, and the area of an earlier Local report. It does not unlock any figureUntil you verify another NPI or delete the account
Page claims: NPI, level, method, time, and a one-way hash of the phone number or email address usedEdit access for a claimed page, and email notices: when CMS releases new data for the page and when a correction request on it is opened or closedUntil you release the claim or delete the account
State license number and photo ID uploaded for a license reviewChecking an edit-level claim by handDeleted when the reviewer decides, and within 30 days in any case
Provider-supplied statement, website, contact line and street-address settingShowing them on the claimed pageUntil the provider changes or removes them; they stay in place across data refreshes. Deleting the edit-level account that added them removes them, unless another verified account manages the page
Correction requests: the text, your email address, the page, our decision and its logDeciding and recording corrections3 years after the ticket closes
Server logs: IP address, browser, page requested, time, responseSecurity, rate limits and fixing errors90 days at most, then deleted. The web server keeps no separate access-log file
Rate-limit counters (keyed by a keyed hash of an IP address or email address, never the value)Limiting sign-in, lookup and form requests2 days

Backups of the database are kept on a 35-day rolling window: each backup is deleted when it is 35 days old, so anything deleted from the site is gone from every backup within 35 days.

Cookies

Two first-party cookies, no others: cl_session, which keeps you signed in (HttpOnly, 30 days, renewed while you use the site), and cl_auth, which only tells the page header whether to show "Sign in" or "Account". No analytics, advertising or third-party cookies. The event log above is kept on our own server, sets no cookie and is not shared with any analytics or advertising company.

Who processes it for us

Each receives only what its task needs. We do not sell or rent personal information, and we do not share it for advertising.

Your choices

Security

Traffic is encrypted. Sign-in links, sessions and claim contacts are stored as one-way hashes. Access to the database and backups is limited to the people who run the site.

Children

The site is for adults working in or around health care. We do not knowingly collect information from anyone under 16.

Changes and contact

We post changes here with a new effective date and email account holders about material changes. Questions: ben@claimlight.io. Corrections: corrections@claimlight.io. Pacific Clinical Solutions LLC operates claimlight.io.