Questions about LLIF, answered plainly

LLIF — the Live Learn Innovate Foundation — is a 501(c)(3) nonprofit foundation. Its job is to govern the data layer of an ecosystem that includes a consumer app (Best Life) and a developer platform (OpenLife Cloud).

LLIF doesn't build the apps people use. It holds the legal framework that determines how participant data is protected across the ecosystem — and it enforces that framework as an independent organization with its own board and governance structure.

No. They're three separate legal entities with three distinct roles.

Best Life is the consumer app — built by Best Life Inc. — that people use to track their health and lifestyle. OpenLife Cloud is the developer and research platform that other builders and researchers work with. LLIF is the nonprofit foundation that governs the data layer both of them sit on.

LLIF doesn't operate Best Life and doesn't own or control it. The two organizations have a formal Data Partner Agreement that binds Best Life to LLIF's governance standards.

Because a for-profit company holding personal health data has a structural incentive to extract value from that data. That incentive doesn't go away because the company promises not to act on it — it just creates pressure that bends behavior over time.

A 501(c)(3) nonprofit with participant data classified as a donor-restricted asset has no such incentive. The organization's legal purpose is the protection of participant data, not return on investment. That's not a soft difference — it's a structural one that changes what can and can't happen to participant data.

An independent board of directors. Board members serve fixed terms and are not employed by LLIF. They hold exclusive authority over any change to how participant data is governed — including the Participant Data Charter, the Data Partner Agreement terms, and LLIF's nonprofit status.

No single person — including LLIF's founding team — can unilaterally change the core data protections. That separation is deliberate and permanent.

Yes. LLIF is a 501(c)(3) nonprofit incorporated in North Carolina, with current and verified IRS tax-exempt status. It files annual Form 990 returns, which are publicly available. It holds a Candid Platinum transparency rating for 2026 — the highest level awarded to nonprofits for financial and operational transparency.

You can view LLIF's Form 990 and Candid profile on the Financials page.

It's a specific legal classification under IRS nonprofit governance rules. When LLIF designates participant data as a donor-restricted asset, it means the data is held under legally binding conditions that restrict what can be done with it.

In plain terms: the data cannot be sold, licensed for advertising or commercial purposes, or transferred to a for-profit entity — regardless of who is running LLIF, what the financial conditions are, or what any future acquirer or leadership team wants. The restriction isn't a policy. It's law.

No. Full stop. Participant data is a donor-restricted asset. Selling or commercially monetizing it — whether to advertisers, data brokers, insurers, or any other third party — is legally prohibited under LLIF's governing structure.

LLIF's operating costs are funded through grants, philanthropic contributions, and program fees. There is no financial model here that depends on the value of what participants share.

A privacy policy is a commitment the organization makes to itself — written by the company, enforced by the company, and updatable by the company. Most privacy policies can be changed with 30 days' notice and assumed consent from continued use.

LLIF's data protections are embedded in its governing documents and backed by 501(c)(3) nonprofit law. Changing the core protections requires a full board vote and, in some cases, IRS notification. They can't be quietly amended. They can't be reversed by a new CEO. The legal mechanism is categorically different.

The protections stay. That's the point.

LLIF's data governance doesn't depend on the intentions of whoever is currently running the organization. The board holds authority over governance changes — not the executive team — and the board is independent. The donor-restricted classification applies regardless of who is in charge. A new CEO inherits the obligations, not the discretion to change them.

Under nonprofit dissolution law, if LLIF were ever to cease operations, its assets — including participant data — must transfer to another charitable organization with a compatible mission. They cannot be distributed to founders, sold to a commercial buyer, or converted to private use.

IRS approval would be required for any such transfer, and the receiving organization would need to accept the same data protection obligations. Participant data cannot simply be liquidated.

No. A 501(c)(3) nonprofit cannot be acquired in the commercial sense. Its assets — including the data it holds in trust for participants — are legally bound to its charitable purpose and cannot be redirected to commercial ends through an acquisition transaction.

