Your work and your data

The intended product boundary

E2C is designed to work with your authorized environment without adding a separate file-hosting, synchronization, or project-management service. The aim is to avoid routing business files through LBAI's cloud or keeping an additional company copy of your Codex conversations. Those boundaries still need to be verified in the implemented product.

Files, outputs, and technical records

Your source files, requested outputs, execution records, temporary data, diagnostic logs, crash reports, and telemetry may follow different paths. What each component reads or writes, where it sends information, who can access it, and how long it is retained still need confirmation. Having no upload button does not establish that no data is processed or stored.

Your execution provider's role

Codex processing under your authorization is separate from LBAI's services. A file can stay on your disk while some of its contents are sent to an execution or model service. The provider's handling depends on the actual product configuration and applicable terms, not on whether the interface is a browser or a desktop app.

LBAI's own responsibilities

LBAI's planned cloud services concern E2C accounts, authorization, and payments. Those services handle information too. LBAI remains responsible for its own software, distribution, updates, integrations, and credential handling; using a third-party service does not remove those responsibilities.

Questions on this website

Questions asked on this website are handled separately from project work.

Read how your chat data is used before sending a question.

Do not include passwords, access keys, sensitive personal information, or confidential business information in a product question.

You can also read Help articles and prepared answers without starting a conversation.