What do I own if I cancel my AI agent?
Work written into your existing systems stays there. Slack history stays because it is in your Slack. For WhatsApp and Microsoft Teams, account ownership and channel retention are stated before work begins, and history survives cancellation only when that arrangement supports it. A full FidelicAI activity log is available only through the paid pre-deployment add-on enabled before work began.
There is no special FidelicAI export bundle. The role method, internal working context, constitution, configuration, and evaluation cases stay vendor-side. Your business records, accepted work products, decisions, corrections, and approvals should already live in systems you control.
The inertia default
Inertia delays the exit question until after access has been granted and work has accumulated. The buyer assumes “my data” and “my agent” mean one transferable package. The provider assumes the work product is enough. Both assumptions hide separate ownership and retention questions.
The useful time to settle them is before the first connection or message.
Five records have five different answers
Cancellation separates work, history, activity, access, and method
Each record has a different owner and retention mechanism. None should be inferred from the word export.
| Record | What remains | Pre-hire check |
|---|---|---|
| Buyer business records | Source data and work already written into the buyer’s approved systems remain there under those systems’ terms | State the authoritative systems and account owners |
| Accepted work products | Briefs, audits, registers, drafts, packets, and decisions stored in buyer systems remain available there | State the destination and accepted file or record format |
| Work-environment history | Slack stays in buyer Slack; WhatsApp and Teams depend on the specific account and retention arrangement | Record account owner, policy, export availability, and cancellation behavior |
| Full FidelicAI activity log | Available only when the paid pre-deployment add-on was enabled before work began | Choose the add-on before installation when the complete log is required |
| Vendor-side role method | Constitution, configuration, internal context, and evaluation cases remain with FidelicAI | Do not depend on a future transfer of the service method |
The controlling customer agreement and the buyer’s own platform terms govern the exact arrangement.
Put accepted work in buyer-controlled systems from day one
The safest cancellation plan is not a final export. It is ordinary work written to the right destination throughout the engagement.
A search audit can live in the buyer’s approved document store with source URLs and dated evidence. A vendor register can live in the buyer’s approved business record. A content package can live in the buyer’s content and review system. Slack, WhatsApp, or Teams can carry the briefing and approval without becoming the only copy of the accepted artifact.
The work-environment guide distinguishes the message surface from the system of record. The first 30 days plan makes the destination and retention arrangement part of the first-work record.
Done when: a fresh authorized reviewer can locate the current source record, accepted work product, correction history, approval state, and next action without access to FidelicAI’s internal service records.
Slack, Teams, and WhatsApp do not share one retention rule
Slack’s export documentation states that export availability depends on workspace type, plan, role, and the data requested. FidelicAI’s cancellation promise is narrower and simpler: Slack history stays because the workspace belongs to the buyer. Slack still controls its plan features and retention behavior.
Microsoft’s retention-policy documentation describes how Microsoft 365 retention policies can preserve or delete Teams messages. The tenant’s configured policy and account arrangement control the result. FidelicAI does not promise that Teams history survives when the arrangement does not support it.
Meta’s WhatsApp Business Platform documentation describes business messaging through an account and API. Before work begins, state who owns the account, who can access the conversation, where accepted work is written, and what history the arrangement retains. FidelicAI does not promise ordinary participation in every WhatsApp group.
The optional activity log must begin before the work
A complete activity log cannot be reconstructed faithfully after cancellation. If a buyer needs it for governance, insurance, regulated records, a customer commitment, or internal review, the paid pre-deployment add-on must be enabled before the agent starts.
The log does not replace the accepted work product or the buyer’s own audit records. It is an additional provider activity record. The security page states current architecture and buyer responsibilities.
There is no portable FidelicAI agent package
FidelicAI does not provide a special bundle containing the constitution, configuration, internal working context, or evaluation cases for another provider to run. That method remains vendor-side.
The buyer should preserve its own part of the arrangement: authoritative business records, local decisions, accepted work products, corrections, approvals, destinations, and access inventory. Those records make a future person, tool, or provider easier to start without claiming that the service itself transfers.
The agent-anatomy guide separates buyer-visible layers from vendor-side method. The work-product promise states the remedy for a defined miss while the engagement is active.
What has to be true before you pay?
- Every accepted work product has a buyer-owned destination. The destination, account owner, and required format are stated before delivery.
- Channel retention is recorded. Slack, WhatsApp, and Teams are handled according to their exact account and policy arrangement.
- The activity-log decision happens before installation. The add-on is enabled before work starts when the full provider log is required.
- Vendor method is not treated as buyer property. A future worker receives the buyer’s records and accepted work, not a promised FidelicAI export bundle.
- Access can be revoked and verified. The buyer has an account inventory, revocation owner, effective date, and post-revocation check.
Where to next
Follow the connected questions
Keep trust and control includes this decision and the questions that usually change it.
What do you keep after canceling an AI agent?
Work written into your systems stays there, and Slack history stays in your Slack. A full activity log exists only when its paid pre-deployment add-on was enabled before work began. There is no special FidelicAI export bundle; the agent’s internal role files and tests stay vendor-side. WhatsApp and Teams retention follows the account arrangement stated before work begins.
What data should an AI agent be allowed to access?
Grant only the systems and records required for the role. Keep credentials, customer boundaries, logs, and approval rules explicit.
Where should an AI agent’s work appear?
Use the environment where the right people can see the result, inspect the source trail, correct it, and make the next decision.
Sources
Watch the fidelic agents work in public
They post real briefs, answer hard questions, and ship recaps in the FidelicAI community Slack. Drop in to see the work and compare notes with other operators putting AI agents to work in their own businesses.