Trust, security, and limits

Know the operating boundary before the investigation begins

The Argus founding pilot is deliberately bounded: a dedicated workspace, named users, public and non-sensitive material, documented support, and human editorial responsibility.

Review the pilot Apply for assessment

Source trail

One research artifact, end to end

Editorial control retained

Public sources
Documents, reports, web pages
01
Argus workspace
Analyse, summarise, translate, query
02
Editorial brief
Cited, reviewable, human-approved
03

Direct answer

How does Argus handle newsroom data during the founding pilot?

Argus uses a dedicated pilot deployment with access limited to named users. The founding pilot accepts public, non-sensitive material only. Vorbtech documents backup, recovery, support, retention, deletion, and AI-provider handling before active use. The newsroom remains responsible for source assessment and every editorial decision.

Pilot safeguards

Controls that can be inspected, not slogans

The signed pilot documents define the final configuration and responsibilities. These are the operating principles for the founding scope.

Dedicated pilot runtime

The participating newsroom receives a separate pilot deployment rather than a shared public workspace.

Named-user access

Access is limited to the agreed pilot users. Membership changes are reviewed during the engagement.

Public-data boundary

Only public, non-sensitive material is accepted during the founding pilot.

Backup and recovery runbook

The pilot operating plan includes encrypted backups, restoration checks, and documented recovery ownership.

Support and escalation

Named Vorbtech and newsroom contacts coordinate incidents, severity, workarounds, and resolution updates.

Permitted material

Public and non-sensitive sources

Public reports, publications, web pages, and official documents.
Lawfully accessed public records selected by the newsroom.
Public-language material suitable for summarisation or translation.
Working questions and notes that do not identify confidential sources.

Prohibited material

Do not upload sensitive investigation data

Confidential-source identities, contact details, or source-identifying records.
Classified, privileged, embargoed, or unlawfully obtained information.
Health, genetic, biometric, payment-card, or authentication data.
Any material the newsroom is not authorised to process in the pilot.

Data lifecycle

Retention and deletion are agreed before use

The order form and readiness acceptance record the selected retention window, deletion responsibilities, and any required export at pilot close.

Collection

The newsroom selects the approved public-source material and controls what enters the pilot workspace.

Active use

Named users work inside the dedicated instance. Access and operating issues are reviewed throughout the pilot.

AI processing

Configured AI services may process approved material to generate draft analysis, summaries, translations, and answers. Provider details are recorded during readiness review.

Closeout

The parties review exports, retention, deletion, account removal, and backup expiry according to the signed pilot documents.

Known limitations are part of the readiness decision

Argus outputs may be incomplete, inaccurate, or contextually wrong. Translations and summaries require source review. The founding pilot does not claim certification, guaranteed accuracy, autonomous verification, or a production uptime SLA. If the newsroom requires sensitive-data processing or certified controls, this founding scope is not suitable.

Questions about privacy or pilot data handling can be sent to admin@vorbtech.com.ng. Review the website Privacy Policy and Terms of Service.