Our Data Promise
Plain English, no legalese. When a program or a community lets us build for them, they're trusting us with something that matters. Here's exactly how we treat your data — and what stays in your hands.
This is our standing commitment. The specifics for any engagement are written into that project's agreement — this page is the promise behind them.
The promise, in four lines
Your data is yours
The organizations and communities we serve own their data. You can export everything, any time — and nothing locks you to us. If you ever leave, you leave with your data.
We don't sell it, and we don't train AI on it
We never sell your data and never share it for advertising. We don't use it to train AI models. We use only what's needed to run and improve the tool we built for you.
The community keeps the authority
When we work with a Tribe or a Native-serving program, the community decides how its data is used, who can see it, and when to revoke access. That authority is yours, not ours.
We collect as little as possible
We keep what we collect to a minimum, we tell you what it is, and we keep it under access controls. Less data held is less data at risk.
Indigenous data sovereignty — we support yours
Data sovereignty is a community's right to govern its own data. It belongs to the community, not to a vendor — so we don't claim it as a credential. What we do is build so that your authority over your data is real and stays real after we're gone.
We design to align with the principles Native data governance is built on:
| CARE Principles | Collective benefit · Authority to control · Responsibility · Ethics. The data works for the community's benefit, under the community's control. |
|---|---|
| OCAP® | Ownership, Control, Access, Possession — the First Nations data-governance standard. We build so each of these can sit with the community. |
| Consent before sharing | Nothing crosses an agency or organizational line without explicit consent. Cross-agency sharing is something you turn on, not a default. |
| Built where the work happens | Role-based access separates public, internal, and sensitive data; sensitive and health data is handled only under explicit consent and a governance agreement, built together with you — never ahead of you. |
What we actually collect
Different tools, different data — but the rule is the same: the minimum, told to you plainly.
Community apps (like Olen Hub)
Basic, mostly anonymized usage — which features get opened — so we can make the app better. Aggregated and de-identified, it can also help the community’s own programs see what residents need — at the community’s direction, and never shared outside it. No selling, no ad-sharing, no profiles sold to anyone.
Program & grant systems
The records the program already runs on (applications, reports, intake). They stay under the client's ownership, with role-based access so people see only what their role allows.
Sensitive & health data
Handled only with explicit consent and a written governance agreement, on access-controlled cloud, with HIPAA-aware engineering. Built with you when a real need exists — not collected "just in case."
How this looks in a real build
This isn't a slogan. We built and deployed an integrated grant platform across all eight North Slope Iñupiat villages with the Arctic Slope Community Foundation — with client-owned data, role-based separation, and consent before any cross-agency sharing, from the start. We wrote up what that looks like in practice:
Read: Tribal data sovereignty, built into the software ›
Questions about how we'd handle your data?
Ask us anything — before there's any agreement on the table. We'd rather walk your team through the specifics than have you guess.
Start a conversation