Privacy

What this website collects

Almost nothing, and that is a design decision rather than an oversight. Apart from the inquiry form and the benefits checker described below, this site is static files and it has:

• no analytics, pixels, or advertising tags
• no cookies, and no local storage
• no embedded video, maps, chat widgets, or social scripts
• no fonts or files loaded from other companies' servers

Nothing above has an exception buried in it. There is one thing on this site that another company runs, the benefits checker on the fees page, and it does not load unless you press the button that opens it. Until you do, every page here is entirely my own.

Visiting this site does not tell me you visited. The hosting provider keeps standard server logs, which may include IP addresses, for operational and security purposes; those logs are not reviewed to identify visitors and are not connected to any clinical record.

The inquiry form

The form on the contact page asks for a name, an email address or phone number, and an optional message. When you send it, those details are emailed to me and also recorded in my own practice management system, so that an inquiry sits in a list I work through rather than only in an inbox where it can be missed.

Both copies stay with me. The email is held in Microsoft 365 like any other message. The inquiry record is held in my own Amazon Web Services account, in the United States, and holds only what you typed into the form.

If you do not become a client, that inquiry record is deleted after six months. Inquiring is not the same as being a patient, and I do not keep a file on people I have not treated.

It is processed by a small function in my own Amazon Web Services account. No third-party form service is involved and nobody else receives a copy. There is no tracking attached to it and no CAPTCHA, so nothing about you is sent to another company in order to prove you are a person.

The form is not a secure channel, which is why it asks for so little. Please keep clinical detail out of it.

The benefits checker on the fees page

The fees page offers a check of what your insurance plan pays toward out-of-network care. That check belongs to Mentaya, the company that files superbill claims for clients of this practice, and it is the one thing on this website that another company runs.

It is closed until you open it. Loading the fees page does not load anything of Mentaya's, and does not tell them anyone was there. Pressing the button is what opens their page inside mine, and that is a choice you make rather than something that happens to you.

Once it is open, it behaves like Mentaya's website, because it is Mentaya's website. That includes their own analytics and advertising tags, which is the sort of thing this site does not do and they do. What you type into the check, which is the insurance details it asks for, goes to them and not to me. It does not reach this website, is not stored here, and I am not told that you used it. Everything you enter is handled under Mentaya's privacy policy and their terms, not this page.

The rest of the fees page is unaffected either way. Mentaya's code stays inside that one panel, cannot read the page around it, and does not run on any other page of this site. If you would rather not involve them at all, do not press the button: nothing else here needs it.

Paying by card

The pay page offers a card as an alternative to Zelle. Unlike the benefits checker above, nothing of the card processor's loads on this website at all, not before you press anything and not after. There is no payment form here, no card field, and no script of theirs on any page.

Pressing one of those buttons sends you to Stripe, and the card is entered on Stripe's own page under their address. Card numbers never touch this site and I never see one. What comes back to me is that a payment arrived and for how much.

Stripe is told what you are paying and, so they can email you a receipt, your email address. They are not told anything about your care. The payment is described as professional services and carries no diagnosis, no procedure code, no appointment date, and no note. That is deliberate and it is not a detail: a payment processor has no business holding any of it.

A card payment appears on your card statement under the practice name. Anyone who reads that statement can see it. For some people that matters, and for them Zelle is the better choice, because it does not appear on a card statement at all.

If you keep a card on file, Stripe holds the card and this practice holds only a reference to it. That is always optional, never a condition of being seen, and removed whenever you ask. You will get an email from me before a cancellation fee is ever charged to it.

The booking page

The book a call page is a link, not an embed. Nothing from the scheduling service runs on this website, and following the link is the point at which you leave it. Until you choose to follow it, nothing about you has gone anywhere.

The link opens Microsoft Bookings, which is part of the Microsoft 365 account this practice already uses for email. What you type there, a name, an email address, a phone number, a time and anything you put in the special requests box, is held in that account along with the resulting calendar appointment and confirmation email. Nothing about your visit to this website is passed along with it.

Like the inquiry form, a booking page is not a secure channel, which is why it asks for so little. Please keep clinical detail out of the notes field.

If you email or call

Email and voicemail are ordinary channels and are not secure. What you send by email travels through Microsoft 365 and is stored there. Please use them only to arrange a first conversation. Once you are a client, we will agree on how to communicate between sessions.

Notice of Privacy Practices

Clinical records are governed by HIPAA and by Colorado, California and Florida law, not by this page. The practice Notice of Privacy Practices describes how protected health information may be used and disclosed and what rights you have over it.

A copy of the Notice of Privacy Practices is provided at intake and is available on request at any time.

Accessibility

This site is built to meet WCAG 2.1 AA: it works by keyboard, carries visible focus, uses text contrast well above the minimum, and respects a reduced motion preference. If something here is hard to use, please call or email and tell me. I will fix it and, in the meantime, give you the information another way.

Changes to this page

If the site ever begins collecting information, this page will say so before that starts.