Contribute data for credits

Every sanitized contribution strengthens the shared hardening corpus, the commons that lowers everyone's silent-wrong-effect rate. In return, you earn run credits that extend your usage allowance. This program is in early access while the terms are finalized, so you register interest and we grant access; there is no upload flow today.

Early access. Opt-in. Sanitized derivatives only.

Request access

The guarantees

Built to protect the contributor first

Sanitized derivatives only
You contribute a sanitized, de-identified derivative. Raw recordings never leave your machine or tenant.
You approve every byte
Nothing is shared until you review the exact bytes locally and approve them through hash-bound review.
Opt-in and under your control
The program is opt-in and off by default. You can stop future contributions at any time. Accepted contributions remain governed by the versioned terms you approved.
De-identification standard
Contributions are sanitized to a de-identification standard, and you attest that a contribution meets it.

How it works

The same sanitize, approve, ingest path you already use

A contribution references an already-approved sanitized derivative: the exact bytes that already passed local review and hash-bound approval. There is no separate upload of raw data, ever.

1
Record and compile locally
You record and compile a workflow the way you already do. The original recording stays on your machine.
2
Sanitize a derivative
A derivative is sanitized to a de-identification standard. You review it locally, not us.
3
Approve the exact bytes
You approve the sanitized derivative through hash-bound local review. Only that approved copy is eligible to contribute.
4
Contribute to the corpus
The approved, sanitized derivative passes manifest and runtime validation at ingest, then strengthens the shared hardening corpus.
5
Earn run credits
Your contribution earns run credits that extend your usage allowance. Not cash, and no per-record price.

What you get

Run credits that extend your usage allowance

Contributions earn run credits that extend your monthly run cap, the same cap shown on the pricing page. Credits are service credits that fund usage. They are not cash, there is no per-record price, and OpenAdapt does not buy your data.

Program status and eligibility

Gated on versioned terms, off by default

Status: early access. The contribution terms are versioned, and the contribution path stays off by default until a finalized terms version is active. The terms name the required de-identification standard, the contributor attestation, the jurisdiction scope, and the curation rules under which a contribution can be declined. Requesting access today registers interest only; it does not accept any terms, enable any upload, or share any workflow data. No customer or patient data has been collected through this program.

Eligibility. When access opens, contributions are accepted only from organizations that can attest, under the versioned terms, that each derivative meets the required named de-identification standard, that they have the right to contribute it, and that contributing does not breach their own downstream agreements. Sanitization alone is not a legal determination. Contributions are curated: a derivative that does not conform can be declined, and declined contributions earn no credits.

When you accept a terms version. Your acceptance records the exact terms version and timestamp. You can stop future contributions at any time; a contribution already accepted remains governed by the versioned terms you approved when you submitted it.

FAQ

Straight answers

Is my raw data ever uploaded?: No. Raw recordings never leave your machine. Only a sanitized, de-identified derivative that you have reviewed and approved is eligible to contribute.
Is this PHI?: The program accepts only derivatives that your organization has de-identified to the required named standard and attests are eligible to contribute. Sanitization alone is not a legal determination. If your organization cannot make that attestation, the derivative is not eligible and must not be shared.
Can I stop?: Yes. The program is opt-in and off by default, and you can stop future contributions at any time. A contribution already accepted remains governed by the versioned terms you approved when you submitted it.
What is the standard?: The required de-identification standard is named in the versioned contribution terms before access opens. Your organization attests that each derivative meets it, and you approve the exact bytes through hash-bound local review.
What do I get?: Run credits that extend your monthly run cap. Credits are service credits, not cash, and there is no per-record price.

Request access

Register interest in the contributor program

Tell us a little about your workflows and we will reach out as early access opens. Registering does not enable any upload or share any data.