Brand and business identity
Documenting earlier use of a brand, name or business identity
Goal: organize brand materials and the sources that show commercial circulation. 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
A business with commercial value and a risk of dispute wants to document material produced under a name, brand, identity or domain at a particular time.
Keep three questions apart: that a file existed, that it circulated commercially and who has priority. Trademark procedures are handled by the trademark office where you operate; documenting use doesn't replace those procedures or grant any right.
Small businesses often use a name long before formalizing anything. The first website goes offline when the hosting changes, old business cards end up in the bin, the menu artwork is redone. When a dispute arises, it's hard to reconstruct which materials existed at each point and in what order.
This use case makes sense when there is commercial value at stake and some risk of a dispute, not for registering every post.
What to preserve
The website, marketing materials, proposals, invoices or contracts where relevant, and other material from the time of use.
Goal: organize brand materials and the sources that show commercial circulation.
Main file: brand material and a commercial document from the time.
When to capture: at real milestones of use; for an older file, its origin still has to be shown.
Supporting sources: invoices, contracts and the procedures of the trademark office where you operate.
Limit of this scenario: on its own, the Record does not establish actual commercial use, legal priority or trademark rights.
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 material from the time itself: the catalogue PDF, a full capture of the website with the address visible, the final logo artwork, a proposal sent to a client, an invoice showing the business name. Keep the files as they were produced, without updating dates or logos afterwards.
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 brand material and a commercial document from the time as your reference material and check it against invoices, contracts and the procedures of the trademark office where you operate. The timestamp on a hash does not confirm actual commercial use, legal priority or trademark rights.
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 three questions apart: that a file existed, that it circulated commercially and who has priority. Trademark procedures are handled by the trademark office where you operate; documenting use doesn't replace those procedures or grant any right.
- Preserve brand material and a commercial document from the time exactly as it is; don't edit the file you register.
- Link the material to invoices, contracts and the procedures of the trademark office where you operate; 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 actual commercial use, legal priority or trademark rights. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
What can this Record be used to check?
Whether the file you kept matches the registered hash and, where there is a valid timestamp, that the hash is tied to the UTC date and time shown. On its own, it does not establish actual commercial use, legal priority or trademark rights.
How should I organize the files for this case?
Use one Project for the brand and register each real milestone of use separately: the logo file, the first website capture, the first invoice or proposal under that name. In each description, distinguish what shows the file existed from what shows it was used commercially, and say where that second proof lives.
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.