Evidence ev_01m67f7ydffst04cmjaphv3wf1: Crusado company

This page shows one reading behind the statements on Crusado's page: what CasinoGuard captured, when and from where, how, and the files kept as proof, each with its SHA-256 so anyone can check it is unchanged.

• Evidence: ev_01m67f7ydffst04cmjaphv3wf1
• Topic: Company
• Source: crusado.com, T&C page (official)
• Scope: United Kingdom (GB)
• Captured: 2026-10-30 22:34 UTC
• Result: read, the first version of what the source states
• Read by: oasis-company@1

Crawl

• Crawl: 01m67f24tqbk2xzz9976b29c7f (done)
• Requested: 2026-10-30 22:32 UTC
• Started: 2026-10-30 22:34 UTC
• Finished: 2026-10-30 22:35 UTC
• Collected with: [email protected] running oasis-company@1
• Looked from: United Kingdom (GB) · Mobile · crusado.com · language en
• Proxy: pool uk-residential-di (Residential, GB)
• Exit network: not recorded (where the casino saw the visit come from)

View 2: terms

• Asked for: https://crusado.com/en/rules
• Landed on: https://crusado-e.com/en/rules
• Redirects: https://crusado.com/en/rules (307)
• HTTP status: 200
• Captured: 2026-10-30 22:34 UTC
• Steps: open_all every part of the terms (opened one by its title, then added its class (seo-accordion-active) to every part so the whole text shows at once; the site opens one at a time)

Full-page screenshot:

What it read

The reading as the worker sent it:

{
    "relations": []
}

How to check it

• The web archive is what the browser received during the crawl: every response with its request, and each view as rendered, listed as a page of its own (a crawl's views share one archive). Download it and open it in ReplayWeb.page to browse each page as it was.
• Each file's SHA-256 is that of the file when it was received; recompute it to check the file is unchanged.
• Cookies, logins and tokens are left out of every file, and so is the proxy's credential.
• The Markdown version and plain-text version of this page say the same.