Security model.

Security starts with deployment choices you can name: the model endpoint, the hardware owner, the approved tools, and the people and devices allowed to connect.

The five data paths

Every Bridge deployment routes work along one or more of these paths — and you can always name which:

1. Same-workstation runtime. Inference on localhost, on the machine running Bridge Desktop.
2. Customer-network model server. A private IP to a runtime such as Ollama or vLLM on your own network.
3. Alluqi Managed dedicated server. An off-site, single-tenant server over an encrypted path.
4. Selected cloud model. The provider’s API, under that provider’s terms.
5. Deliberate hybrid routing. Each workload sent to the path that fits it.

End-to-end encryption

Bridge traffic is end-to-end encrypted between Bridge Mobile and Bridge Desktop. The relay carries encrypted session traffic and is designed to forward opaque encrypted traffic between approved endpoints without deriving the content keys — it cannot read prompts, code, or responses.

What hosted services store

Alluqi’s hosted services may store:

• Account metadata
• Host and device metadata
• Pairing and relay metadata
• Audit metadata

They are designed not to store or log:

• Prompts and responses
• File contents or paths
• Terminal output and screenshots
• Credentials, private keys, and session keys
• Approval payloads and command content

Identity and remote access

Sign-in is passwordless, using a one-time emailed code. A signed-in account is not the same as remote authority: authenticator-app TOTP is required before pairing a PC or viewing sessions, files, responses, or controls, and pairings, devices, and remote authorization are revocable. See Bridge Mobile.

Tools and permissions

A model does not automatically gain access to the whole computer, every file, terminal command, browser session, or business system. Permissions define which approved tools, resources, and actions a configured workflow can use.

What stays your responsibility

Explicit tools, working directories, user approvals, model choice, local backups, infrastructure access, and incident response remain part of customer responsibilities.

Compliance stance

Architecture supports a review. It does not replace one. Alluqi does not claim a certification or authorization unless it is named on the security page with current evidence.