Transactions between individuals
Private sale of a valuable item
Goal: document the visible condition when the item changes hands. If your material is older, keep in mind that a timestamp obtained today covers the hash submitted today. Documents from the time have their own dates and their own sources of proof; the Record does not certify the date of the event or the capture.
The problem
After the sale of a valuable item, one side disputes its condition, operation, damage, mileage or characteristics.
Keep old listing photos separate from the inspection done at the time. Link the identification details and the inventory to the handover document, without treating an old image as the current condition.
In a private sale, the inspection is usually quick and informal. Buyer and seller look at the item together, agree a price and close the deal. Later, when a fault or damage appears, each side remembers it differently. The listing photos are old, and the ones someone took on the day are loose on a phone, with no reliable date.
This works both ways. The seller wants to show how the item was handed over. The buyer wants to show how it was received.
What to preserve
A continuous video at handover, detailed photos, identifiers, mileage or serial number, and the contract or receipt.
Goal: document the visible condition when the item changes hands.
Main file: the inspection done at the time and the handover document.
When to capture: at the inspection and at handover.
Supporting sources: the item's identification, the inventory, the contract and the receipt.
Limit of this scenario: on its own, the Record does not establish hidden defects, or that the other side knew and accepted every condition.
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.
A continuous video, walking all the way around the item without cuts, shows the whole. Photos show the details: scratches, dents, screen, dashboard, accessories. The odometer, the vehicle identification number, the number plate or the serial number identify which item was handed over. The signed contract or receipt goes in as a document.
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 the inspection done at the time and the handover document as your reference material and check it against the item's identification, the inventory, the contract and the receipt. The timestamp on a hash does not confirm hidden defects, or that the other side knew and accepted every condition.
Step by step
- Define your goal and check that your access is legitimate, which permissions apply and whether any deadlines are running before you collect anything.
- Keep old listing photos separate from the inspection done at the time. Link the identification details and the inventory to the handover document, without treating an old image as the current condition.
- Preserve the inspection done at the time and the handover document exactly as it is; don't edit the file you register.
- Link the material to the item's identification, the inventory, the contract and the receipt; describe its origin and when it was captured as declared information.
- 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 hidden defects, or that the other side knew and accepted every condition. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
Who should create the Record, the seller or the buyer?
Either of them, or both. Each keeps their own originals.
How should I organize the files for this case?
Use one Project per sale. Register the handover video and the photos taken on the day as the main Records, with the signed receipt or contract next to them. If you add old listing photos, say clearly in the description that they come from the listing, not from the handover.
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.
- RFC 3161 — Time-Stamp Protocol (IETF)https://datatracker.ietf.org/doc/html/rfc3161
Start with three free credits
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.