TERMS OF USE
Use the platform responsibly.
VeriTrustLab supports evidence-aware email investigation and human review. These usage terms describe responsibility, authorized access, and the service boundaries of the documented implementation.
Reference updated Documented implementation and evidence boundaries
- Use
- Authorized investigation
- Review
- Human judgment
- Availability
- Bounded pilot operation
Service scope and availability
The active investigation workflow handles email text, raw .eml, extracted URL evidence, and authorized trusted-receiver context. Archived/catalog references to image, audio, video, deepfake, learning, or WebUSB do not make those active user capabilities.
Features, providers, limits, and schemas can change. The documented pilot has a finite model operating window, workspace quotas, and bounded CPU capacity. Before model readiness or outside the window, SMTP can safely defer. There is no unrestricted always-on delivery or sustained-capacity SLA claim.
Your responsibility for submitted content
You must have permission to submit, process, retain, and share the material used in an investigation. Follow applicable law, internal security/privacy policy, and your incident-response procedures. Minimize unnecessary personal or confidential data.
Review the source evidence and coverage gaps before acting. Model scores, rule indicators, infrastructure context, and campaign matches are decision support; they do not establish certainty, malicious intent, or legal responsibility.
Accounts, workspaces, and credentials
Protect account credentials and use the workspace and role you are authorized to access. Membership in one organization does not grant access to another organization’s investigations, exports, original files, or receiver.
Keep developer keys private and use them only from trusted backends or private automation. Do not publish them in browser JavaScript, repositories, public notebooks, logs, or client applications. Scopes, activation/expiry, revocation, feature flags, and quotas can independently deny a request.
Prohibited misuse
Do not use the service for illegal surveillance, harassment, credential theft, unauthorized processing, evasion, or harmful automation. Do not attempt to bypass authentication, tenant boundaries, recipient authorization, worker replay protection, or request limits.
A configured gateway is not an open relay. New organizations, domains, mailboxes, and delivery providers require explicit operator assignment, credentials, routing, and independent testing. Creating an account does not automatically enable organization-wide mail protection.
Reports, signatures, and independent review
Preserve the original exported evidence package when signature verification matters. A valid Evidence Passport detects modification and checks its configured issuer; it does not certify that a message is safe, identify its human sender, or establish legal admissibility.
Historical signed snapshots retain their original observations and limitations. New policy versions, provider facts, or higher acquisition stages do not authorize rewriting old signed decisions. Confirm important outcomes through independent, trusted channels.
Data handling and configured integrations
Submitted material and derived evidence are handled as described in the privacy and data-handling page. Retention and erasure are policy/hold-aware workflows, not an unconditional automatic deletion guarantee.
Configured providers and delivery adapters can fail or become unavailable. Analysis completion, saved evidence, gateway disposition, and confirmed final delivery are separate outcomes. Optional billing integration is not a claim that live commercial payment flows were validated by the technical review.
Read the analysis limitations and security controls before relying on the service for high-impact decisions.