Trust
The page your compliance reviewer will ask for.
What the product refuses to do, each backed by a published mechanic: no token, no cross-site graph, no KYC. Most security questionnaires can be answered from the links below.
What we hold, and what we promise
- SecurityWhat orangecheck stores, what can move funds, and what happens if it disappears.
- CustodyWho holds each role today, what replaces it, and what has to happen first.
- PrivacyProperties you can check, side by side with Sign in with Google and Apple.
- RecoveryThe backup that runs, and what survives without us.
- Your dataEverything held under your identity, with an export.
- The charterEight commitments, including no token and no protocol fork.
Live numbers
- StatusEvery dependency, one verdict, from one check.
- EconomicsEvery sat the fee split has produced.
- Network numbersCapacity, economics, graduation and compliance on one page.
- ScaleThe ceiling at each layer, and the limit per app.
- ComplianceEach federation against the charter's custody rules, checked live.
- Check a receiptCheck any receipt against the published key, in your browser.
Records
The anti-gaming limits, in writing
Class A events per identity, per day
5- Why
- Bounds farming of new-account bonuses. Real people join a few sites a week.
Class A events per identity, per month
30- Why
- A monthly cap on durable state changes.
One site's share of a person's monthly earnings
≤ 60%- Why
- Stops one site inflating a person's earnings to make a wash flow look organic.
Review threshold, class A, per month
≥ $50- Why
- Above this, a person reviews the identity. Classes B and C are bounded by design and never trigger it.
Longest drop window
92 days- Why
- A site may batch payouts into drops, but none can hold a person's share longer.
The posture, in two paragraphs
Every envelope your project signs checks against Bitcoin without orangecheck online, using your published Ed25519 key and an OpenTimestamps proof. If orangecheck disappears, through acquisition, takeover, regulation or attrition, your project key is yours, your receipts keep checking, and the protocol carries on. The charter is the public version of that; how it works walks each mechanic.
Your users' accrued sats are a custody question, not a protocol one, and this page reads the answer rather than asserting it, in the same words your users see: “OrangeCheck holds your accrued sats during bring-up — it is operating every role until independent operators take them. Federation custody and graduation to your own keys are what replace it.” That half does not inherit the guarantee above: a balance is exposed to an acquisition or a shutdown to the degree orangecheck holds it. Security walks each scenario; custody has the full posture.
Questionnaires
Answering a security questionnaire?
Most answers are one link away above. For the rest, write to us and a person who built it replies.