Real context before output
Recommendations should be based on the customer’s actual offer, audience, objective, and connected evidence.
Trust and controls
The product is designed around organization isolation, encrypted platform tokens, explicit budget approvals, signed service requests, and a clear separation between observed evidence and generated recommendations.
Product principles
The platform is shaped around a few boundaries that stay useful as automation becomes more capable.
Recommendations should be based on the customer’s actual offer, audience, objective, and connected evidence.
Synchronized account data stays distinguishable from hypotheses, drafts, and recommendations.
Connections can synchronize automatically, while launches and material budget changes require authority.
Production changes need validation, a trail, and a path to understand or reverse what happened.
Personalization with boundaries
The workspace can use brand, offer, audience, goals, budget, and connected performance to improve its output without turning every system component into a credential holder.
Campaigns, metrics, files, messages, referrals, and recommendations are queried within the active workspace context.
OAuth tokens are stored in the web application and are not returned through customer-facing forms or AI generation payloads.
A generated recommendation is not permission to change spend. Consequential execution remains an approval event.
Measured performance can support a recommendation, but generated explanations are still treated as hypotheses until evidence supports them.
Built for accountable automation