Academic submission proof · originality record
Submitted it. But what if someone questions when — or whether — it was yours?
A sealed, timestamped record of your work before submission is the answer to "how do I prove I submitted on time?" or "how do I show this was mine?". One record, created before the question arises.
Before you submit your assignment, thesis, or capstone project — create a tamper-evident record of it.
One sealed file with a timestamp and a SHA-256 fingerprint.
If anyone ever questions whether you submitted your own original work, or when exactly you submitted it —
the record answers, without you needing to say a word.
1
Upload your file (locally)
No file upload to our servers
SHA-256 fingerprint
Tamper-evident
$19.99 one-time
Three situations where this matters
You do not know when you will need it. That is exactly why you create it before submitting.
📝
Plagiarism allegation
Your professor suspects your essay is not your own work. You try to prove you wrote it — but all you have is your email drafts and a Google Doc with no clear history.
A sealed record shows the SHA-256 fingerprint of your file, the timestamp of when you sealed it, and the exact content — unchanged since you created it. The record speaks for itself.
⏰
Late submission dispute
The university system shows you submitted at 11:58 PM, but you claim you tried at 11:43 PM and hit a technical error. Your word against a system timestamp.
A pre-submission seal shows your file existed and was ready at 11:43 PM — before any system error. The record establishes the timeline independently of the platform.
🔄
Version confusion / co-authorship dispute
A group project goes wrong. A team member claims you submitted their version as your own, or that you changed the file after the deadline.
A sealed record per version shows exactly what was in the file at each point in time — proving what you submitted and when you submitted it, down to the byte.
What to prepare — what you receive
Simple in, clear out.
📋 What you need to provide
📄
Your file
The assignment, thesis, or project file — PDF, DOCX, ZIP, any format. It stays on your device. We compute a fingerprint locally, we never receive your file content.
🏫
Course or module name
e.g., "COMP-3400 Algorithms Final Project" or "MSc Dissertation — University of Leeds"
📅
Submission deadline
The deadline date from your course. This helps context the record — it is not verified, just recorded as declared.
💬
One sentence about the submission
e.g., "Final submission of my own original work for the group project, version 3, completed independently." This becomes the reviewer summary.
👤
Your name or student ID
Just enough to identify the record. No sensitive personal data required.
✦ What you get back
🔒
Sealed record with SHA-256 fingerprint
A tamper-evident fingerprint of your file. If anyone modifies the file after this moment — even by one character — the fingerprint will not match. Mathematically provable.
⏱
Server timestamp
The exact moment the record was sealed — independent of your device clock. ed25519-signed by Vraimony servers. Cannot be backdated.
📦
PDF + PNG + JSON exports
Download your sealed record as a PDF to attach to communications, a PNG for quick sharing, and a JSON for technical verification. All three are yours, forever.
🔗
Verify link
A unique URL anyone can open to confirm the record is genuine — your professor, the academic committee, or yourself. No account needed to verify.
📊
Status labels: Declared / PASS / Unverified
Every claim in the record is honestly labelled. What you stated is "Declared." What the server confirmed is "PASS." Nothing is hidden or overclaimed.
How it works — step by step
Four steps. Under five minutes.
1
Finish your work as normal
Complete your assignment exactly as you would. Vraimony does not change how you work — it adds a layer of proof on top of what you already do.
e.g., final-essay-v3.pdf ready to go
2
Fill in the submission record
Add your course name, deadline, a one-sentence description of what you're submitting, and your name or student ID. That's it — five fields, two minutes.
e.g., "MSc Data Science — Final Project — own original work"
3
Select your file — fingerprint computed locally
Your file never leaves your device. We compute a SHA-256 hash in your browser — a unique fingerprint of the file's exact content at this exact moment. Only the fingerprint is sent to our servers, not your file.
SHA-256: e3b0c44298fc1c149afb... (64 characters)
4
Seal — then submit your assignment normally
The record is sealed with an ed25519 server signature and timestamp. Download your PDF, JSON, and verify link. Then submit your assignment to your institution as usual — nothing changes on their end.
Record sealed. Submit to Turnitin / Moodle / email as normal. ✓
Quick check — do you need this?
Tick what applies to your situation.
If you tick 3 or more, creating a submission record before you submit is worth the five minutes.
Tick the boxes above
0 / 8
Select what applies to your situation.
Pricing — simple
One submission. $19.99. No subscription.
Free draft
$0
Local only — not sealed
- SHA-256 fingerprint computed locally
- JSON record on your device
- Not server-signed
- Not tamper-evident to third parties
- Cannot be independently verified
Try free draft
Good for practice. Not for use if you need real proof.
Most used
One sealed record
$19.99
One-time · no subscription
- Server-signed with ed25519
- Tamper-evident timestamp
- SHA-256 fingerprint sealed
- PDF + PNG + JSON exports
- Verify link (no account to open)
- PASS / Declared / Unverified labels
- Yours forever — no recurring charge
Seal one submission →
Pro — multiple submissions
$39
Per month · unlimited records
- Everything in One Case
- Unlimited submissions per month
- All template families
- Best for final year with many deadlines
See Pro plan
Most students only need One Case.
What this does not do
We package facts. We do not create them.
A sealed record proves that a file with this fingerprint existed at this timestamp. It does not prove authorship, originality, academic quality, or legal innocence. It is one honest piece of evidence — not a magic shield.
✕ Does not prove you wrote it
✕ Does not guarantee any academic outcome
✕ Does not replace your institution's processes
✕ Does not provide legal advice
✓ Proves the file existed at this timestamp
✓ Proves the file has not changed since sealing
✓ Provides a tamper-evident, independently verifiable record
When is this most useful? When the dispute is about when something was submitted, what version was submitted, or whether the file was modified after the fact. For disputes about authorship or originality, the record is one supporting piece — not a complete defence on its own.
Ready to seal your submission?
Five minutes before you submit.
Peace of mind for as long as it matters.
Create the record before you send the file. The record costs less than a textbook chapter. The alternative — trying to prove what you submitted after the fact — costs far more in time and stress.
We improve review-readiness. We do not control the outcome. No subscription, no hidden fees. Export everything, always.
Decision layer — what stops and what advances your submission record
One thing that blocks the review. One thing that unblocks it.
⛔
One Invalidate — what makes this record unactionable
If the file you seal is not the same file you submitted — even one character changed after sealing — the SHA-256 fingerprint will not match, and the record provides no proof of your original submission. The seal is only useful if it is created from the exact file before submission.
❖
One Next Evidence — what advances the case most
A system-generated submission receipt from your institution's platform (Turnitin, Moodle, Canvas, or email timestamp). This confirms not just that the file existed, but that it was received by the platform at a specific time. Combined with the Vraimony seal, this pair establishes both existence and delivery.
Quality stops — states this record cannot claim without these
✕No "Submission proved" without sealing the exact file before submission — sealing after is not proof of what was submitted
✕No "Tamper-evident" claim for a free local draft — only a server-sealed record ($19.99) is independently verifiable
✕No "Authorship proved" — this record proves file existence and integrity, not who wrote the content
✕No "Academic outcome guaranteed" — the record supports your case but does not determine the institution's decision
■ Facts — what the record contains
- SHA-256 fingerprint of your file
- Server timestamp (sealed moment)
- Course / module name
- Your student identifier
- Submission description (declared)
▶ What this means for the committee
- This file existed before the submission deadline
- The file has not been modified since sealing
- The seal is independently verifiable
- Timeline is server-certified, not self-reported
► What the committee can do now
- Verify the seal independently at verify.vraimony.com
- Confirm the file fingerprint matches the submission
- Use the timestamp as evidence in timeline disputes
- Request further information if declaration is disputed