Skip to the policy

Privacy policy

Last updated . Effective .

NezerCare helps clinics answer questions on their websites, triage the health concerns their patients raise and send what needs a person to the right one. This policy explains what information we handle, why, and the choices you have.

In short

1. Who this policy covers

This policy is from NezerCare ("we", "us"). It covers nezercare.com, the NezerCare staff app, the chat widget clinics put on their websites, our API and our developer docs. It speaks to three groups of people. For the first two, we decide what is collected and why. For the third, we work for the clinic.

1.1 People who visit nezercare.com

You may read our pages, use the chat on our site, write to us or ask for a demo. We decide what is collected and why, and this policy is our notice to you.

1.2 Clinics and the people who work at them

Clinics, telehealth companies and other healthcare businesses (our customers, "clinics" here) create a NezerCare workspace, and their staff sign in to it. We decide what we collect to set up and run the account, the sign-in, the billing and support. This policy is our notice to the people who do that.

1.3 Patients, and visitors to a clinic's website

Clinics use NezerCare to talk with their patients and to answer visitors on their own websites, and some use our API to do so from their own patient portal. Information about those patients and visitors is the clinic's. Under HIPAA we are the clinic's business associate: we handle patient information only on the clinic's instructions, and under a Business Associate Agreement (BAA) the clinic signs with us. Patient features stay off until it's signed.

If you're a patient, your clinic's notice of privacy practices explains how your health information is used, and your clinic is the place to ask about it. This policy describes how NezerCare handles it for them. Patients don't create a NezerCare account: the clinic's website signs you in to its chat. A clinic's chat and the emails we send for it say "Powered by NezerCare" unless the clinic has removed that line. This policy applies either way.

2. What we collect

2.1 When you visit nezercare.com or use NezerCare

2.2 When you chat with Nezer or a clinic's website chat

The chat on our site, and the chat clinics put on theirs, answers questions from people who haven't signed in. We process anonymous messages without saving their text on our servers. The optional try-link carry in your browser is described under Cookies and browser storage. Here is what happens during an anonymous chat:

The chat's default greeting says that it is an AI assistant, and the chat says so if you ask whether you are talking to a person.

On a clinic's site, the chat remembers for the rest of your visit that it already greeted you (a "shown" flag in that site's session storage), and nothing else. The fixed-answer demonstration on our main site makes no chat requests and stores nothing. A private try-link demonstration reads a company's public pages and sends questions to our service to answer them, but saves no anonymous question text on our servers. It is NezerCare's demonstration, not the company's own chat or its endorsement. Health questions receive fixed care-team guidance; emergencies receive 911 guidance. It cannot reach that company's care team.

2.3 When you write to us

The contact form on nezercare.com asks for your name, email address, a subject and your message. What you write is not stored on our site: it reaches our team as an email, with your address as the reply-to, and we use it only to answer you. To stop the form being flooded we keep a keyed, one-way hash of your network address for about a day. If you email us instead, we receive your message and address the same way. Please don't include health details; our inboxes aren't meant for them.

2.4 When you request a demo

We ask for your name, work email, company, the kind of practice you run, your team's size, what you hope NezerCare will do for you, and the time you book. We use these details to arrange the demo and prepare for the call. We email you a confirmation, a reminder and a link to move or cancel; our team gets an email about your request. When our demo calendar is connected to Google Calendar, the booking is an event on our Google Calendar with a Google Meet link: Google sends you the invitation and holds your name, email, company and answers as part of that event. Otherwise we send the invitation ourselves. We don't add you to marketing lists or share your details with anyone else for their own use. Please don't include patient information in your answers.

2.5 When you create a workspace

Anyone can sign up for a clinic and start a free trial. To do that we collect:

