PulpDental.io
PlatformHow it worksQuestions
Sign inGet started ↗
PlatformHow it worksQuestionsSign inGet started ↗

Last updated October 26, 2026

Privacy policy

PulpDental helps dental clinics verify a patient's insurance benefits before a visit. This policy explains what the PulpDental web app at pulpdental.io and the Pulp Dental Insurance VerificationChrome extension collect, why, and how it is protected. It applies to clinic staff who use the product; patients should ask their clinic about the clinic's own privacy practices.

Who we are

PulpDental is operated by the PulpDental team. Questions about this policy, and requests to export or delete data, go to shubham@spaceharpoon.com.

What the Chrome extension does

The extension has a single purpose: when a signed-in clinic user starts a verification in the PulpDental web app, the extension opens the patient's insurance company portal in a browser tab, signs in with the clinic's own portal account, reads the benefits the portal shows for that patient, and sends them to PulpDental so the verification form is filled in. It only runs on the payer portals listed in its permissions and on pulpdental.io, and only while a verification the clinic started is in progress. It never runs on other websites, never reads browsing history, and shows nothing to anyone but the clinic.

Data we handle

  • Clinic account data. Your sign-in name, practice name, NPI, address, hours and the dentists you add.
  • Patient and insurance data.Patient name, date of birth, phone number, policy holder details, member and group numbers, and the benefits the insurance company reports (coverage status, maximums, deductibles, coverage per procedure, frequencies, history). Clinic staff enter this, or patients submit it through the clinic's intake link, or the extension reads it from the payer portal. This is protected health information under HIPAA; clinics use PulpDental as part of their own treatment and payment operations.
  • Payer portal logins.If a clinic chooses automatic sign-in, the clinic's portal username and password are stored encrypted in PulpDental and handed to the extension only for the duration of a verification. The extension keeps them in memory, never writes them to disk or extension storage, and discards them when the run ends. Clinics can switch any portal back to manual sign-in or delete the stored login at any time in Settings.
  • Verification-code emails. Some portals email a one-time code at sign-in. If a clinic sets up forwarding, those emails are delivered to a PulpDental address, the code is read, used once within ten minutes, and the email text is kept only long enough to diagnose a missed code. No other mail is read.
  • Documents the portal produces. Benefit summaries the portal offers as PDFs may be downloaded by the extension and parsed for the same benefit fields; the parsed values are kept with the verification.
  • Technical data. Which portal step a verification reached, when, and any error text, so failures can be fixed. If a portal page cannot be read, a short outline of its page structure (element names, not patient data) is kept with the error.

What we do not do

  • We do not sell or rent any data, and we do not use it for advertising.
  • We do not collect web browsing activity. The extension sees only the payer portal tab it opened for a verification.
  • We do not use data for anything other than providing and improving PulpDental for the clinic that entered it.
  • We do not use clinic, patient or insurance data to train machine-learning models.

Where data goes

Everything the extension collects is sent over HTTPS to the PulpDental API at api.pulpdental.io and stored in a PostgreSQL database hosted in the United States. The extension talks to no other server. The web app itself is hosted on Vercel. We use transactional email (Maileroo) to receive forwarded verification-code emails and to send a test email to the clinic. Where a clinic uses the in-app phone features, calls go through Twilio. These providers process data only on our instructions.

Security

All traffic is encrypted in transit. Portal passwords are encrypted at rest with a key held outside the database. The extension holds a short-lived token for each verification; the token identifies one check for one clinic and expires within hours. Access to clinic data requires that clinic's sign-in.

Retention and deletion

Verifications, patients and intake records stay in the clinic's account so staff can refer back to them. A clinic can delete patients, verifications, stored portal logins and forwarded emails from the app, and can ask us to delete the whole account by emailing the address above. One-time codes are discarded once used or after ten minutes.

Chrome permissions, in plain words

  • tabs and scripting: to open the payer portal in a tab and read the benefit tables on it, only on the portal domains listed in the extension and only during a verification.
  • storage: to remember which verification is in progress so it survives a service-worker restart. No patient data or passwords are stored there.
  • Host access to the listed insurance portals and to pulpdental.io, so the web app and the extension can talk to each other.

Changes

If this policy changes in a way that affects how data is handled, the date at the top moves and clinics are told in the app before the change takes effect.

Back to PulpDental

PulpDental.io

A clearer picture of dental benefits.
A more connected front desk.

ExploreThe platformHow it worksQuestions
Your workspaceGet startedSign inChrome extension ↗
Here to helpSupportContact the teamPrivacy policy
© 2026 PulpDentalBuilt for the work behind the care.Back to top ↑