What Kiroku is

Kiroku preserves pages before they change, so the record can still be explained later.

A screenshot alone is often not enough. Kiroku keeps the page body, screenshot, save time, archive URL, external timestamp, and searchable context together.

What Kiroku keeps together

Not just a snapshot. A record you can revisit, search, and hand to someone else.

Kiroku captures the page and its visible appearance at the time you saved it.
The timestamp, archive URL, and context stay attached to the same record.
Later you can search it, compare it, keep it private in Pro, or package it for review.
Every save — Guest or Pro — automatically gets an external RFC 3161 timestamp right after capture, so the moment of saving is verifiable by a third party. Pro lets you download that proof as an evidence pack later, including for archives you originally saved as a Guest.

Why people need Kiroku in the first place

Kiroku is for situations where a page may matter later, but the live web will not wait for you.

Pages change after the moment that matters

Terms, pricing, notices, profile pages, and announcements are often updated, removed, or rewritten after the moment you first saw them.

A screenshot is hard to search and explain

Images help you remember, but they are awkward to search, compare, package, and hand to someone else cleanly.

Work begins after the first save

Later you may need to revisit the same page, compare changes, keep it private, or send a record to teammates, counsel, or clients.

How Kiroku records a page

One page becomes a set of records you can still use later.

Kiroku is designed so the archive is not trapped in one screenshot or one note. The page, its capture, and its context stay connected.

Screenshot

A visible capture of what the page looked like at the time of saving.

Self-contained HTML

An archive file you can reopen later instead of depending on the live page.

Timestamp

The save time is preserved alongside the archive so the moment can be explained.

Searchable archive

Find archives again by keyword, URL, host, or exact match instead of relying on a folder of files.

Archive URL and context

Each save has a stable archive URL plus the surrounding information needed to explain what was saved.

AI summary

A quick explanation of what the page contained so it is easier to triage later.

Why not just do this yourself?

DIY capture can still leave avoidable questions around the record.

If you keep records only in your own folder

You still need to explain who captured it, when, and whether the file was ever modified later.
Capture methods often vary by person, which makes the record harder to defend consistently.
It is easy to lose the relationship between the screenshot, the page HTML, the URL, and later versions.

When you record it through Kiroku

The save workflow is standardized, so the archive, timestamp, and context stay together.
The archive URL, page data, and screenshot are packaged in one place for later review.
It becomes easier to revisit, search, compare, and hand off the same record to someone else.
Kiroku does not replace legal judgment or guarantee evidentiary weight on its own. The point is to make the record easier to preserve, organize, and explain to a third party than a loose collection of in-house files.

Who Kiroku is built for

Legal and compliance teams

For teams that need to show what a page, policy, notice, or disclosure looked like at a specific time.

PR and communications

For people who need a usable record of announcements, campaign pages, and social content before it changes.

Research and investigations

For researchers who want something more reliable than scattered screenshots and copied notes.

Teams watching the same URL repeatedly

For anyone who expects the same page to change over time and wants that history to stay organized.

Pro

What Pro adds when archiving turns into ongoing work

Guest is enough for quick public saves. Pro is for the moment you need privacy, repeat monitoring, evidence-ready output, or archive management.

Open the Pro page

Private archives

Use Pro when a page should not live as a public archive URL and needs to stay inside your own workspace.

Typical use: client pages, internal reports, sensitive notices, drafts.

URL monitoring and diff checks

Use Pro when one save is not enough and you need to know what changed on the same URL next week.

Typical use: terms, pricing pages, press releases, product pages, takedowns.

Evidence-ready export

Use Pro when someone else needs to review the record and screenshots alone are no longer enough. Every save — Guest or Pro — automatically gets an external RFC 3161 timestamp, so the moment of capture is verifiable by a third party. Pro lets you download that proof as an evidence pack, even for archives you originally saved as a Guest.

Typical use: internal escalation, PR response, legal review, recordkeeping.

Archive management as ongoing work

Use Pro when archiving stops being a one-off action and turns into a repeat workflow.

Typical use: recurring monitoring, shared investigations, repeated competitive tracking.
Three moments Kiroku is built for

These are the moments that decide whether a record is usable — long after the page itself is gone.

The moment a term changes

A SaaS you paid for three months ago updates its terms of service without notice. Your cancellation policy changes, or a clause that was not there on signup appears in the new version.

Without a usable record
You remember the original terms but cannot show them. The vendor asserts the current terms apply. Without a record of the old version, your recollection does not hold up.
With Kiroku
If you saved the original terms page through Kiroku when you signed up, the HTML, screenshot, URL, and the save-time RFC 3161 timestamp are still there. Pro unlocks the evidence pack so you can hand the full proof to counsel or a consumer affairs office.
The moment a post is deleted

A defamatory post, a misleading ad, or a public statement gets deleted once the backlash begins. Screenshots are floating around, but no one has the URL, the surrounding profile state, or a verifiable save time.

Without a usable record
Reconstructing who posted what and when becomes a multi-day effort. Platform support, counsel, and insurance reviewers all want the original page, not passed-around images.
With Kiroku
If the page was captured early through Kiroku, the record exists with the URL, the rendered view, and a timestamp verifiable without trusting your own device. The reconstruction is already done — you just hand over the pack.
The moment a listing is swapped

A real estate listing, a job posting, or a product page you relied on quietly changes. The price, the photos, or the 'includes' list now differs from what you saw when you decided.

Without a usable record
You have no way to prove the original offering. Consumer affairs offices and platform dispute desks will ask for the original page — the page that now no longer exists in that form.
With Kiroku
Kiroku has the original save. Pro's URL monitoring catches the moment the page changes, and diff views make the exact change obvious to someone who was not there.
What Pro actually adds

Pro is not 'more saves.' It is three specific capabilities that start mattering after the capture.

Private archives tied to your account

Pro archives do not appear in the public /a/ feed and stay inside your workspace. This matters when what you are capturing is client material, internal drafts, or sensitive notices.

Monitoring + diff, so changes find you

You do not have to re-check the same URL every week. Kiroku watches it and captures a new version when the content actually changes, then shows the exact difference between versions.

Evidence pack that a third party can verify

The evidence pack ZIP bundles the archive, screenshot, manifest, and the RFC 3161 timestamp response. Anyone with openssl and the TSA's public certificate can verify the timestamp independently — without trusting Kiroku.

Retroactive evidence

The save you made today as a Guest can become evidence the day you upgrade to Pro — with the original capture time intact.

Timestamps are attached at save time, not at download time. That is why saving early — even on Guest — is the single most important thing you can do with Kiroku. You never know which page will be the one that matters three months from now.

Editorial standards

How Kiroku researches, verifies, and updates guides

Trust depends on showing how the information was produced. We make our source priorities, verification method, and refresh policy visible so both readers and AI systems can understand the context behind the page.

Primary sources first

Our guides prioritize official documentation, platform help centers, public institutions, and direct product verification over recycled summaries.

Visible refreshes

When features, platform behavior, or sources change, we update the body and the visible modified date together.

Claims tied to verification

Product explanations are based on direct saves, reproducible tests, or code-level verification rather than assumption.

No false certainty

We explain product behavior clearly, but we do not turn general information into legal certainty. Sensitive decisions still require professional review.

Need private saves, monitoring, or evidence-ready output?

The About page explains what Kiroku is for. The Pro page explains what happens when saving stops being a one-off action and becomes real work.