LobeWork is designed with clear boundaries between your local projects, your account, connected providers, and optional features so you can understand what each part can access.
Sign-in, billing, device authorization, licensing, and organization access are handled separately from your local project folders. Using the customer account portal does not give LobeWork access to the contents of those folders.
Voice is click-to-talk, not always listening. LobeWork does not intentionally store your audio or dictated text as part of ordinary voice use. Availability can depend on the voice option and operating system you choose.
Extensions are expected to declare what they need before use. Permissions and capabilities should be visible so you can make an informed choice before an extension interacts with project resources.
Automation Studio is designed around reviewed actions. LobeWork should not silently perform destructive work, send data, or execute powerful actions without the permissions and confirmations required for that workflow.
Supported local-model connections are intended to stay local to your computer unless you deliberately configure a remote destination. LobeWork does not turn your local model service into a public endpoint.
Support requests do not automatically include your project files. You choose what diagnostics or context to share, and you should never send passwords, provider keys, payment-card details, or unrelated confidential files.
Use the dedicated security report form for suspected vulnerabilities, account-security concerns, or unsafe product behavior. Security reports are handled through the private support workflow.
Open security report form