THE SHORT VERSION

Elias is designed to help an AI host answer questions using business data from sources you choose. A production privacy policy should explain exactly what account, connection, usage, support, and billing data is collected and why.

This mockup does not collect a real account, source credential, payment method, or API key.

DATA A LIVE SERVICE MAY HANDLE

Depending on the final product, this could include account details, workspace settings, connected-platform identifiers, source data requested by an AI host, API usage records, support messages, and billing metadata supplied by a payment provider.

The production policy should list each category precisely, including retention periods and the service providers involved.

HOW IT WOULD BE USED

The intended use is to authenticate your workspace, maintain authorized connections, answer requests from your AI host, improve reliability, provide support, and manage a subscription if billing is enabled.

Elias should not use connected business data for unrelated advertising or sell it to data brokers. Any production use beyond the core service would need to be stated clearly.

SHARING & SECURITY

A live service may share limited information with infrastructure, authentication, analytics, support, and payment providers needed to operate the product. It should document those providers and the safeguards applied to each data flow.

You should never paste a personal API key into a public prompt, commit it to a repository, or share a source credential with someone who does not need it.

YOUR CHOICES

A production service should provide a way to review, correct, export, or delete account information where required, and to contact the team with privacy questions. The final policy should include the real contact and response process.