The questions a careful evaluator asks — OAuth scopes and approval-gated execution, whether your data trains AI, supported CRMs, security & DPA, what's live today, and how Claresto differs from point tools — answered plainly.
The Claresto demo is powered by permissioned, anonymized real ad-account data from volunteer operators and design partners. We remove or substitute identifying brand details before anything appears publicly, but the spend movement, pacing behavior, alerts, draft states, attribution drift, and workflows reflect real paid-media operations. You can explore every module without connecting your own accounts, then run the same guardrails against your own connected accounts during diligence.
Claresto connects with the narrowest permissions each platform supports for the workflow you enable. Monitoring, reporting, draft detection, and reconciliation use least-privilege access. Any write-capable action is policy-controlled, approval-gated, and recorded in the audit ledger with actor, timestamp, rationale, and before/after state. Connections are explicit, revocable by the account owner, and documented platform by platform in the security packet.
Claresto supports operational workflows and executes approved changes through governed controls. High-impact actions are routed through maker-checker approval, role policy, and audit logging so teams can monitor, govern, approve, and execute from one control plane. You decide which work stays monitor-only and which workflows Claresto is allowed to carry through approval-gated execution.
Claresto is working with early design partners and volunteer operators who contributed permissioned, anonymized real account data for the demo and evaluation flows. Public names are not listed because paid-media account data is sensitive, but reference conversations and deeper diligence can be handled privately where appropriate. The important investor and buyer point: this is not a generic mock dataset; the product story is grounded in real operator workflows and real account behavior.
No. Customer ad and CRM data is not used to train or tune foundation models, and it is not pooled across customers. Claresto uses tenant-scoped statistical baselines and guardrail logic to detect drift in that tenant’s own campaigns. Data minimization, encryption, revocable connections, and configurable retention apply throughout.
Claresto supports Salesforce and HubSpot as the core CRM paths for early access, with additional CRMs scoped during onboarding. Matching uses click and lead identifiers such as GCLID, MSCLKID, and lead email mapped to CRM opportunity records and closed-won revenue. Claresto then compares platform-reported conversions and ROAS against CRM-verified revenue, surfaces the gap, and flags broken CAPI, UET, and sGTM tags that can inflate the platform number.
Claresto reads the live, in-effect campaign settings directly from each platform rather than relying on the draft someone intended to ship. When a budget, targeting, or schedule change is saved as an unpublished draft and never promoted, the live campaign keeps running the old numbers. Claresto flags that gap, shows the live value next to the intended value, and records the event in the change-audit ledger with before/after state and timestamp. You can see the planted draft workflow in the demo and repeat it against a connected account during diligence.
The evaluation experience demonstrates the full Claresto operating model: cross-platform budget pacing, overspend detection, unpublished-draft detection, a hash-chained change-audit ledger, Claresto AI anomaly detection, CRM-verified attribution, finance reconciliation, RBAC and maker-checker approvals, Launch QA, client/stakeholder portal, and executive reporting. Some enterprise integrations such as nonstandard CRMs, SSO/SCIM, custom retention, and data residency are scoped during onboarding.
Yes. Claresto’s diligence packet is built for the questions security, finance, and procurement teams ask first: architecture, approval-gated access model, requested platform permissions, data handling, encryption, retention, DPA terms, sub-processors, and control mappings. Cloudflare is the primary infrastructure provider for compute, storage, and AI inference. Full named sub-processor and retention details are shared during diligence under NDA.
Retention is configurable by data class. Audit and reconciliation records are designed for long-lived financial and compliance evidence, commonly aligned to multi-year audit windows. Raw campaign and spend metadata can be kept on a shorter rolling window, and anomaly baselines are recomputed rather than retained as raw training data. Enterprise plans can tune these windows by policy.
Claresto is built around SOC 2-style controls from the start: governed ingestion, role-based access, maker-checker approval gates, access review workflows, encryption, and a tamper-evident change ledger. The security packet maps these controls to buyer review requirements and SOC 2 change-management expectations, with formal audit evidence handled as part of enterprise diligence.
Every budget, bid-strategy, targeting, and creative change across connected platforms lands in one ledger. Entries carry actor, timestamp, before/after state, approval status, and source platform, and they are hash-chained with SHA-256 so later edits to prior records are detectable. The result is exportable evidence for finance, compliance, and client/stakeholder review.
Permissions are scoped by role — viewer, analyst, approver, administrator — and high-impact changes can require a second person to review before release. Approval policies can be configured by account, platform, and spend threshold. Every approval is written to the audit ledger with actor, timestamp, rationale, and before/after state.
Claresto governs budget risk, so pricing follows the paid media it protects rather than the number of people who need visibility. That means teams can bring in finance, approvers, executives, agencies, and auditors without being punished for collaboration. Tell us your monitored spend and we size the plan around the budget at risk.
Claresto is built for marketing, finance, compliance, and agency teams that need one control plane over cross-platform paid media. Bid optimizers tune campaigns. Dashboards stitch exports. Attribution tools explain conversion credit. Claresto governs the operation around them: pacing, drafts, changes, anomalies, attribution drift, invoice reconciliation, approvals, and reporting in one governed system.