← Back to the category

Financial platforms

Balances or positions at a broker or exchange when there is a concrete risk of a freeze or loss of access

Before exporting or capturing anything, leave passwords, private keys, recovery phrases and tokens out of the material. Store it securely and share it sparingly; never expose credentials to document a balance. Goal: preserve statements and screens when there is a concrete risk.

Create an account and start

The problem

This use applies only when there is material financial exposure and concrete signs of instability, blocked withdrawals, intervention or loss of access.

Distinguish the date a statement was issued, the moment of the capture and the actual position, which depends on the institution's records. Don't include passwords, private keys, recovery phrases or tokens.

The history of a broker or exchange account lives on the platform's own servers. While everything works, you just open the app. When withdrawals are blocked, an intervention happens or access fails, the screen that showed positions, deposits and withdrawals can disappear overnight. Rebuilding that history later from bank statements and memory is slow and incomplete.

This use case isn't for registering your portfolio every month. It makes sense when significant value is at stake and there are concrete signs of trouble.

What to preserve

Native CSV or PDF exports, balances, history, deposit and withdrawal receipts and relevant communications.

Goal: preserve statements and screens when there is a concrete risk.

Main file: a native CSV or PDF statement and a screenshot with context.

When to capture: when the statement is issued and when the screen is captured, keeping the two moments apart.

Supporting sources: the institution's own documents and records.

Limit of this scenario: on its own, the Record does not establish the actual economic position, an admitted claim or any recovery of funds.

Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.

Prefer the exports the platform itself generates, in CSV or PDF, because they keep the original format. Complete them with screenshots of balances and positions, with the date visible, and with deposit and withdrawal receipts. Also save the platform's emails and notices about freezes, maintenance or rule changes.

How Provenia documents this scenario

Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.

Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.

Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.

Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.

In this scenario, use a native CSV or PDF statement and a screenshot with context as your reference material and check it against the institution's own documents and records. The timestamp on a hash does not confirm the actual economic position, an admitted claim or any recovery of funds.

Step by step

  1. Before exporting or capturing anything, leave passwords, private keys, recovery phrases and tokens out of the material. Store it securely and share it sparingly; never expose credentials to document a balance.
  2. Distinguish the date a statement was issued, the moment of the capture and the actual position, which depends on the institution's records. Don't include passwords, private keys, recovery phrases or tokens.
  3. Preserve a native CSV or PDF statement and a screenshot with context exactly as it is; don't edit the file you register.
  4. Link the material to the institution's own documents and records; describe its origin and when it was captured as declared information.
  5. Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.

What the Record shows and what it does not

A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish the actual economic position, an admitted claim or any recovery of funds. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Should I register my balance every month?

No. Use it when significant value is at stake and there are concrete signs of risk.

How should I organize the files for this case?

Register the native export first, then the screenshots, and in each description state the statement's issue date and the time of capture separately. If you need a copy to share, redact account numbers in a separate file, note which version you registered and check that no credentials appear in either.

Which date is certified?

Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.

Official references

Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.

Start with three free credits

Before exporting or capturing anything, leave passwords, private keys, recovery phrases and tokens out of the material. Store it securely and share it sparingly; never expose credentials to document a balance.

Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.

Already have an account? Log in.

Create an account and start

Continue reading