Legal
Privacy and data use
Effective October 20, 2026.
ClinicIntent is a product of Andrew Suver Ventures LLC, of Washington, United States ("we", "us"). This page says what we keep about the people who use ClinicIntent, what ClinicIntent reads about practices and from where, what it never does, who processes data for it, how long it is kept, and how to have an account deleted. Write to support@clinicintent.com with any question about it.
1. What is kept about you
Your account: its email address and the name you give it; the company and territory you choose; its plan and seats; and each seat's invitation, whose link is kept only as a one-way hash.
Signing in: with the link an account was given when it was set up. Sessions and sign-in links, and the addresses that asked for one, are kept only as one-way hashes. An account set up by hand signs in with a link whose key is kept as it was issued.
Your work: the marks you set on practices (called, reached, meeting, proposal, won or lost, with the value, date and reason you give), your notes and call-back dates, the practices you star, your alert settings, which practices a teammate has taken, and when your call list was last looked at.
Exports: how many rows the account exported from the search, the market page and the call list, each month.
A customer list you upload: your browser reads the file and sends only the columns needed to match it. We keep the list's name, how many rows it had and matched, and which practices matched and how; no name, address or email from the file is kept. Dates you add are kept beside the practices they match. A new upload replaces the last, and a list can be deleted at any time.
Your company's own website: read once to learn what your company sells, robots.txt first and at most twelve pages; what it sells is kept, not the pages.
A CRM or chat connection, where you make one: its tokens, and the addresses of a Slack, Microsoft Teams or webhook connection, are kept encrypted. Each push is logged with the practice, the record it made, whether it went through and what was sent. Disconnecting deletes the connection; the log is kept.
Billing: each billing step, with Stripe's customer, subscription and checkout ids, the plan, the territory and the amounts. Card details are held by Stripe, never by ClinicIntent.
A form: a preview request on the pricing page keeps the company, name, email, state and vertical given; a correction on the method page keeps the practice, the fact, the note, the reply address and a one-way hash of the sender's IP address.
Your browser: a signed-in browser keeps its sign-in in local storage, and a few short steps (a Google sign-in under way, a page's last answer) use session storage. ClinicIntent sets no cookie of its own. The front page, the pricing page, the terms and this page (and two old addresses that lead to the front page and the method page) load Google's analytics tag, which sets cookies to count visits; the signed-in pages do not load it. Fonts load from Google Fonts on every page.
2. How it is used, and who processes it
To run the account: show its calls, market, search and feed, count its exports, sign it in, bill it, and send the emails it asks for. It is not sold and not shared for advertising. It is processed by Stripe (payments and the billing portal); Resend (emails to you: sign-in links, the Monday email and alerts, each only when it is switched on); Google (sign-in when you choose it, the analytics tag on the public pages, and fonts); and the services that host ClinicIntent: Vercel (the site), Railway (the application) and Neon (the database). When you connect one, HubSpot, Salesforce, Slack, Microsoft Teams or your own webhook receives the practices you send it.
3. How long it is kept
What is kept about an account stays while the account exists; nothing about it is deleted on a timer. Sign-in links and sessions stop working when they expire, and their hashed records stay. You remove things yourself by replacing or deleting a customer list, unstarring a practice or disconnecting a connection, and everything by asking for the account to be deleted.
4. Deleting your account, and your other rights
To delete your account, write to support@clinicintent.com from the account's email address. There is no delete button. A plan's billing is cancelled first; then the account is deleted with its organization's plan, seats and records, every row that names it, the preview and correction requests it sent, and the database's history copies of them, and we reply to confirm. Stripe keeps its own billing records as the law requires. Write to the same address to see or correct what is kept about you.
5. What ClinicIntent reads about practices, and from where
Every fact on ClinicIntent is read from one of these sources, and links back to it:
The NPI registry. NPPES, published by CMS and read from its weekly files: practices, providers and their NPI numbers, the official who files for each practice with their title and phone, practice addresses and phone numbers, and when each was registered or changed.
State dental board license files. Texas, California, New Jersey, Wyoming, Washington, Illinois, Colorado, Connecticut and Delaware, read weekly from each board's published file or open-data listing: license numbers, statuses and dates. The Texas and Washington files carry a birth year column, which is never kept.
CMS Medicare and Open Payments. The procedures each provider billed Medicare, and the payments companies report making to clinicians, as CMS publishes them.
SBA loan records. The SBA's 7(a) and 504 loan data, published under the Freedom of Information Act, read each week from the files the SBA updates each quarter.
Building filings and permits. The Texas Department of Licensing and Regulation's architectural barrier (TABS) filings, and city and county building permits from their open-data portals, for offices being built; the US Census geocoder places their addresses.
Practices' own websites. Read as described below.
Open places data. To find med spas and practices' websites: Overture Maps Foundation's places data (Meta, Microsoft, PinMeTo, Krick, RenderSEO, DAC and BrightQuery under CDLA Permissive 2.0; Foursquare under Apache 2.0; AllThePlaces under CC0 1.0) and Foursquare Open Source Places (Copyright 2025 Foursquare Labs, Inc., under the Apache License 2.0).
Job postings. Practices' own careers pages, read directly; Google Jobs results, read through SerpApi and DataForSEO; and Adzuna's published listings, through its API.
Google's business listings. Read through Serper: whether a practice's listing is marked permanently closed, the listing's phone, and the listing at an address, to tie a posting or a new practice to it.
The Internet Archive. Captures in the Wayback Machine, to date when a practice's own site first named a product. The capture's address and the line that names it are kept, not the page.
Email verification. An owner's email built from a practice's mail domain was checked with Hunter and MillionVerifier before it was shown. With the email reveal switched on, which it is not today, Hunter receives a practice's domain and a person's name to find an address.
Each dataset's terms, and Foursquare's notice in full, are in the method page's sources. Each kind of fact is shown only after a drawn sample of its rows, usually thirty, is read by hand against its source; the result and the denominator are published on the method page. Kinds of fact that fail are withheld, not shown with a caveat.
6. How a practice's website is read
ClinicIntent reads a practice's site as ClinicIntentBot, a user agent that names the product and a contact address. It reads robots.txt first and does not read what it disallows, and it waits at least a second between requests to one site. Where a site refuses the direct read with a challenge page or an error, a page may be read once through scrape.do, a page-reading service, under the same robots.txt rule. No page behind a login is read, no headless browser is used, and no CAPTCHA is solved. One earlier read of practices' sites, made before this reader existed, identified itself as a browser and did not read robots.txt first; facts from it are shown where their checks passed.
The tools a practice's site loads: ClinicIntent reads only a practice website's public code, as any browser receives it: the scripts and frames a page loads, the links it sends patients to, element ids, the footer credit and the analytics and ad tags on the page or in its tag manager container. No visitor data, cookie or analytics result is read, collected or stored; a tag's ID says the tag is installed, not who visits.
7. What is kept about practices and the people at them
For each fact: the page or record it came from, when it was read, and the words it rests on. About people: the names, NPI numbers, titles and phones the registry publishes; the people a practice's own site names, with their title, and their email only where the site publishes it; an owner's email built from the practice's mail domain and verified; license numbers, statuses and dates from the state boards; a clinician's graduation year or years in practice, where the practice's own site states it; and Medicare and Open Payments figures per clinician, as CMS publishes them. A phone shown is the one the practice's own site gives, else its matched Google listing's, else the registry's.
The people a practice's own site names: ClinicIntent keeps the names and roles practices publish on their own sites: each name as the site writes it, the role the site gives the person, the line on the page that names them, the page's address and the day it was read. From those pages it keeps no photo, no age or birth year and no personal address. When a later read of the same page no longer names a person, or names someone new, that change is recorded with both reads' dates. Anyone can ask for their line to be removed by writing to support@clinicintent.com with the practice's website and the name as the site writes it: the line is taken off ClinicIntent, and the site is not read for that person again.
Copies of the public web pages ClinicIntent reads are kept in a working cache on ClinicIntent's own systems, outside the product database.
No birth year or date of birth is kept. No estimate of a person's age is kept either.
8. What ClinicIntent never does
It never sends an email to a practice on your behalf: the routes that could are closed, and any outreach is your own. It never reads a job board's pages: Glassdoor, Indeed, LinkedIn, ZipRecruiter, SimplyHired, Monster, Snagajob and CareerBuilder are never fetched. It never keeps a birth year or date of birth. It never buys or sells lists of contacts.
9. Corrections
A practice, or anyone, can report a wrong fact from the method page. A person reads each report, and the fact is corrected or withheld.
10. Changes and contact
This page may change; an account is told of a material change by email. Questions, and requests to see, correct or delete what is kept: support@clinicintent.com. The terms of service govern the account and its plan.
Andrew Suver Ventures LLC, of Washington, United States ยท ClinicIntent