This is one of the practical reasons the nonprofit structure matters: there's no acquisition path that puts participant data in new hands under different incentives.

Only organizations that have signed LLIF's Data Partner Agreement — which binds them to the same data protection standards LLIF holds itself to. This includes app developers, research institutions, and program organizers.

Every access to participant data is logged and visible to the participant in their data access record. There is no silent data use. Partners cannot access data outside the scope of what participants have consented to, and LLIF retains audit rights throughout.

In two layers. The first layer is consent to LLIF's overall data framework — what LLIF can hold and what it will never do. This covers the permanent protections: no data sale, export rights, deletion rights, and the right to see every access.

The second layer is consent to a specific program or study. This is separate, scoped, and specific: it covers only what that particular program organizer can access, and for how long. Joining one program doesn't extend consent to other programs or future uses. Each consent event is timestamped and recorded in your consent log.

Six specific rights, backed by board oversight and public governance documents:

You own your data — LLIF holds it in trust; ownership never transfers. You can export your full data at any time, in standard formats, with no waiting period. You can request deletion, processed within 30 days and permanent. Your data will never be sold. You will be notified of every research or partner access. And you can revoke consent to any program at any time, immediately.

Yes, at any point. You can revoke consent to any specific program or study without affecting your participation in others. You can delete your account entirely. These actions are processed immediately, logged, and confirmed.

Revoking consent from a study terminates that program organizer's ongoing access to your data. Historical data collected under prior valid consent may be retained per study protocol, but no new data is collected after revocation.

Because personal health data is most valuable — and most sensitive — when it spans years, not days. A sleep pattern tracked over 18 months reveals things a single reading never could. That kind of contribution requires trust that outlasts any given product version, any given leadership team, and any given business condition.

Most privacy promises are only as durable as today's conditions. LLIF's governance structure is designed to remain aligned with participant interests regardless of what changes around it. That's what makes long-term participation reasonable.

Best Life is one way to participate — it's the primary consumer app built on OpenLife Cloud infrastructure. But other app developers can also build on the same governed platform, and participation can happen through any of them.

LLIF's governance applies to the data layer, not just to Best Life. Any app that operates under the Data Partner Agreement is subject to the same participant protections.

Yes. That's one of the core things OpenLife Cloud exists for. Developers who build on the platform get a governed data backend — consent management, audit logging, program infrastructure — without building it themselves.

In exchange, they sign the Data Partner Agreement and agree to operate within the same governance framework. They can't use participant data for purposes outside the consented scope, and they can't transfer or monetize it. The governance layer applies to everyone who touches the data, not just to LLIF.

Yes, through the Program structure. Research institutions can publish a study as a Program — a structured, consent-backed research project that participants can explicitly opt into. Consent is specific: participants see what data types the study will access, who is running it, and for how long.

The research team signs the Data Partner Agreement before data access begins. LLIF retains audit rights throughout the study. The data cannot be used for secondary purposes outside the consented scope, and access terminates when the study does.

No. Every access to participant data is logged and visible to the participant in real time. There is no silent data use. Participants can see which researchers or program organizers have accessed their data and when.

Research access is also scoped to the consent record. A researcher cannot access data types outside what the participant consented to for that specific study.

LLIF retains audit rights over all data partners and can terminate access immediately for violations. The Data Partner Agreement is not negotiable on core participant protection terms — there are no carve-outs.

Violations would also expose the partner organization to legal liability, since the agreement is a binding contract. LLIF takes compliance seriously as part of its governance obligation.

The governance structure, Participant Data Charter, and Data Partner Agreement framework are documented on the Governance page. The explainer pages cover specific topics in more depth: why nonprofit governance matters, what donor-restricted data means, and how consent works across the ecosystem.

If you have questions not answered here — about working with LLIF, running a study, building on the platform, or the governance structure — you can reach the team directly through the Contact page.