Never hold your assets
The file is built from read-only exchange access and the public addresses of your wallets. CashoutReady never asks for a seed phrase, a login or an API key that can trade or withdraw.
A Source-of-Wealth file needs the most complete picture of your crypto life that exists anywhere: every exchange, every wallet, every transfer. CashoutReady is designed so that this picture stays out of reach of anyone who does not need it, inside ChainComply as much as outside it, and does not outlive your case unless you decide it should.
Nothing CashoutReady holds can move a coin.
Each one holds for every case, from the Simple check to the Full SoW Claim Kit.
The file is built from read-only exchange access and the public addresses of your wallets. CashoutReady never asks for a seed phrase, a login or an API key that can trade or withdraw.
Ninety days after delivery, the file, the map and the data behind them are deleted. If you want them kept for the next bank, they are encrypted with a key only you hold.
No need for your passport, because your bank already has it, and with the anonymity add-on you can work under a code name. Identity documents are collected only with the KYC add-on.
Who you are and what you hold sit in separate stores. They are brought together only when the case needs it, with a full audit log.
No single store holds both who you are and what you hold, and the case data has a fixed end: ninety days after delivery, unless you choose to keep the file under your own key.
Once the case is closed, you can ask for the case data to be deleted sooner. Invoices are kept, because accounting law requires it.
The file is built to be shown, but only by you. Nothing reaches your bank or anyone else unless you send it.
The interactive map opens from a link you share with your bank. It expires with the file after 90 days, and you can switch it off sooner.
Your data is used for your case and for nothing else. It is not sold, and it is not passed on.
You receive the file and the interactive map, and you decide who sees them.
An analyst at ChainComply reviews the reconstruction before the file reaches you, and works on it under the case reference.
Your bank sees what you send it. With the Full SoW Claim Kit, it can also ask ChainComply to confirm that the file is authentic and unchanged.
Third-party providers retrieve and augment the transaction data and screen addresses for illicit-activity indicators, so that nothing your bank finds comes as a surprise.
A code name protects you against one provider holding your identity, your addresses and your net worth in the same place. It is anonymity towards CashoutReady, never towards your bank: the file is built to be shown, in your name, to a bank that already knows exactly who you are.
| What CashoutReady knows | In your name | Under a code name | With the KYC add-on |
|---|---|---|---|
| Your name and contact details | Kept only for the invoice, as long as tax law requiresApart from the case data | Not known: an alias and a channel you choose | Kept for 10 yearsApart from the case data |
| Identity documents | Not collected | Not collected | ID or passport photo |
| Wallets, exchange histories and their value | Known while the case runs, under a case reference, whichever way you engage | ||
| After delivery | Deleted at 90 days, or kept under your key, whichever way you engage | ||
A code name comes with DataPatrimony, and with the Full SoW Claim Kit as the anonymity add-on.
The engineering behind these rules is not published, to reduce the attack vectors against client data. Data is hosted in the EU, and CashoutReady does not publish how it is encrypted, how keys are handled or who can access what.
The case desk takes you, your tax adviser or your bank through the set-up on request.
No. CashoutReady never asks for them and never needs them. The reconstruction runs on read-only access and public addresses, and nothing it holds can move funds.
Because a bank cannot tell an edited export from an honest one, and banks say so: a CSV can be easily modified. Read access pulls the history from the exchange itself, and every figure in the file traces back to the record or the chain it came from. Where an exchange offers no read access, its exported history is used instead.
The file, the map and the data behind them are deleted. If you chose to keep the file, it is encrypted with a key only you hold instead. Once the case is closed, you can also ask for deletion sooner.
Then the kept file cannot be reopened, by you or by ChainComply. A key that nobody else holds cannot be recovered by anyone else either, so keep it somewhere safe. You will need to recreate your case.
Yes, if you have the Full SoW Claim Kit: the bank can contact ChainComply to confirm that the file is authentic and unchanged. The file remains your claim, so a bank usually verifies it independently as well.
The only data that leaves ChainComply goes to the third-party providers that retrieve and augment the transaction data and screen addresses for illicit-activity indicators. Nothing goes to your bank unless you send it, and the data is never sold.
In the EU. The rest of the hosting set-up is not published, to reduce attack vectors. Identity and case data are kept apart, and the case desk can take you through the details.
The first call is free and needs no data at all. The case desk can take you through the set-up before a single wallet address is shared.