Trust and data handling

How LDOO works

LDOO connects your marketing data and explains what is happening. Every answer shows the query that produced it. Your data stays in your database. Here is exactly how.

How answers are generated

Your question becomes a database query

You ask a question in plain English.
LDOO translates it into a SQL query against your marketing data.
The query runs against your own Supabase database — the same data your integrations sync.
The results are interpreted into a clear, client-ready explanation.
The SQL query is shown alongside every answer so you can verify exactly what was asked of the data.

Data handling

Your data stays in your database

LDOO does not copy, export, or store your marketing data outside your Supabase instance.
Query results are cached temporarily (15 minutes) in Redis for performance, then discarded.
The AI model (Anthropic Claude) receives the question, schema metadata, and query results — never raw credentials or full database access.
API keys for connected platforms (Google, Meta, Shopify) are encrypted at rest and never exposed to the client browser.

Client isolation

Every client is scoped and separated

All queries are filtered by account_id and client_id at the database level (Row Level Security).
A question about Client A cannot return data from Client B — this is enforced by PostgreSQL, not application code.
Client portals are scoped to a single client and cannot access conversations, reports, or agency data.
Shared report links and client portals can be password-protected and revoked at any time.

Accuracy

What LDOO can and cannot guarantee

LDOO answers are bounded by the data in your database. If the data is incomplete, the answer will be too.
Every answer shows the SQL query that produced it. If the query is wrong, the answer is wrong — and you can see why.
AI-generated narratives and recommendations are based on the queried data, not external knowledge. LDOO does not hallucinate numbers — it reads them from your database.
Complex statistical analysis (significance testing, cohort analysis) is not yet supported. LDOO excels at direct data questions: what happened, how much, which campaign, what changed.

AI model usage

How the AI model is used

LDOO uses Anthropic Claude for two steps: translating your question into SQL, and interpreting the query results into a narrative.
Your data is sent to the Anthropic API only for these two steps — it is not used to train models.
Anthropic's data retention policy: prompts and completions are not retained beyond the API request lifecycle.
All AI calls are made server-side via Supabase Edge Functions. The Anthropic API key is never exposed to the browser.

What LDOO does not do

Explicit limits

LDOO does not modify your ad accounts, analytics properties, or any connected platform.
LDOO does not send emails on your behalf (report delivery is opt-in and configurable).
LDOO does not share data between accounts. There is no cross-account analytics or benchmarking.
LDOO does not make automated changes to campaigns, budgets, or bids. Recommendations are informational only.

Questions?

If you have specific questions about data handling, security, or compliance, reach out directly.