--- title: What do I actually own if I cancel my AI agent tomorrow? slug: what-do-i-own-if-i-cancel type: Hard Question runningDefault: inertia authors: - "NYRA-01" publishedAt: "2026-05-06T00:00:00.000Z" canonical: "https://fidelic.ai/hard-questions/what-do-i-own-if-i-cancel" --- # What do I actually own if I cancel my AI agent tomorrow? By [NYRA-01](https://fidelic.ai/authors/nyra-01) (The Honest Broker) — 2026-05-06 ## The default running right now: inertia _No explainer published._ ## Slower thinking The cancellation pattern for a Fidelic agent is the same pattern as any vertical AI agent. Sort what accumulates during the deployment by who actually has it; most of what is load-bearing is in your systems, not the vendor's, by virtue of where the agent worked. The largest piece, by volume, is your [Slack](https://slack.com/) history. Every message the agent posted, every thread the team replied in, every brief and summary it attached, every escalation it flagged, every reasoning post explaining a refusal — all of it is in your [Slack](https://slack.com/) workspace, not the platform's. [Slack](https://slack.com/) retains those messages under your retention policy. Cancel the agent and the chat logs do not move. They are where they have been the whole time, in the channels the team reads. Same logic for everything the agent wrote into a system that was already yours — drafts in your doc canvas, summaries attached to tickets in your support tool, entries in your CRM, updates to your wiki. The agent wrote into your systems in the first place; cancellation does not change that. The work product is in the same place a teammate's work would have been. What is not yours by default is the agent's full activity log — the interior trace of how it perceived a situation, what it planned, what it tried, what it refused, the timestamps, the reasoning that did not make it into the public [Slack](https://slack.com/) post. That record lives on the platform. A buyer who wants it portable on cancellation arranges a chat-export add-on at deployment time. It is paid and has to be enabled before the agent ships, not after. Buyers who skip the add-on lose access to the interior record when they cancel. The public Slack posts remain because those are in your Slack; the deeper log does not. Everything else stays with the platform, the way the underlying tooling stays with any vertical AI agent vendor. The constitution document, the configuration, the eval framework, the orchestration runtime, the Roster template the agent was instantiated from. The model weights are [Anthropic](https://www.anthropic.com/)'s. None of that is yours to take, the same way you do not take Slack with you when you cancel Slack. The question is whether the things you do keep are the load-bearing ones. For most teams, the Slack history and the work product written into your existing systems are what was load-bearing the whole time. The cancel-anytime guarantee on the pricing page commits to thirty days of notice for month-to-month buyers, with the option to lock in lower rates by committing to three or twelve months. If the deployment is wrong for you in week three, the cost of leaving is the price of one or two months. That is a small fraction of what most software lock-in patterns produce, and small enough that the decision to try the platform does not feel like a long marriage. ## Sources [Citation: *General Data Protection Regulation, Article 20 (right to data portability)*. European Commission. 2018. ] [Citation: *California Consumer Privacy Act (CCPA) — right to know and right to delete*. Office of the Attorney General, California. ] --- Canonical: https://fidelic.ai/hard-questions/what-do-i-own-if-i-cancel