Lawful source intake
Provenance, acquisition method, transfer moment and authority are recorded before processing.
BronVast Messages | Sources & intake
Prove what was supplied before processing begins.
WhatsApp, SMS, Signal, Teams and other business messages may arrive through very different exports or capture outputs. BronVast does not promise a universal connector: every source variant records what exists, what is missing, which assumptions apply and which processing route is defensible.
Messages
Every source byte in the manifest
SHA-512, size, file characteristics and source ID enable checks before and after processing.
Support is tested
Parser, time zone, attachments, events and exceptions are recorded in a versioned source profile.
From source package to accountable destination
Scope
channels, roles, period and purpose
Transfer
authority and chain of custody
Manifest
files, characteristics and SHA-512
Profiling
records, time, attachments and events
Exceptions
missing, duplicate, unknown or damaged
Pilot
acceptance profile and safe next step
The BronVast Messages Scan
The Scan shows where your organisation stands and which first step can be taken responsibly. Together with records, archives, privacy, security and technology specialists, we map sources, roles, risks and dependencies.
- source and channel map
- scope, roles and authority map
- available exports and capture dependencies
- context, appraisal and hold questions
- risk and dependency register
- target architecture and pilot acceptance
What a source profile records
A brand name is insufficient. Version, export route, language, device or platform behaviour and missing fields can change the outcome.
- record and conversation identifiers
- source time, time zone and normalisation
- participants, groups, aliases and roles
- attachments, voice notes and availability
- edits, replies, deletion signals and system events
- known constraints and tests per profile version
Where further verification remains necessary
A hash shows that a file is unchanged, but without source testing it does not yet establish whether the original communication is complete and authentic.
- recovery of deleted messages only where the source permits it
- completeness tested against source and export profile
- compatibility established for each tested export variant
- processing within the agreed purpose and scope
What your organisation receives
Provenance remains connected
Every package and file receives a stable place in the evidence route.
Capabilities and limits in advance
Supported fields, exceptions, time behaviour and test results per source variant.
Small, controlled and measurable
Test set, acceptance criteria, roles, security, fallback and receiving destination.
Reference points
These references show the professional basis for our choices. The requirements that apply in practice are determined with you from your situation, responsibilities and receiving environment.
Questions about this route
Does this work with WhatsApp or Teams?
Only after profiling the concrete, lawfully obtained export or capture output. A brand name alone is not a technical acceptance profile.
Does 2dA alter source files?
The source layer remains unchanged and verifiable. Derived representations and metadata live in separate layers.
What happens to missing attachments?
They are neither invented nor silently skipped. The exception remains visible in the manifest, review and delivery report.
Next step
Start with evidence, not assumptions
A first engagement can be limited to one lawful source package, one process and one receiving profile.