Privacy notice

Version 2026-10-01. Plain-language summary of what this site collects, why, and the controls you hold over it.

Who runs this

This site is maintained by organizers of an independent claims registry for customers of the exchange in its announced wind-down — a community-run resource not affiliated with the exchange, its advisers, any committee, or any law firm. For privacy law purposes (GDPR and equivalents), the organizers act as the data controller for submission records. Most rights below are self-service and do not require contacting anyone.

What we collect

Only what you choose to type or upload in the intake form:

Claim fields: an optional contact (pseudonymous handles are fine — a real name is not required), claimant type, claim-status bucket, amount range, asset class, jurisdiction, withdrawal request IDs, last attempt dates, holdings summary, and your narrative.
Attachments: only the files you select — e.g., a CSV account export and a balance screenshot. These are sealed in your browser before upload; the server stores ciphertext.
Parsed holdings: if you upload a CSV export, a parser in your browser previews a normalized table; only rows you explicitly confirm are serialized into the sealed payload. The raw file itself is also sealed if uploaded.
Optional public-status opt-in: if you check it, a whitelisted subset (claim status, asset class, amount range, a "registered" marker, and the date) is shown on the public status board. Nothing else is published.

What we do not collect: no IP address stored, no user-agent logged to your record, no cookies, no analytics, no trackers, no third-party beacons. The abuse gate is either a Cloudflare Turnstile token or a local proof-of-work (ALTCHA) — the latter identifies nothing about you.

Minimization — by design and by request: do not upload government ID, do not include your exchange password or seed phrase anywhere, and redact your account email in screenshots if you prefer. We do not want identity documents; balances and statuses are what matter. If an attachment incidentally contains such material, note it in your submission or revoke and resubmit.

Why we collect it

To build a quantified, categorized claims register — how many claimants, in which buckets, for roughly how much.
To make the ledger available to a duly-constituted claimants' committee, its counsel of record, or a court-appointed claims agent — only under the consent state you choose.
To let you verify, correct, or remove your own record at any time.

We do not use submissions for advertising, profiling, or any automated decision-making. There is none.

Legal basis — multi-jurisdiction

Claimants are spread across the US, Cayman Islands, St. Vincent & the Grenadines, the EU/EEA, Singapore, Hong Kong, and elsewhere; rights differ by jurisdiction, and we aim to honor the strictest common set for everyone:

EU/EEA & UK (GDPR): processing rests on your consent (Art. 6(1)(a)) and on the legitimate interest (Art. 6(1)(f)) of organizing affected claimants' claims and preserving evidence. Withdrawing consent does not undo processing already done — but because your record is sealed to you, almost nothing is processed in readable form until you say so.
Singapore (PDPA) / Hong Kong (PDPO): collection is consent-based; you may withdraw consent and request access, correction, or deletion — the self-service controls below implement all three.
US: no comprehensive federal regime applies, but we extend the same access/deletion controls to everyone. State-law rights (e.g., CCPA/CPRA for California residents) are honored through the same self-service mechanisms.
Cayman / SVG and elsewhere: the same controls apply — they are designed to satisfy the strictest regime rather than the laxest.

Sealed model caveat: because content is ciphertext at rest, "access" and "erasure" operate on the sealed record — your self-key is what makes it readable, and deletion removes the ciphertext. This is a stronger guarantee than most processors offer, and it also means we cannot read out your record to you ourselves.

Who can see your record

Licensed (default): your submission stays ciphertext in storage; releasable to a duly-constituted claimants' committee, its counsel of record, or a court-appointed claims agent or insolvency officeholder.
Sealed private: ciphertext only; no one reads it. Aggregate counts may still include it.
Released: the receiving committee/counsel may decrypt for the claims process.
Revoked: deleted everywhere we host it.

You move between these states yourself — see below.

Your rights and how to use them

Right	How
Access	Manage your submission → enter your receipt → your ciphertext is returned. Decrypt it locally on Verify a proof.
Rectification	Submit a corrected record with the same details — deduplication keys on your field content — or ask organizers to annotate.
Erasure	Manage your submission → Delete my submission. Removes the sealed record, escrow key, public listing, and every uploaded file, and writes a content-free tombstone so the ledger can mark consent revoked without keeping your data.
Restriction	Manage → Keep sealed private — processing stops; the record stays unreadable.
Portability	Your receipt retrieves your full encrypted record — it is your copy, decryptable only by your key.
Objection / complaint	You may object to or complain about processing. EU/EEA residents may complain to their national supervisory authority; UK residents to the ICO; Singapore residents to the PDPC; Hong Kong residents to the PCPD; others to your local authority. You can also act on your record directly — deletion does not require anyone's approval.
Takedown / correction	Erasure above is the takedown path for your own record. To request correction of site content, use the private form with supporting evidence — verified corrections are incorporated.

Your receipt is the credential. Treat it like a password.

Where data lives and for how long

Records are stored on Cloudflare's network (Pages Functions + KV + R2), which processes data on globally distributed infrastructure. All claimant content is stored as ciphertext — sealed in your browser before transit — so storage location does not expose contents. Records persist until you revoke them or the claimant effort concludes, after which remaining sealed records will be deleted or destroyed. Tombstones (timestamp + action only) may be retained to keep the ledger's consent audit honest.

Security

Field payloads, PII, and file bodies are sealed in-browser (libsodium sealed boxes); the server never receives plaintext or a decryption key.
TLS in transit; ciphertext at rest; no IP/UA written to your record.
Organizer decryption keys live outside this infrastructure.

Caveat we won't hide: copies already decrypted into a receiving party's private archive before a revocation are outside what this site can delete — the consent states exist so release happens only to a process you've chosen. Full detail in SECURITY.md in the repository.