Kansoku
English日本語简体中文

Evidence and compliance

What a page showed, in which country, on which date — kept in a form usable as evidence rather than as an assertion.

When "we looked" is not enough

None of these survives on "someone checked." They need a record.

What is kept

Every observation is stored with the record of how it was obtained.

Time of retrievalretrieved_at, to sub-second
Country looked fromThe country named in the request
URL retrievedThe page actually read
HTTP statusWhether it was 200, or a 403 refusal
Rendered DOMThe state after JavaScript, as a person saw it
ScreenshotThe screen itself
Request identifierWhat ties it all together

Artifacts are retrieved through short-lived signed URLs, never from public object storage.

A refusal is not an empty result

When a source answers 403 or 429, it is recorded as a refusal — not as a successful read with nothing in it.

For evidence this distinction decides the conclusion. An empty result reads as "there was nothing there." The actual message was "slow down" or "not for you." Confusing the two later changes what you conclude.

Retention and deletion

Retention is configured per workspace and enforced by a scheduled deletion job, not by manual housekeeping.

Hold it for as long as you need, and it goes when the period ends. Neither "I thought we deleted that" nor "I thought we still had it" happens.

See Security for how this is implemented.

One thing to be clear about

Kansoku does not give legal advice. What constitutes a violation, and which records a tribunal will accept, is a lawyer's judgment.

What we provide is a record good enough to base that judgment on — when, from where, of what, with what result, in a form that can be checked afterwards. That is where our role ends.

Who uses it

Read about brand protection

Last updated