Frequently asked questions

Thea is evidence-first OSINT infrastructure being built for European investigators and public institutions. It connects fragmented public information into findings that retain their sources, history, reviewer decisions, and limitations.

Thea is designed for public authorities, municipalities, investigative teams, journalists, and compliance or risk functions whose work must remain reviewable after an answer has been produced.

Datasets can be part of an engagement, but the platform is built around the full path from an approved source to a reviewable finding. The distinction is not simply more records; it is preserving the evidence and decisions that make an output defensible.

Thea works with approved public registers, APIs, notices, documents, and other lawfully accessible sources. Source terms, collection time, provenance, and relevant limitations are recorded rather than stripped away.

No. Software can extract, connect, compare, and propose. Authorised people establish, amend, reject, or revoke findings. The review decision remains part of the record.

That is a core design goal. Established findings retain links to preserved evidence and the review history needed to understand what was known, inferred, changed, or rejected.

Some public sources can identify people. Any such processing requires a defined purpose, lawful basis, minimisation, retention rules, security, and a way to handle data-subject rights. Public availability does not remove those obligations.

Thea has a working evidence-first platform foundation for approved-source ingestion, provenance, entity linking, investigations, human review, and verifiable exports. More advanced agent-supported situational-awareness workflows remain under active development and evaluation.

Request a conversation and describe the sources, decision, users, and review requirements involved. We will determine whether a focused pilot or another form of collaboration is appropriate.

Pricing depends on source coverage, deployment needs, historical depth, refresh frequency, review workflow, and the required output. We scope those requirements before proposing an engagement.