PDF, DOCX, and HTML stay in the local inspection lane
The local-first path is clearest when the source is an imported file. That keeps the trust boundary narrow from the start.
Trust model
Local first by default. Explicit when the network is involved.
Veridicus Scan keeps inspection and report generation local for imported content. When the source is a user-provided HTTPS URL, the app makes that network boundary explicit, applies the chosen redirect policy, and carries the resulting coverage state into the report. The same local boundary extends into premium MCP sessions while the app is active.
On-device path
The safe default is the local path.
For imported files, the app centers the on-device flow: inspect the content, score the result, and keep the readable report available without routing the file through a remote analysis surface first.
Readable evidence is generated from the same local scan
The score, findings, guidance, and coverage notes come from the scan itself, not from a separate remote reporting service.
Recent scans keep prior review close at hand
Users can reopen recent items and resume the trust decision with the earlier scan still available for reference.
When the network is used
URL fetching is explicit, scoped, and policy-aware.
The app does not blur local file inspection with URL fetching. The URL path begins only when the user chooses an HTTPS source and it stays governed by the selected redirect mode.
User-provided HTTPS input
The network path starts only after the user chooses to scan a specific HTTPS URL instead of importing a file.
Strict or lenient redirect policy
Strict mode preserves a hard boundary when redirects matter, while lenient mode exists for broader compatibility with safe HTTPS redirects.
Coverage and boundary notes
The report carries the scan outcome forward so a user can see whether the result is complete, partial, or limited by the chosen path.
Export boundaries
Sharing should preserve the same restraint as the scan.
Export exists for handoff and review, but the default posture stays conservative. A team can share the outcome without turning the report into an accidental copy of the original suspicious content.
What a teammate sees
- Risk score, risk band, findings, and guidance
- Coverage notes if the scan was partial or capped
- Source context strong enough to review the decision
What stays bounded
- Evidence snippets are redacted by default
- Export is deliberate, not automatic
- Users control whether more evidence is included
Where to go next
Next step
Trust works better when the report surface is just as clear as the scan surface.
Continue into the report page for the output side of the workflow, or jump to the URL explainer if the network boundary is the main concern.