HIPAA does not apply just because an app collects sensitive health information. Its reach usually depends on the relationship connected to the data. The relevant questions, as discussed in When health apps asked whether HIPAA applied to them, are who collected the information, for whom it was collected, and whether the app handles it on behalf of a covered entity.

When an application handles protected health information for a covered entity, the developer is a business associate. That role carries direct obligations under HIPAA, including requirements reflected in the Code of Federal Regulations. The result is different when an application collects the same type of information directly from consumers outside a provider relationship. HIPAA generally does not cover that activity. The Federal Trade Commission and state law may still impose requirements, including the concerns discussed in The FTC covers what HIPAA does not.

This distinction can produce different results for information that appears equally sensitive. Sensitivity by itself does not determine whether HIPAA applies. The relationship behind the collection and use of the information does.

The relationship matters more than the data

A person might enter health information into an app in at least two different settings. In one, a provider uses the app during or in support of a clinical encounter. In the other, a consumer completes a health questionnaire before becoming a patient or before any provider relationship exists.

The questions may be similar, and the answers may concern the same medical subjects. The privacy obligations may still differ.

When a developer handles information for a covered entity, the developer has a business associate role and direct obligations under HIPAA. When a company collects information directly from consumers outside that provider relationship, HIPAA generally does not govern that activity. This remains true even when the information is medically sensitive.

That does not mean information collected directly from consumers has no protection. The Federal Trade Commission and state law may create obligations that apply to the company’s practices. Those rules operate under a different framework from HIPAA.

For that reason, a company’s privacy practices cannot be assessed by asking only whether the company has health data. A more useful inquiry asks how the company obtained the information and whether a provider relationship existed when the collection took place. The same company may handle information at several stages, with different facts at each stage.

Why telehealth creates a boundary problem

A telehealth platform may operate on both sides of this boundary. The clinical encounter may fall within HIPAA, while the marketing funnel that brought a person to the platform may not. To a user, both activities may look like parts of one service. The applicable privacy obligations can still differ.

The boundary may arise before a person speaks with a clinician. A quiz or other pre-intake feature may collect health information before the user becomes a patient. The platform may also collect analytics as the person moves through the service. That information may be treated under a different framework from consultation notes.

A person may assume that every health detail entered into a telehealth service receives the same protections. That assumption may be incorrect when some information was collected during marketing or pre-intake activity rather than during the clinical encounter.

Our GLP-1 clinic rankings cover how providers handle patient information, but the comparison also raises a policy question. A service should explain the different stages of the user experience and describe them clearly enough for users to understand when they are providing information before a clinical relationship begins.

What to examine before sharing information

A general privacy policy may not answer the most important question for someone concerned about pre-intake information. Users should look for language that addresses this data directly. The policy may discuss information entered before a consultation, data collected through a quiz, or analytics gathered while someone decides whether to use the service.

The aim is to determine where the service places its boundary. A policy may describe patient information in broad terms while leaving it unclear whether the same treatment applies before a person becomes a patient. General statements about health information may therefore provide less detail than a separate explanation of pre-intake collection.

This distinction also matters to developers building services that combine a clinical encounter with a consumer-facing funnel. The user experience may make those stages appear connected even when different privacy frameworks apply. The source of the information and the relationship in place at the time of collection remain central to the analysis.

A service may collect information before a consultation, during a consultation, and after a person enters a provider relationship. Reviewing each stage separately can help identify which facts determine the applicable obligations. The label attached to the information does not answer that question by itself.

The practical test

The most useful starting question is not, “Does this app contain health information?” It is, “For whom is the app handling that information?”

If the app handles information on behalf of a covered entity, the developer may be a business associate with direct obligations under HIPAA. If the app collects the information directly from consumers outside a provider relationship, HIPAA generally does not reach that activity. The Federal Trade Commission and state law might still apply.

This test will not answer every privacy question. It does identify where the analysis begins under HIPAA’s statutory framework. It also explains why two parts of one platform can receive different treatment. The data may look the same in both places, but the relationship connected to the collection determines the obligation.