Overview
Trendemon’s AI assistant, SAIL, allows authenticated Trendemon users to ask natural-language questions about their website traffic, engagement, conversions, campaigns, content, audiences, and personalization performance. Trendemon retrieves the account data, sends the question and required data to the OpenAI API, and displays the generated answer inside the Trendemon dashboard.
This differs from an external MCP integration: Trendemon operates the full application flow and selects OpenAI as the AI service provider. Customers do not connect a separate AI client or authenticate directly with OpenAI.
Architecture and data flow
- The user signs in to the Trendemon dashboard through Auth0 and submits a question to SAIL over HTTPS.
- Trendemon verifies the user's session, account access, and feature enablement before retrieving data.
- SAIL requests data only through approved analytics sources or a controlled query layer bound to the validated account.
- Trendemon sends the question, instructions, and relevant retrieved data to the OpenAI API over TLS. Auth0 tokens, OpenAI credentials, and database credentials are not included in the prompt.
- OpenAI generates an answer, which Trendemon returns to the authenticated SAIL session. Follow-up questions remain subject to the same account-scope controls.
Authentication, authorization, and query safety
SAIL uses the existing Trendemon identity and permission model. The user does not need an OpenAI account, and OpenAI credentials remain server-side.
Controlled analytical access
- Only approved tables, dimensions, metrics, and filterable fields are available.
- The assistant uses structured query parameters rather than arbitrary SQL.
- Filter values are bound as parameters, and the validated account ID is added server-side as a mandatory filter.
- Date ranges, result rows, payload size, execution time, model tokens, and request frequency are limited.
- Generated output is treated as untrusted text, safely encoded for display, and never executed as HTML, JavaScript, SQL, or a privileged Trendemon action.
Data sent to and processed by OpenAI
Depending on the question, the OpenAI request may include the user's question; aggregated traffic, engagement, conversion, campaign, content, audience, and personalization metrics; relevant dimension labels; and company names or domains when an ABM analysis requires them. Trendemon transmits only the smallest relevant data set and period, and excludes credentials, secrets, payment data, and unnecessary internal identifiers.
According to OpenAI's published enterprise privacy information, business data submitted through its API Platform is not used to train OpenAI models by default. OpenAI also states that API inputs and outputs may be retained for up to 30 days for service delivery and abuse monitoring, except where eligible endpoint or account configurations provide different controls.
Data shared with OpenAI
Seven read-only tools, in three families:
The analytics catalog is a static, code-defined allow-list of 29 aggregated tables (daily and monthly grain) covering traffic, conversions, coverage, sources, campaigns, unit performance, and uplift — including their ABM (company-level) counterparts. It is not a generic SQL gateway: the model cannot name a table, column, or expression that is not in the catalog.