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
- (a) We don't sell personal information, we don't share it for advertising, and we don't show ads.
- (b) Our website counts traffic without cookies or visitor identifiers. We use no advertising trackers, and NezerCare sets no cookies of its own.
- (c) We don't store anonymous chat text on our servers. In a private try-link demonstration, questions it couldn't answer are saved in your browser only if you press Create your free workspace, and reach your new workspace only if you then press Add to my list. Health questions never get an AI answer; emergencies get fixed 911 guidance.
- (d) Patient information belongs to the clinic. We handle it on the clinic's behalf, as its business associate under HIPAA and a Business Associate Agreement, and only to provide the service. Patients should ask their clinic about their information.
- (e) We do not train AI models on patient information, including patient information de-identified under HIPAA, or permit our PHI-handling subprocessors to do so except under a separate, express written agreement and applicable safeguards.
- (f) Our systems are in the United States, and patient information stays there. It is encrypted in transit and at rest.
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
- (a) Server and security logs. Like any service, our hosting records technical details of each request, such as your network (IP) address, browser type, the page asked for and the time. We use these logs to keep the service running and to detect and stop abuse.
- (b) Counting visits. We count visits to nezercare.com ourselves, without cookies: which page was viewed, how long it was visible, the country the visit came from (as our network provider reports it; we never store your IP address), the website or campaign link that sent you, and whether you used a phone, tablet or computer. We keep only daily totals, never visitor identifiers or anything you type. We keep the totals for 13 months. If your browser sends Global Privacy Control or Do Not Track, we don't count your visit. nezercare.com still has no advertising pixels or third-party tracking scripts.
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:
- (a) Your message is checked for emergency words first. An emergency gets fixed, reviewed guidance to call 911, with no AI involved.
- (b) It's then processed, only in passing, to tell a health question from a business question (like pricing, shipping or how the service works). Business questions are answered from the clinic's own website and articles.
- (c) Health questions never get an AI answer. A visitor who hasn't signed in is pointed to the clinic's contact option and the 911 line.
- (d) During an anonymous chat our servers keep only counts, not your words: for example that a question was answered, or that it was a billing question the clinic's content didn't cover.
- (e) Your chat is held by a random code that lives in the chat window's memory. We store only a one-way fingerprint (hash) of that code, the chat's start and end times and how many messages it had, to cap how many questions one visitor can ask. A chat lasts at most a day.
- (f) To stop someone opening endless chats, we count chats per network address, but we never store the address. We store a keyed, one-way hash of it that is different for each clinic's site, so a visitor can't be linked across sites.
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:
- (a) your work email and a password (the password goes straight to Google Identity Platform; we never see it), and we email you a link to verify the address;
- (b) the name of the clinic, its website (we read up to 100 of its public pages, following its robots.txt, so the chat can answer from them) and the kind of practice if you tell us;
- (c) that you accepted the Terms and this policy, which version of each, and when;
- (d) a keyed, one-way hash of your network address, never the address itself. We use it to limit how many workspaces can be started from one place in an hour and a day, and we keep it with your acceptance of the terms.
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
- (a) Your account. Your work email, your password and any name on your account are handled by Google Identity Platform (Firebase Authentication); we never see your password. We send the verification and password-reset emails. A second sign-in step, with a code texted to your phone, protects sensitive actions, so Identity Platform also keeps that phone number; our own systems never see it or the code. Google reCAPTCHA checks that step to stop automated abuse.
- (b) Your workspace. Your role, your team, settings, and the content your clinic adds (its website, articles, Health concerns and workflows), including any questions staff type into the Playground or Knowledge to test the chat. If a colleague invites you, we receive your email address from them and email you the invitation, which expires after seven days.
- (c) An audit trail. Who did what, and when, for sensitive actions and changes to settings. Clinic staff with the right role can see their own organization's log.
- (d) Signing the BAA. When someone signs a BAA in the app, we record their name, title, email, the time, their network address and browser, as evidence of the signature.
- (e) Feedback you send us about NezerCare itself. The form asks you not to include patient information, and we read it to improve NezerCare.
- (f) Billing. The plan, usage (such as credits used) and invoices. Card details go straight to Stripe; we don't see or store card numbers. When you buy credits by card after your free trial, Stripe keeps the card so that automatic top-ups can use it if you turn them on. We email a receipt for each automatic top-up that names the amount, the credits added and the card's brand and last four digits; we keep only those details of the card, in the record of that receipt.
- (g) Setting a workspace up for you. If we set your workspace up on a call, our team works in it with access that is limited in time and never includes patient data.
- (h) Connections you set up. If your clinic connects Slack, a system that receives its cases, or webhook endpoints, we keep the access tokens and credentials it gives us for them, encrypted, so that we can post and deliver on its behalf.
- (i) What our team can see about your workspace. In our administration tools our staff can see each workspace's owner (the email address, with a note when it is at a free mailbox provider such as gmail.com) and the people on its team: the name your sign-in provider holds, if any, the email address, the role, whether two-step sign-in is set up, and when each person joined, was invited or was removed. We use this to run accounts, give support, keep the service secure and tell genuine workspaces from throwaway ones, and we record each time staff look at a workspace's team. It never includes patient information, a password or a sign-in code.
- (j) Appointment reminders for staff. If you book an appointment on a case in the staff app, we email you, and the person the case is assigned to, about an hour before it, with the case's reference, the time (in UTC) and a link to the case. The email has no patient name or health information.
2.7 When you're a patient of a clinic that uses NezerCare
On the clinic's behalf, NezerCare handles:
- (a) what the clinic's website tells us when you sign in to its chat (or, for a clinic with its own patient portal, what the portal tells us through our API): the clinic's own ID for you and, the first time, your first name and email address, with your last name and phone number if the clinic sends them. That sign-in is how a patient is added to NezerCare, and later sign-ins refresh these details. Each time you open the chat it also tells us the time zone your browser reports (a name such as America/New_York), which we keep with your profile to write appointment times in your own time zone, and update if you open the chat from another one;
- (b) what you write once you're signed in: a health concern you describe, your answers to the clinic's questions and safety checks, the summary you review and send, your messages, photos and PDFs to the care team, questions you ask the chat, and any thumbs up or down you give an answer;
- (c) what the care team does with it: the cases it opens for you, marked emergency, urgent or routine, its replies and notes, any appointment it books for you (its time, and the visit link your clinic supplies), how it resolved them, and summaries of them;
- (d) details like times, whether a message was delivered, and a record of when staff viewed your information.
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.
4. How we use information
We use information to:
- (a) provide the service: answer questions, triage health concerns, route messages and cases to the right people, remind patients of appointments and alert a clinic's team to an emergency;
- (b) keep it secure, prevent abuse and fix problems;
- (c) run accounts, sign-in, billing and support, and reply when you contact us;
- (d) arrange and prepare demos you ask for;
- (e) start your free trial, limit it to one per person and stop automated sign-ups;
- (f) meet legal obligations.
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:
- (a) tell a health question from a business question and spot urgent messages, so they reach the right person;
- (b) when a signed-in patient describes a health concern, match it to one of the clinic's concern types, read it against the safety checks and choose which approved question to ask next. The patient sees fixed, approved wording (the clinic's own, or NezerCare's defaults until the clinic approves its own), never text the AI wrote;
- (c) answer business questions from the clinic's own content;
- (d) summarize cases and draft messages for the clinic's staff, who review them;
- (e) follow up on cases a clinic has posted to Slack and, if the clinic turns it on, carry out what teammates ask of @Nezer there, once the team says yes;
- (f) check BAA copies a clinic uploads.
Some things AI never does:
- (a) It never answers a health question. Those go to the clinic's care team, and emergencies get fixed 911 guidance chosen by rules, not by a model.
- (b) It doesn't diagnose, prescribe, or change anyone's treatment.
- (c) A message telling a patient the outcome of a care team's decision is sent only after a member of that team approves it.
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.
7. How we protect it
- (a) Encrypted in transit with TLS 1.2 or later.
- (b) Encrypted at rest. Patient profiles, messages, photos and PDFs, appointment visit links, AI intake conversations and other sensitive records are also encrypted by our application (AES-256-GCM) before they're saved.
- (c) Each clinic's data is kept apart by the database itself (row-level security), not only by our code.
- (d) Staff need a second sign-in step to open patient information or to make sensitive changes.
- (e) Patient links work once, and a signed-in patient's session ends after 30 minutes without activity, and in any case 12 hours after it began.
- (f) Access to patient records, including staff opening a photo or PDF, is audited. The audit trail can't be edited; when a clinic deletes a patient's information, its entries keep who did what and when, without the patient's details.
- (g) Patient messages are kept out of our application logs and our internal administration tools, except where needed to provide the service. Our people can reach patient information only when they need it to provide, support or secure the service.
- (h) Stored and processed in the United States.
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
- (a) Anonymous chats: we don't keep what you type on our servers. A try-link carry is saved only in your browser, after you press Create, and expires 24 hours later. The chat's fingerprint and message count are deleted 30 days after it ends. Network-address counts are deleted soon after their hour has passed.
- (b) Patient links and sessions: a link from a care-update email works once, and expires after seven days. A signed-in patient session ends after 30 minutes without activity, and in any case 12 hours after it began.
- (c) Patient information: for as long as the clinic's agreement with us requires. After the agreement ends, our BAA commits us to return or delete the clinic's patient information within 60 days, with backup copies gone within 90 days. A clinic can export its data, or a single patient's record, at any time, and delete a patient's information when it approves a request. A clinic can also delete a single file, and a patient can remove a file they added until the care team has opened it. Backups made before a deletion keep a copy until they expire: we keep backups for no more than 30 days, and in every case they are gone within 90 days after the agreement ends.
- (d) Workspaces: kept while the clinic's account is open. If a free trial ends without a plan, the workspace ordinarily remains read-only; an account with no active plan for 90 consecutive days may be closed on at least 30 days' notice under the Terms of Service. For owner-initiated closure, active-system deletion is ordinarily scheduled 30 days later; other closures may use a 7-to-60-day window. PHI in active systems is returned or destroyed no later than 60 days after termination, subject to the BAA's lawful-retention exceptions; backups rotate according to the BAA. Exports are available during the applicable export window.
- (e) Staff accounts and audit trails: while the clinic's account is open, and then as the clinic's agreement and the law require. Team invitations expire after seven days. Feedback you send us is deleted with the workspace.
- (f) Demo requests and messages to us: until you ask us to delete them, or once we no longer need them to follow up with you. The contact form's hourly-limit hash is deleted after about a day.
- (g) Sign-up records: your acceptance of the terms is kept as a record of what you agreed to and when. The one-way hash that allows one free trial per person is kept after a workspace is deleted. Counts of sign-up attempts are kept for about a day.
- (h) After a workspace is deleted we keep the signed BAA and its signature record, which hold no patient information, for as long as the law requires.
- (i) Billing records and receipts: as long as tax and accounting law requires.
- (j) Server and security logs: for a limited time, to keep the service running and secure.
- (k) Appointments and time zones: an appointment's time and visit link are kept with the case, the link encrypted, and are deleted with the patient's information. A patient's time zone is kept in the patient's profile until the patient's information is deleted.
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:
NezerGroup LLC
7027 W Broward Blvd, Unit #3206
Plantation, FL 33317
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.