Who we are
CommunityDX ("we") is a market tool for dental practices, veterinary clinics, and medical groups. You use it to study an area: who lives there, which specialists already practice there, and where a new location might fit.
This policy covers communitydx.com, including Atlas, Report Builder, your account, and the contact and support forms.
We are based in Dallas, Texas. Privacy questions go to [email protected]. You can also use the support page.
Information we collect
Account
When you create an account we ask for your first name, last name, email, profession (dentist or veterinarian), and a password. Phone is optional. An organization signup also asks for the organization name. The profession on that signup is the profession for the whole organization.
An owner or admin can create a teammate's account by entering that person's name, email, and a starter password. The teammate has to choose a new password before using the product. We do not keep our own copy of any password. Google Firebase Authentication stores it.
Your profile can include a photo. We store the image in our file storage. Teammates in your organization can see it. You can remove it.
You can save notification preferences for product updates, support replies, billing, marketing, and security, and whether you want email, text, or in-app notices. In-app notices stay on. Security notices stay on. We do not send marketing email or text messages today. Those preferences are saved for when we do. The email we send now is a password-reset message, and only when you ask for one.
Payment
Checkout is Stripe's form, on our signup page. Stripe collects the payment details. We keep the plan, the subscription status, the Stripe customer id, when the current period ends, and whether the latest payment failed. We do not store your full card number or security code.
What you save in the product
Atlas can save recent searches. Each one stores the address and the map coordinates. You can also save pins, and places you label as a partner, owned, excluded, or a custom location. A custom location can include a name, an address, a category, notes, and coordinates. You can upload a spreadsheet of names and US street addresses. Those become custom locations on your account.
A report includes the address you asked about and the file we generate.
Pins and saved places start private to you. You can share them with your organization. A shared item shows your display name. If you are in an organization, a report is visible to the other members from the moment it is created.
In-app notifications can name the event, such as a billing notice or a support reply.
Messages you send us
The contact form asks for your name, email, an optional company, and a message. We also store the IP address and browser type for that submission, and your account id if you were signed in.
The support page asks for your name, the email on your account, a topic, and a message. You do not have to be signed in. If you are signed in and write from Account, then Support, we also store your account id and organization id.
You can tell us a specialist location is missing or wrong. That report includes the location details you enter and your name and email.
The feedback form, when you are signed in, asks how it went, an optional category, whether it blocked you, a message, and whether we may contact you about it. We also store the page you were on.
The Request a Demo form on the marketing pages does not send your name, email, or notes to our servers. We only record that the form was opened, submitted, or closed, and whether the company and notes fields had text in them.
Usage and your device
We record which page you are on. If you are signed in, usage events include your account id. On Atlas we record actions such as adding a pin, changing a filter, opening a chart, sharing a saved place, and whether a search worked.
A successful address search includes the address you typed, the matched address, and the coordinates. A specialist search includes the coordinates of that search, the profession, and how many locations came back. We do not send your name, the notes you type, chart contents, or a password to analytics.
Our host keeps ordinary server logs. Those can include an IP address, browser type, and the page requested.
Public market data
Atlas and Report Builder show publicly available census statistics and publicly available specialist listings, including national provider identifier (NPI) records. That information does not come from you. We do not collect patient records or medical charts.
A label you put on a location, such as partner, owned, or excluded, stays in your account. It does not edit the public listing, and it is not a verified ownership claim.
How we collect it
- You type it in: signup, profile, support, contact, feedback, uploads, and labels on the map.
- The product records it as you use Atlas and the rest of the site.
- Stripe, Mapbox, and public census and provider sources provide what we need to run checkout, the map, and the market views.
- Google Tag Manager receives the usage events described above.
How we use it
- To create and run your account, including sign-in and organization membership.
- To show the map, drive-time areas, specialist locations, and the reports you ask for.
- To take payment and keep your subscription in the state you chose, including a failed payment.
- To reply to support, contact, and feedback messages.
- To remember searches, pins, places, and reports so you can come back to them.
- To tell you about account events you have not turned off.
- To see which parts of the product people use, and to fix what breaks.
- To limit abuse of the public contact form.
- To meet law that applies to us, and to keep the service secure.
We do not sell your personal information. We do not let other companies use it to advertise to you on other sites.
Legal basis
This service is built for people and practices in the United States.
If you are in the European Economic Area or the United Kingdom, this is the basis we rely on. We process account, payment, and saved-work information to provide the service you signed up for. We process security logs and abuse limits so we can run a safe service. We process usage events to understand the product. Where a law requires consent before analytics cookies, we do not currently ask. Analytics tags load with the page.
Where it is processed
We and the providers named above process information in the United States. If you use CommunityDX from another country, your information comes here.
How long we keep it
- We keep account information while the account is open.
- The sign-in cookies last 5 days. The cookie that opens a saved place on the map from the dashboard lasts 2 minutes.
- We keep support tickets, contact messages, location reports, and feedback so we can answer them and keep a record. We have not set a fixed delete date for those.
- Analytics tools keep usage events under their own settings.
- When you ask us to delete an account, we delete the account information we are able to delete. Stripe may keep payment records it is required to keep. An organization activity record can still name a removed member.
Your choices and requests
On your profile you can see your name, email, and profession. You can change your photo, and you can ask for a password-reset email.
Notification choices are under Account, then Notification preferences. You can turn marketing email off there. We do not send marketing email or text messages today.
You can delete pins, places, and other saved items from the product.
Email [email protected] to ask for a copy of your account information, a correction, or deletion. We will reply within 45 days. There is no self-serve delete button yet.
We will not charge a different price or shut off a feature because you made a privacy request.
California residents
You can ask what personal information we collect, ask us to delete it or correct it, and ask us not to sell it or share it for advertising on other sites. We do not sell personal information, and we do not share it for advertising on other sites, so there is no sale to opt out of. We will not treat you differently for asking.
Security
Pages load over an encrypted connection. The sign-in cookie is not readable by page scripts. Card numbers are entered on Stripe's form. Photos and reports are not public, and each view is checked against your account.
No service is perfectly secure. If you think someone used your account without permission, email [email protected].
Children
CommunityDX is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child gave us personal information, email [email protected] and we will delete it.
Changes to this policy
We post a new version on this page and name the date it applies. A small change can apply the day we post it. When a change needs advance notice, that date is later than the day we post it. We do not email these changes.
Other
A link to another site, including a map link that opens Google Maps, is not covered by this policy. That site has its own.
The laws of the State of Texas, and the United States laws that apply, govern this policy.
Contact
CommunityDX
Dallas, Texas
[email protected]
communitydx.com/support