Skip to content

Trust

Who holds what, and what you can check yourself.

Each answer is read from the running system, not written for this page.

Custody now

orangecheck holds what you earn while payouts are in testing, and every key that can move it.

  1. Todayorangecheck
  2. Planned · not builtGuardians
  3. Planned · not liveYou
Your sign-in key
You, with a bitcoin wallet; orangecheck, with email
Your earned sats
orangecheck
Sending payouts
orangecheck's executor
The key that signs settlements
orangecheck's executor
Guardian seats
No guardian seats yet
Receipt signing
orangecheck, always

A receipt proves an app recorded what it owes you, signed by orangecheck. It is not a claim on funds, and there is no solvency proof yet.

Every role, and what replaces it

Data and funds

What we store, and what can move funds

01 · What we store

  • Your account id
  • A display name
  • How you sign in: an email, encrypted, with hashes to find it, a Google or GitHub id, or a Bitcoin address, which is public anyway
  • Your passkeys’ public keys
  • The device of each session, and which sessions share a browser
  • The IP address of each sign-in, which is cleared after 90 days
  • A coin backing your account, if you add one
  • Events apps send about you, receipts and app settings

02

No password.No private key.No recovery phrase.

03 · What can move funds

Nothing orangecheck runs can move your own wallet: its keys never reach us.

What you earn here is different. Today orangecheck holds every key that can move funds. Payouts are in testing, so no sats move yet.

Where your data goes
  1. You to an appYour session: your account id, the same in every app, and anything you chose to share.
  2. An app to orangecheckWhile it pays its users: each event it sends about you, kept whether or not it was charged, with your account id, when it happened, your share, and any note, label or payment amount the app adds. That is how your share reaches you.
  3. orangecheck to youA line in your activity: the app, the event, what you earned, and a link to check its receipt.
  4. orangecheck to everyoneEach paid receipt’s hash, anchored to Bitcoin, and a salted commitment to it on Nostr. Neither names you, the app or the amount. The receipt itself goes only to whoever holds its id.
What this site keeps in your browser
__Host-oc_session
Your session here: a sign-in token for this site alone. Sent to ochk.app and nowhere else, and no script on the page can read it. It ends when the token expires or you sign out here.
__Host-oc_also_0__Host-oc_also_1__Host-oc_also_2
Up to three other accounts signed in in this browser, so you can switch to one. Each holds that account’s sign-in token, out of reach of page scripts like your session, and ends when that token expires or the account signs out.
__Host-oc_active
Which account you are using: its account id, which this site’s own page script reads so a reload draws that account’s places at once. Access never rests on it. It lasts as long as your session.
__Host-oc_oauth
Only while you sign in with Google or GitHub: a one-time check that the sign-in coming back is the one you started. Deleted as you land, ten minutes at most.
__Host-oc_handoff_guard__Host-oc_handoff_<state>__Host-oc_to_io
Only while a sign-in passes between ochk.app and ochk.io: what it needs to come back to the page you started on, to stop a failed one looping, and to tell it apart from one another site started. Two minutes at most.
oc_logo
Which of our two logos you chose, set only when you open a page with ?logo= in its address, and kept for a year. ?logo=classic deletes it.
In local storage
Light or dark, under theme. The code tab you last picked. Your alert switches on the account page and, on the balance page, when and where to suggest moving your balance, as this browser last saw them. The setup steps you ticked, in the quickstart and on each of your projects’ pages. For each account signed in here, which of its areas it could open when last checked, so a reload draws them at once; every page still checks on the server. ov_ignore, only if you opt out below. A tab also keeps what a sign-in, a Google or GitHub link, a sign-out, a claim, a check or a write in progress needs, until it closes. Unlike cookies, your browser attaches none of this to its requests; our scripts send a piece of it only in the request that uses it.
In IndexedDB
Only if you make, restore or import an operator key on the operator page: the key pair, its operator id, when it was added here, whether it was made in a browser or imported from the kit, and the version of the record, in oc-operator-key, filed under that account’s id until you delete it there. No request carries the private key; our scripts read it here to sign your operator actions, and show it to you only when you ask.

No tracking cookies, no advertising ids, no third-party pixels. Page views are counted without cookies by our own beacon at insights.ochk.io, and by our operations dashboard at overlook.technology, which never stores your IP address. To opt out of the second, open any page with ?ov_ignore=1.

Where records are kept, and what if we disappear

Privacy

The formal version is the privacy policy.

Sees which apps you sign in to
At sign-in, to mint that app’s token. For its caps it keeps, per token, a keyed hash of your account and that app, and one of your account alone. Once a day old they are deleted as later capped actions run, so after a quiet spell they can stay longer. For an app registered with orangecheck, it also records that you signed in there, kept with your account, so the app can name you as its earner.After that, each app checks your session itself.
Builds a graph of you across apps
We build no cross-app graph and sell none. Today that is policy, not cryptographyEvery app gets the same account id, so two apps that compare notes can match you. Our own records link what apps pay you, because that is how it reaches you.
Advertising tied to you
No
What you give to sign up
Nothing with a Bitcoin wallet. Or an email address
Keeps out fake accounts
Accounts backed by bitcoin their owner holds
Hold what you earn yourself
Not yet. Payouts will go to a Lightning wallet you choose
Records that outlive the provider
Yes. Anchored receipts check against Bitcoin, without us

Delete your account from your account. Deleting does not pay out what you have earned; while payouts are in testing, a balance above zero is settled by hand first. Hashes on Bitcoin and commitments on Nostr can't be changed, and neither names you.

Live numbers

The numbers the charter commits orangecheck to publishing, read as you load this page.

Guardian federations runningNot counted: the test network (one key, testnet)
0 of 1
Limit today, events a secondSet by the event store. Federations settle payouts, not each event: 100 to 500 a second each.
600 to 770
Events a second, last 5 minutes0 events, under 0.01% of one app's cap
0.00
Receipts, all timeSigned receipts for paid events, network-wide
0
  • Sats in and out
    No platform fees accrued or paid out yet, and orangecheck's treasury is empty. Nothing is simulated or back-filled.
  • Charter check
    1 guardian federation, 0 running, plus the test network (one key, testnet): none blocked, 1 warning.
    In full
  • Capacity, layer by layer
    The limit of every layer, and how much of it is used.
    In full

Questionnaires

Answering a security questionnaire?

Most answers are on this page. For the rest, write to us and a person who built it replies.

Write to us