Human approval on anything irreversible
The agent has no send path to your clients. A quote drafted from an inbound RFQ stays a draft — on email, WhatsApp, and every other channel — until an operator explicitly sends it. This is a structural property of the pipeline, not a setting that can drift.
Document filing is gated the same way: a customs packet only files automatically when every safety check passes — no extraction alarms, clear sanctions screening, a confident order match. Anything ambiguous waits for a human, and auto-filing can be disabled entirely per workspace.
Credentials and encryption
- Mailbox passwords for IMAP/SMTP connections are encrypted at rest with AES-256-GCM before they touch the database.
- Per-tenant WhatsApp tokens are stored encrypted with the same scheme and are readable only by server-side service code.
- Inbound WhatsApp webhooks are verified against Meta's payload signature; machine-to-machine APIs require bearer tokens with optional per-workspace allowlists.
- OAuth connectors (Gmail, Microsoft 365) use scoped refresh tokens; Google data handling follows the Google API Services Limited Use policy, affirmed verbatim in our privacy policy.
Workspace isolation and access control
Every workspace's data is isolated with row-level security enforced in the database itself — not only in application code — so a browser session or API caller can never read another tenant's rows.
Inside a workspace, access follows a capability matrix crossed with assignment scope: drivers and clients never hold agent-chat capabilities, managers see only assigned drivers once assignments exist, and the AI layer runs with a manager's permissions — never as a superuser.
The workspace Telegram bot refuses unknown chats. A stranger who discovers the bot's username gets no response surface at all; only linked staff, drivers, and clients are routed, each with their role's capabilities.
Compliance guardrails with audit trails
Customs packets are screened against sanctions risk before filing. A hit blocks automatic filing; an operator can override only with an explicit acknowledgment, and the override is logged. Administrative actions such as credit grants are recorded in an audit log, so "who did this" stays answerable.
GDPR and jurisdiction
The data controller is Solario projektai, UAB, registered in Lithuania (company code 304156786), operating under EU law. Privacy questions reach privacy@4logist.ai; security reports reach security@4logist.ai. The supervisory authority for GDPR complaints is the Lithuanian State Data Protection Inspectorate.
Frequently asked questions
Can the AI email my clients on its own?
No. There is no automatic send path on any channel. Drafts wait for an operator's explicit send.
Is my mailbox password stored in plain text?
No. IMAP/SMTP credentials are encrypted at rest with AES-256-GCM; decryption happens only server-side when connecting to your mail provider.
Who do I contact about a vulnerability?
Email security@4logist.ai. Reports are read by the engineering team.