Capture entire websites and Facebook timelines as court-ready evidence

Point Elite Assisted Capture at the site or the timeline and set the scope. Discovery maps up to 20,000 pages in a single pass, quickly, because it only reads. Capture is the slow part, so you run it in scoped batches rather than one enormous job: limit a run to a path such as /blog, filter by include or exclude patterns, or simply uncheck what you do not need in the review tree. Each captured page is preserved up to 500 screens deep. Facebook runs are bounded by your date range, up to All time.

Yes, and it keeps expanding during the capture. Each post is switched to All comments and every comment and reply is expanded, including threads that load while the capture is running. When the run finishes, it prompts you to verify the captures before relying on them.

Every plan, including Free, can run website discovery and export the Intelligence results. ELITE adds Facebook timeline discovery. Capturing the discovered pages and posts as evidence requires the Elite Assisted Capture plan.

The two halves are nothing alike. Discovery is quick because it only reads: one real run mapped 6,700 pages in 3 minutes 9 seconds, about 2,123 pages a minute, and discovery is free on every plan. Capture is the slow half, because each page is opened, expanded, and preserved in full, so a large timeline with complete comment expansion can be a multi-hour job. Run discovery first and you will know the exact size of the work before you commit any time to it.

Less than people expect, because it is a reconciliation rather than a file-by-file review. Discovery exports the approved list to CSV before capture starts, so verifying is confirming the run produced an item for every line you approved, and reading the short list of anything it could not capture, which is reported rather than dropped. You then open the captures you actually intend to rely on and confirm the comments, replies, and media you need are there. That same exported list is what you hand over as the record of what existed before capture ran.

Every screenshot, image, and MHTML file gets its own SHA-256 hash. UTC and local time, timezone, browser, OS, and extension version are recorded and burned into the capture. Captures run one at a time, each pinned to a single capture ID.

Switching tabs pauses the run and it resumes when you return. Locking the workstation pauses every run and it resumes exactly where it left off when you unlock, and minimising the window does the same. Simply walking away without locking does not pause anything, which is deliberate: long runs are meant to be left alone. If the page navigates somewhere else mid-capture, that capture is discarded rather than saved wrong.

One run per Chrome profile, and profiles are independent. A second Chrome profile is a separate browser context with its own copy of the extension, its own storage, and its own capture budget, so two profiles run two sweeps side by side on one machine. Keep both windows visible rather than stacked: a window fully covered by another stops producing frames, and a capture needs a live frame. Inside any one profile it stays one capture at a time, each pinned to its own capture ID, and each profile keeps its own captures until they sync to your case.

It works at the pace of a person reading, because a person reading is exactly what it stands in for: one request at a time, one capture at a time, unhurried scrolling and dwell times, and no platform API or scraping backend. That restraint is the point. Hammering a site is what actually creates a terms-of-service problem, and it is not how a lawful review of one subject behaves. The extension also shows a live detection-risk panel: it counts your captures for the day, warns you as the count climbs, and tells you when an account has not been warmed up before a run. Use the same lawful, authorized account you would use to read the timeline by hand.

Discovery records every item it finds, and that list exports to CSV, so you have a persisted record of what existed before capture ran. Items it cannot parse or that you skip are reported, not silently dropped, and you can capture them by hand. When a run finishes, it prompts you to verify the captures before relying on them.

Yes. Pause and resume, skip individual pages or posts, or stop entirely. Everything already captured stays saved.

Sites change constantly, and a change can temporarily affect a specific capture feature until we ship a compatibility update. That is the nature of every capture tool, ours included. In practice a fix usually ships within a day or two, and when someone is against a deadline we have several times issued that client a pre-release build the same day so they could finish the work in front of them. Meanwhile discovery still records what it found, and you can capture affected items by hand.

We avoid that term on purpose. Electronic evidence is authenticated by a person who can testify to what was collected and why, so describing a collection as having run on its own invites the obvious question of who the witness was. Platform terms that restrict "automated means" are aimed at bulk scraping: harvesting data to resell, to feed marketing, or to stand up a competing service. That is not this. Elite Assisted Capture exists for lawful investigations, criminal and civil, where an investigator examines a defined subject within a defined scope and preserves what they are already entitled to see. Assisted Capture is the accurate description: discovery proposes a list, you review and approve it, and capture runs only on the items you kept. You make every collection decision and you remain the witness to it.

Closer to the opposite: the human is the loop. "Human in the loop" normally describes a person reviewing decisions an autonomous system already made. Nothing here makes those decisions. There is no AI and no model anywhere in the capture path. The investigator sets the scope, discovery reports what it found, the investigator approves the list, and only approved items are captured. If your policy requires human review of automated collection, this meets it at a stronger point in the process: the review happens before anything is collected, not after.

Continuous Auto-Capture documents pages as you browse them. Elite Assisted Capture maps the whole target first, shows you the list, and then works through every item you approved. One records where you went. The other sweeps where you have not been yet.

Yes, both. Elite Assisted Capture is available in on-premise and single-tenant cloud deployments as well as the managed cloud. Capture itself never runs on our servers in any deployment: it runs in the investigator’s browser, in their session. The deployment choice governs where your cases and evidence are stored, which is usually the part a procurement or policy review cares about.

Every team starts with a 60-minute live training session, and we arrange further group sessions free of charge through the year as your people change and the product grows. Training videos are available on demand for anyone joining later. There is no separate onboarding fee.

No. It runs in your browser, in your session, and captures only what you can already see. No credentials are collected and no part of the capture itself runs on our servers.

Capture happens on the investigator’s machine, never on our servers. What happens next is your deployment choice. Captures are held locally in the browser until they sync, and they sync to the environment you bought: our managed cloud in Azure USA, a single-tenant cloud dedicated to you, or your own on-premise install where nothing leaves your network at all. Reports are generated and stored in that same environment. If your matter has a residency, retention, or legal-hold requirement, tell us before you buy and we will confirm in writing which deployment meets it.