To allow one free trial per person, we also keep a one-way hash of your email address, not the address itself. It stays after a workspace is deleted, so a deleted account can't start another trial. We use the same kind of hash for about a day to limit how many workspaces one email can start. When your workspace verifies its website, so its chat can go live there, we keep that website's domain with your workspace, and how and when it was verified (a team member's email at that domain, a DNS record or a code on its home page). It is deleted with the workspace.

Our own team is emailed when a workspace is created and at a few later moments, such as its website being read or verified, its chat being added to the clinic's site, its BAA being signed and its trial ending. The email names the workspace and its owner's address and says where its trial or plan stands. It never includes anything a patient said. A bot-protection check (Google reCAPTCHA) may also run when you sign up, to stop automated abuse.

2.6 When you work at a clinic and use NezerCare

2.7 When you're a patient of a clinic that uses NezerCare

On the clinic's behalf, NezerCare handles:

If the clinic chooses, cases of some kinds are also sent to its own systems, such as its EHR. A case sent this way carries your first message, the questions we asked you and your answers, and the case's urgency. See "Where a clinic tells us to send it" below.

Emails we send you for the clinic, such as a care update or a message from the care team, open with "Hello there" and don't include your name or a description of any health concern, only a secure link that works once and expires after seven days. They show the clinic's name. If an appointment is booked for you, we also email you a notice when it is booked, moved or cancelled, and a reminder a day and an hour before it; these show the appointment's time in your time zone and never the visit link, which you open in the chat. When several updates arrive together on one case, we send one email. Replies to them aren't read, so please contact your care team through the link instead.

Photos and PDFs you attach are checked before we store them: we save a photo again without its location, camera and other hidden details, and we refuse a PDF that contains scripts or embedded files. Files are stored encrypted. You can remove a file you added until the care team has opened it; after that, ask your clinic. The clinic's owners and administrators can delete any file, and our audit trail records when staff open one.

If your clinic connects a messaging workspace, limited default case notices show a randomly generated NezerCare reference, broad administrative category and secured link, without identifying patient content. Without confirmed PHI mode, the Assistant refers to patients only by an ID a staff member wrote or an opaque NezerCare reference, never independently adding names, contact details or health information, and reports the outcome of the task requested by staff, such as delivery status, reasons a message could not be sent, or a clinic workflow result. Such an outcome may still reveal PHI in context. Where a clinic confirms appropriate provider BAA coverage, enables PHI messaging, and selects an authorized channel, the Services may, where supported, deliver patient identities, case summaries, messages, medication and prescription details, and Assistant replies relevant to authorized workflows directly in that channel. These messages may contain PHI. The clinic chooses who may access the channel and manages membership, guests, external participants and permissions. Features differ by integration and configuration; not all described capabilities are available on every platform.

When a case opens as an emergency, we alert the people the clinic chose to hear about emergencies, by email and in its connected Slack or Microsoft Teams channel. The alert says only that an emergency case has arrived and links to the clinic's queue. It has no patient name, identifier, words or description of the concern.

3. Cookies and browser storage

NezerCare doesn't use cookies for tracking or advertising, and the website, the staff app and the chat widget don't set cookies of their own. They use your browser's storage for a few small things. Nothing you type in an anonymous chat is saved there unless you choose the try-link carry described below:

Only when you press Create your free workspace in a try-link demonstration, your browser saves nezer-try-carry in its local storage: the website's domain, an adoption ticket and up to five questions the demonstration couldn't answer, each of at most 300 characters. The ticket lets your new workspace copy the demonstration's public website pages and look. Once your workspace is created, the domain and ticket are removed and the questions stay, tied to that workspace, until you press Add to my list (which sends them to its list of unanswered questions) or No thanks. The record expires 24 hours after you pressed Create; an expired one is deleted the next time a NezerCare page reads it. Signing in to an existing workspace carries nothing.

If you choose not to count this browser in Platform admin, local storage remembers that choice in nezer-site-traffic-off. Remove it with the same control to allow counting again.

A signed-in patient's chat session is kept in the chat window's memory only. It is never a cookie. Our fonts are served from our own site, so loading a page doesn't contact Google Fonts.

Google reCAPTCHA runs on the staff app's second sign-in step and may run when you create a workspace. Google loads it from its own servers and may use cookies and similar technologies, under its own policies, to tell people from bots.

We don't track you across websites, so there is nothing for a browser's Do Not Track or Global Privacy Control signal to turn off.

4. How we use information

We use information to:

We use patient information only to provide the service to the clinic, as our BAA allows. We never use it for marketing. To run and improve the service and to produce overall usage figures, we may use information that has been de-identified under HIPAA's standards, and we don't try to re-identify it.

5. How we use AI

NezerCare uses contracted AI processing services, currently provided through Google Cloud in the United States, to assist with the following functions:

Some things AI never does:

We do not use patient information, customer-derived de-identified patient information, or visitor messages to train, retrain, fine-tune, evaluate for improvement, or otherwise improve AI models, and our BAA limits the same use by subcontractors. We use AI services to process permitted requests and may retain encrypted case-related inputs and outputs as part of the clinic’s records until applicable deletion. Provider logging and retention are governed by the applicable configuration and contractual commitments; we do not promise that every system retains data for zero time. Non-model service analytics and security monitoring remain permitted.

6. Who we share it with

We never sell personal information, and we don't share it for cross-context behavioral advertising or targeted advertising. We share it only in these cases.

6.1 Service providers

We use service-provider categories including cloud hosting, database and file storage, AI processing, authentication, email delivery, billing, business communication and scheduling. We share only information needed for the relevant service. A current provider-level list of subcontractors handling patient PHI is available to clinic customers upon request. When HIPAA requires a downstream BAA, we put one in place before the provider handles PHI. Vendors used for business administration are not intended to receive patient PHI; please do not submit health information to our business mailboxes or demo forms.

6.2 Customer-selected destinations and messaging

Clinics can connect their own EHRs, webhooks and supported Slack or Teams services. Default unconfirmed case notices contain an opaque case reference, a broad administrative category, and an authenticated link, without patient IDs or message contents. When a clinic enables @Nezer in an unconfirmed workspace, the Assistant responds to requests from the clinic’s staff using only an ID the staff member wrote or an opaque NezerCare reference; it does not independently add a patient name, contact details, health information, or a different clinic patient ID. It may report what happened in the requested workflow, including whether a message was sent and reasons for failure, case creation, or the result of a customer-configured workflow. Such status information may constitute PHI when connected to a patient. When a clinic confirms that its specific messaging service and designated channel are covered by appropriate arrangements with the provider, including a BAA where required, and enables PHI messaging, NezerCare may provide authorized workflow-relevant patient names, IDs, case summaries, patient-authored messages, medication or prescription details, status reports, and Assistant replies through supported functions. The clinic is responsible for selecting a suitable channel, limiting who can see it, managing membership and guest access, and promptly disabling PHI mode if its channel becomes inappropriate. NezerCare applies its own integration and approval controls, and the provider BAA alone does not justify unrestricted disclosure. Emergency alerts remain generic. If a clinic enables @Nezer in Slack, we read connected-channel messages to identify instructions addressed to the Assistant and process authorized requests. Features are available only where supported and configured.

We may disclose information when the law requires it, such as a valid court order, or to protect people's safety or our rights. For patient information, we follow HIPAA and our BAA with the clinic.

6.4 If our business changes hands

If NezerCare is merged, acquired or sells its assets, information may pass to the new owner, who must keep protecting it as this policy and our agreements with clinics require.

7. How we protect it

No system is perfectly secure. If a breach affects patient information, we tell the clinic as our BAA and the law require, so it can tell the people affected.

8. How long we keep it

9. Your rights and choices

9.1 If you're a patient

Ask your clinic. It decides on requests to see, correct or delete your health information, and we help it respond. If you write to us, we'll pass your request to your clinic and won't answer it ourselves unless the clinic asks us to or the law requires.

9.2 Visitors, clinic staff and everyone else

You can ask us for a copy of your information, or ask us to correct or delete it. Write to our privacy team or to the mailing address at the end of this policy. We may need to confirm who you are first, and we'll reply within the time the law requires. Clinic staff can also ask their clinic's administrator, who manages the team's access.

9.3 US state privacy rights

Depending on where you live, for example California, and on whether a state's law applies to us, you may have rights under state law to know what personal information we have about you, to get a copy, to have it corrected or deleted, and to appeal if we turn down a request. To make a request, contact us as described above. You can ask through someone you authorize, and we won't treat you differently for using your rights. To appeal, write to us with "Appeal" in the subject.

We don't sell personal information, and we don't share it for cross-context behavioral or targeted advertising, so there is nothing to opt out of. We don't pass personal information to others for their own direct marketing. The kinds of information we collect and why are described above, and we disclose it only to the service providers and destinations under "Who we share it with". Health information we handle for clinics is covered by HIPAA rather than by these laws, and requests about it go through the clinic.

10. Children

NezerCare is a service for healthcare businesses. Our website and staff accounts aren't meant for children under 16, and we don't knowingly collect their information there. If you think a child has given us information, write to our privacy team.

Clinics may use NezerCare to care for patients of any age, including children. That information is the clinic's, handled under its agreement with us. Parents and guardians should contact the clinic about it.

11. Where your data is

Our systems are in the United States. Patient information is stored and processed there, and our BAA keeps it there unless the clinic agrees otherwise in writing. Some providers that handle other information, such as Google Calendar and Stripe, may process it elsewhere. If you use NezerCare from another country, your information is transferred to the United States.

12. Changes to this policy

When we change this policy, we'll update the date at the top. If a change is significant, we'll tell clinics before it takes effect, by email or in the app.

13. Who we are and how to reach us

13.1 Who we are

NezerCare is operated by NezerGroup LLC, doing business as NezerCare. NezerGroup LLC provides the NezerCare platform and acts as a business associate for patient information under its agreements with customer clinics.

13.2 How to reach us

Questions or requests about privacy? Email our privacy team, or write to:

Please don't include health details; our inboxes and mailbox aren't meant for them. Patients should contact their clinic first.

Clinics can find what we do for them in our developer docs (nezercare.com/developers) and in their BAA.