Model location
Local or LAN endpoints keep model processing on the hardware and network you choose.
Security
Model location, tool permissions, and remote access determine the path your data takes.
Local or LAN endpoints keep model processing on the hardware and network you choose.
Configure the files and actions that Bridge may use.
Remote sessions require an approved device pairing.
For a local deployment, prompts and selected files go to your configured local model endpoint.
Hosted model endpoints and optional web search send relevant requests outside your network.
ComfyUI processes image jobs at the endpoint you configure.
Alluqi services hold account, device, pairing, and connection records.
Remote sessions exchange encrypted payloads between paired devices.
Paired remote sessions use device-side key agreement and encrypted payloads.
An approved device pairing is required for a remote session.
Paired devices and remote access can be revoked.
You control endpoint access, backups, network policy, and incident response.
Bridge supports private deployment planning; regulatory obligations depend on the whole environment.
Alluqi does not train models on your prompts, files or outputs.
You own your inputs and outputs. Alluqi never sees your prompts, files or outputs. If you choose an external or cloud model provider, that provider’s terms apply to the data you send it.
Alluqi staff can see account details needed for support, never your local files or chats.
Alluqi does not sell your data or use it for advertising.
Contact sales for data processing terms. Alluqi does not offer a DPA today.
Bridge keeps patient data on your hardware and Alluqi never sees it; contact sales about HIPAA requirements. An external or cloud model provider you choose is governed by that provider’s terms.