Data & Cultural Stewardship

The Cultural Significance of Hula Data

Hula lineage, mele, and oli are not just records — they are sacred knowledge entrusted from one generation to the next. A hālau’s data represents the living memory of its tradition: the names of kumu who carried the knowledge forward, the texts and melodies preserved through practice, and the histories that give each hālau its identity. Protecting this data is not a technical exercise. It is a cultural obligation.

Data Minimization

We collect only the data necessary to operate the platform and serve your hālau. We do not collect Social Security Numbers, driver’s license numbers, bank account numbers, or full credit card numbers. Payment data is tokenized by Stripe and never stored on our servers. If a data point does not serve your hālau’s needs, we do not ask for it.

Permission Layers to Protect Sacred Knowledge

Not all hula knowledge is meant to be shared openly. The Hula Binder™ supports granular permission layers so each hālau can control who sees what. Sacred mele and oli can be restricted to specific roles, ensuring that sensitive cultural materials are only accessible to those who have earned that access within the hālau’s own protocols.

Hālau Data Isolation

Every hālau’s data is isolated using Row-Level Security (RLS) at the database level. This means one hālau can never see, access, or interact with another hālau’s data — not through the interface, not through the API, and not through any administrative tool. Isolation is enforced by the infrastructure itself, not just application logic.

Your Hālau’s Data Rights

Your hālau has clear, codified rights over its data:

• • Ownership — Your hālau owns all data entered into the platform. Haumea Technologies LLC is a steward, not an owner.
• • Export — Export your data in CSV or JSON at any time from the Admin dashboard, or request a complete archive via email within 7 business days.
• • Portability — Your data is structured for easy migration to any other system.
• • Deletion — Request permanent deletion at any time. Written confirmation is provided once deletion is complete.

Continuity of Service

The Hula Binder™ is built for the long term. We have established the following continuity measures:

• • Emergency credential access stored in a shared password manager, accessible to a designated trusted party
• • A named successor for Haumea Technologies LLC in the event something happens to the founder
• • A minimum 90-day operating reserve to sustain platform operations during any transition
• • Complete operational documentation for platform maintenance, deployment, and infrastructure management

Wind-Down Protections

If the platform ever needs to wind down:

• • Minimum 90 days written notice to all hālau
• • Full data access maintained throughout the entire notice period
• • Migration assistance provided at no cost
• • Complete data archive delivered before any infrastructure is decommissioned
• • Written deletion confirmation after data is permanently removed

Ongoing Commitments

• • Annual transparency report shared with every hālau on the platform
• • 90 days advance written notice before any pricing change
• • Open feedback channels — your voice shapes the platform