Communications and temporary content
Important emails, proposals and business negotiations
Goal: organize a proposal, its attachments and any acceptance.
The problem
When money or a significant obligation is at stake, an email you sent or received may contain a proposal, condition, instruction, deadline, acceptance, attachment or commitment that could be disputed later.
Keep the exported email (.eml), each relevant attachment and the acceptance as separate items. Headers are an indication of origin; they don't prove who sent the message or that it was received.
The supplier sends a proposal with a price and a deadline, the client replies "go ahead", someone attaches the spreadsheet with the terms. Months later, when the project runs late or the invoice looks different, the questions start: what was the agreed price? Was that the attachment, or another one? Who said what, and in which version?
Email feels permanent, but inboxes get cleaned out, accounts are closed, people leave the company and attachments get replaced by "corrected versions". A loose screenshot with no headers and no attachment is usually easy to challenge.
What to preserve
Ideally the original exported email (.eml or equivalent), the relevant attachments and, when useful, a PDF or a screenshot with context.
Goal: organize a proposal, its attachments and any acceptance.
Main file: the email exported as .eml, with the attachments saved separately.
When to capture: at the relevant exchange, keeping whatever headers are available.
Supporting sources: the acceptance reply and the email provider's records.
Limit of this scenario: on its own, the Record does not establish who sent the email, or that it was received, read or accepted.
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.
The exported file carries the headers, which hold the declared sender, the recipients and the route the message took: indications to check against other sources. Attachments deserve their own file, because they usually carry the price, scope and deadline. A PDF or screenshot makes things easier for someone who won't open an .eml. Keep the file you choose intact; a derived copy is a different file and should be labelled as one.
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 email exported as .eml, with the attachments saved separately as your reference material and check it against the acceptance reply and the email provider's records. The timestamp on a hash does not confirm who sent the email, or that it was received, read or accepted.
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 the exported email (.eml), each relevant attachment and the acceptance as separate items. Headers are an indication of origin; they don't prove who sent the message or that it was received.
- Preserve the email exported as .eml, with the attachments saved separately exactly as it is; don't edit the file you register.
- Link the material to the acceptance reply and the email provider's records; 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 who sent the email, or that it was received, read or accepted. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
Isn't a screenshot of the email enough?
A screenshot helps people read it, but it loses the headers and attachments. Whenever you can, preserve the exported message and use the screenshot as a complement.
How should I organize the files for this case?
Register the .eml, each attachment that matters and the acceptance as separate Records in the same Project, in the order the negotiation happened. Give them neutral, descriptive names, such as "proposal v2 – attachment: price sheet", so anyone can see which attachment went with which message.
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.