Argus for journalists

A reporter's browser is a liability. It carries your logins, your history, your newsroom's IP address — and every page you open for a story can read enough of it to know who is asking. The five situations below are where that costs you, and how the same research runs in Argus.

Isolation

Open the page without introducing yourself

Every Argus profile starts from its own directory — separate storage, cache and cookie jar, with nothing carried over from any other profile. The session you open to read a company's careers page, or a forum you are watching for a story, knows nothing about the session where you are signed into your email, your CMS, or your own social accounts. Session restore is disabled, so a previous run cannot resurface in a new one.

That cuts both ways, and both matter: the subject of the story cannot connect the visit to you, and your accumulated browsing cannot contaminate what the site decides to show the visitor. You see the page a stranger sees, not the page your history has earned.

Fingerprints

The machine they see is not the machine you own

Sites do not need a login to recognize you — the hardware is enough. Canvas, WebGL, screen, timezone, CPU cores: together they name your laptop nearly as reliably as a cookie. An Argus profile presents a generated hardware identity instead — platform, memory, screen, timezone and languages produced together as one coherent set, so nothing contradicts anything else. The spoofing is applied in the renderer, below the page: a script sees the spoofed value because that is the only value present, not because a wrapper hid the real one.

Each profile keeps its identity across launches. The account you use to watch a Telegram channel looks like the same believable machine every morning — just never like yours.

Proxies · WebRTC

Read the story from where it is happening

Prices shown only to one country, a politician's ads targeted at one region, a page that serves different text to different geographies — verifying any of it means arriving from there. Assign the profile a proxy from the shared library and the whole session arrives from that geography. Argus health-checks every proxy and reports the egress IP, its country, and the latency — and a proxy that fails its check blocks the launch entirely, instead of quietly falling back and stamping your newsroom's IP onto the visit.

WebRTC is sealed as browser policy on every profile — a page cannot read your real address around the proxy, and it is not a toggle you can forget to set. Authenticated SOCKS5, the variant plain Chromium cannot speak at all, is handled inside the browser.

Profiles · Cookie sets

A persona that survives longer than one afternoon

Monitoring a community for months means the account doing the watching has to stay consistent: same identity, same sessions, same logins. In Argus that persona is a profile — its cookies live in the profile's own jar, and a login saved as a cookie set is seeded into the session at launch, so the profile opens already signed in every time.

A beat becomes a folder of profiles: each row with its own status label and notes — which source it watches, when it was last used, what it must never be used for. Deleting is soft, so a persona retired at the end of a story can be restored if the story reopens.

Cloud sync · Teams

The investigation is not trapped on one laptop

Sign in with an email and password and your workspace follows you — the profiles, proxies and cookie sets are synced to your organization, not stranded on the machine where they were made. A desk working one investigation shares one pool: the colleague picking up your monitoring list opens the same rows you left, and two people working at once cannot overwrite each other.

When a story hands over — a reporter rotates off, a partner outlet joins — the handover is an account, not a folder of exported cookie files traded over email.