The Sovereign Suite controls what leaves your hands. The Record Suite does the opposite job: it captures what happened and keeps it intact, so you can show later that nothing moved. Same rule as everything else here. It runs in your browser, nothing is uploaded, and there is no account.
Most of the work that goes wrong in a dispute goes wrong quietly. A file gets re-saved and the date changes. A bundle gets copied to a shared drive and one page is different. Somebody says they sent version four and you have version three. None of that is dramatic and all of it is expensive.
A record made at the moment you receive or send something closes that gap. It costs one minute, and it turns an argument about what happened into a check anyone can run.
These tools are part of the Sovereign Pass. One pass covers every Sovereign Suite and Record Suite tool, $9 for 7 days or $9 a month.
Show that a set of files has not changed. Point it at files or a whole folder. It records the name, size, date and a SHA-256 digest of every byte, and gives you a manifest, a spreadsheet and a readable record sheet. Hand the manifest over with the files and the other side loads it here to see for themselves that what they received is exactly what you sent. If anything was altered, added or lost, it says which.
The page is also straight about the limits. A digest proves two files are identical; it does not prove when they existed or who made them, and the page tells you the one extra step that makes the timing checkable by somebody other than you.
Build a disclosure schedule from a folder. It lists every file with its type, size, dates and digest, then opens each one far enough to say what it is carrying. Who wrote it. Whether text was deleted under tracked changes and is still sitting in the file. Whether comments are still attached. Whether a photograph has GPS coordinates and a camera serial number in it. Whether a spreadsheet has hidden sheets. Whether anything calls out to a server the moment it is opened.
The output is a printable schedule, a spreadsheet, or JSON. It is the job somebody currently does by hand over two days, and it does not miss the fourth file in a folder of three hundred.
Keep a chain of custody. Record each exhibit with its description and its SHA-256, then log every hand-off: who took it, from whom, when, and why. Export a printable custody record, a spreadsheet, or a file you can load back and carry on with next week.
A digest proves an exhibit has not changed. A custody log says who was holding it while it did not. Neither is worth much on its own.
Write a statement and seal it. Who is speaking, in what capacity, what they say in numbered paragraphs, and the exhibits it refers to listed by digest. Sealing prints a SHA-256 of the text on the document and in a JSON sidecar, so anyone holding either copy can check that not a word has moved since.
It is a fixed text with a fingerprint, not a signature and not an oath. Print it and sign it the way your process requires; the seal covers the words.
Build a chronology. Events in date order with the source beside each one, and a plain label for whether a line rests on a document, on what somebody said, or on the author's inference. Attach the file an entry relies on to record its SHA-256, so the chronology and the exhibit list mean the same file.
Order is not cause. The tool sorts and labels; the reader draws the conclusions.
Bind exhibits into one PDF. Drop in the PDFs, photos and screenshots, put them in order, and get back a binder: an index whose entries click through to each exhibit, an exhibit sticker on the first page of each item, and a Bates number in the margin of every page. The index CSV records each source file's SHA-256 so the binder can be tied back to the originals.
It numbers, labels and indexes consistently. It does not know your court's rules; check the output against them before filing.
Turn a chat export into a numbered transcript. Drop in a WhatsApp, Telegram or CSV export and get one PDF: a cover that records the source file and its SHA-256, the period, the participants and the quiet gaps, followed by every message numbered in order with its timestamp. Filter by date or keyword first; photos from a WhatsApp zip are placed under the messages that sent them.
It reproduces the export faithfully and says so on the cover. It cannot verify the export itself; keep the phone and the original file where authenticity will be contested.
Find the dates a contract hopes you miss. It reads a lease or agreement in this tab, pulls out auto-renewal deadlines, notice windows and expiry, and exports a calendar file so the reminders land in the diary you already watch. It is not a lawyer; it catches what a skim misses.
Freeze a web page as evidence. It turns a page you saved into one self-contained file that cannot change or call home, fingerprints it with a SHA-256, and writes a capture record. The hash proves the copy is unaltered since capture; keep the original saved file.
Draft a removal notice that reads right. A DMCA takedown, a GDPR erasure request, a CCPA deletion request, or a plain demand for defamatory or doxxing content, with the statutory language these notices carry and your evidence listed by hash. A template, not legal advice.
It is not a timestamping authority, and it does not pretend to be one. A record made on your own machine is your own assertion until a third party dates it. Anything that claims otherwise, without a trusted timestamp service behind it, is telling you something it cannot deliver.
It is not a substitute for a preservation obligation. If you are under a litigation hold or a production order, that duty governs, and the Acceptable Use Policy spells out where the line falls.