Skip to main content
Kave Health

Privacy

Kave is designed so that sensitive information never reaches it. Here is exactly what that means.

This page describes how the product is built. It is a plain-language summary written by the team that built it, not a lawyer-reviewed privacy notice, and it must be reviewed by healthcare privacy counsel before launch.
  • What Kave does not ask for

    Kave is designed so that sensitive information never reaches it in the first place. It does not ask for, and has nowhere to store:

    • Your name
    • Your Social Security number
    • Your full date of birth
    • Your insurance member ID or plan number
    • Your hospital account number
    • Your diagnosis or medical records
    • Uploaded documents or bills

    There are no user accounts, so there is no profile to build and nothing to breach.

  • What happens to the guided questions

    Your answers live in your browser while you are answering, and then in the address of your results page so it can be bookmarked, printed, or shared if you choose to. They are not written to a database, not attached to an identity, and not used to build a profile. Closing the tab ends it.

    If you share a results link with someone, remember that the link itself contains your answers — including, for example, that you selected “I do not have insurance”.

  • What happens when you report a problem

    The issue report form asks what is wrong and, optionally, for an email address so Kave can follow up. The email field is optional, is used only to reply about that report, and is never used for marketing or shared with the organisation you are reporting.

  • Analytics and cookies

    Kave measures whether pages work — which pathways get abandoned, which searches return nothing — and deliberately does not record the answers you give. No analytics event carries an insurance status, a selected need, a hospital name, or anything else that would reveal your medical or financial situation. Sensitive form values are also excluded from error reports.

    The public site sets no advertising or tracking cookies. Signed-in administrators have a session cookie, which is required for them to log in at all.

  • Leaving Kave for another site

    Links to programs and hospitals open those organisations’ own websites, which have their own privacy practices. Kave labels every external link with the site it opens so you can decide before you click.

  • Health-data posture

    Kave is built so it does not receive protected health information from providers and does not need detailed patient information to be useful. Document upload, bill upload, patient accounts, provider integrations, and personalised case management are all out of scope and would each require specialised healthcare privacy counsel before being considered.