What happens to my data if PHapp® changes ownership?

Minimal data, jurisdiction ownership, and commitments that carry over

Operational responsibility for a public service can change over time. PHapp® is built so that a change of operator does not put your data at risk.

There's very little data to begin with

PHapp® does not require an account to read alerts. If you turn on push notifications without signing in, we hold an id, push token and label for your device, a default language setting, and the subscriptions that route alerts to it. If you sign in, your Hub Account holds a display name (the name your sign-in provider shares, when it shares one), your email address once it is verified, a link to your profile photo if there is one, and which sign-in method you used and when, along with your settings, the subscriptions that route alerts to you, and, unless you opt out, usage records linked to it.

Agency data stays with the agency

Data tied to a jurisdiction — its content, configuration, and aggregate reporting — belongs to that jurisdiction, not to Hub or to any future operator. The jurisdiction can export or download all of it at any time, including before or during a transition.

Our commitments carry over

  • No selling of data, no ads, and no tracking — these are intended to bind any successor operator.
  • Resident and jurisdiction data is never treated as a saleable asset in a transfer.
  • Jurisdictions receive advance notice of any change of operator, with time to export their data.

PHapp® is built and operated by Hub Public Benefit Corp, a Delaware Public Benefit Corporation. These data commitments are part of how the service is designed, not tied to any single operator.