Getting your data out: a census of 149 listings

On termination the customer is given access to all stored information for export, but prepaid credits are explicitly non-refundable, so unused balance is money you do not get back.

Checked 2026-09-23

Individual agents export their output, for instance clean structured Excel lead databases and CRM-synced contact records, but no account-level data export path or credit expiry policy is published.

Checked 2026-09-27

Conversations and messages leave over a documented export API, configuration leaves via the Snapshot API and the audit log exports to CSV; export history is limited to the past twelve months.

Checked 2026-10-11

All state is plain local files you already own — project config, checkpoints and logs in a documented state directory — and with no billing there are no credits to expire.

Checked 2026-10-10

Client ownership of the deployment is offered where architecture permits and post-launch ownership of changes and vendor dependencies is named, but no export mechanism or wind-down term is published.

Checked 2026-10-11

Conversation state lives in storage you already own, such as a JSON file, SQLite or Postgres, and there are no vendor credits that could expire; no formal export tool is documented.

Checked 2026-10-11

Nothing to export because the data never leaves your database, retention is unlimited and deletion is yours; there are no credits that could expire.

Checked 2026-10-11

Data export is a checked row on every plan and Enterprise adds free export in its standard terms, but the other half of the question is worse than neutral: unused conversations expire after two months on monthly plans.

Checked 2026-09-23

Audit history and connections can be reviewed and revoked in the dashboard, but no data export is documented and the terms disclaim any obligation to refund an unused balance; credit expiry is never addressed.

Checked 2026-10-03

Nothing is locked in a vendor store: edits land as commits in your own git repo and the chat transcript is a plain markdown file you can copy, and there are no credits that could expire.

Checked 2026-09-30

Configuration is portable: workflows export as downloadable files for import into another app, and audit logs and request transcripts export to external systems. No full-tenant data export or credit-expiry policy is published.

Checked 2026-09-24

Export exists as a role permission covering tasks, contacts, leads and lists, but the terms cut the other way at the end: access stops and you must delete service output data on termination, and unused subscription periods are not refunded or credited.

Checked 2026-09-10

Conversations live locally and export to the desktop app, but deleting your stored interactions means emailing support rather than a self-serve control, and nothing says whether purchased credits expire.

Checked 2026-09-10

Exports and saved lists stay downloadable as CSV from the app or CLI, account data is supplied on request in a portable format, and prepaid credits survive cancellation for 365 days.

Checked 2026-09-26

Exit is a defined deliverable: code and account ownership, documentation, rollback and the support boundary are settled at handover rather than left open.

Checked 2026-10-03

Data gets out cleanly enough - CSV export on every plan including Free, CRM sync back to Salesforce or HubSpot, and deletion or return of customer data within 30 days of written request - but credits are the sticking point: annual allocations expire at term end and purchases are non-refundable.

Checked 2026-09-10

Call records, recordings, transcripts and AI agent logs can be exported from the portal or the API, but they are deleted automatically at the retention period and no credit-refund terms are published.

Checked 2026-09-24

Top-ups expire 12 months after purchase and included usage does not roll over; usage data exports as CSV, but no code/session export is documented.

Checked 2026-09-02

Teams, agents and conditions serialise to JSON via dump_component and save_state, and Studio persists sessions in your own SQLite or PostgreSQL database. No credits exist to expire.

Checked 2026-09-02

Leads export to CSV and recordings can be downloaded call by call, and press-release credits do not expire, but there is no documented bulk export of transcripts and cancellation does not delete data immediately.

Checked 2026-09-11

Code and intellectual property transfer to the buyer at completion and the privacy policy grants a data access right, but no page describes handover of trained models, prompts or agent configuration on cancellation.

Checked 2026-09-11

Call data exports as CSV and via API, but the export window is capped at 180 days and credit expiry is never addressed.

Checked 2026-09-11

Code leaves cleanly as a zip or through GitHub sync, but unused tokens expire two months after issue and are lost entirely if you stop paying.

Checked 2026-09-11

Conversations and analytics export via the API and the DPA requires deletion or return at termination; unused conversation packs expire at month end while AI credit grants carry for up to 12 months.

Checked 2026-09-02

Self-serve deletion is documented down to the button in account settings, but no bulk export is described, unused subscription time is explicitly non-refundable and data may be erased on termination.

Checked 2026-09-13

Artifacts are retrievable by API and replays downloadable as MP4, but retention is capped at 7 or 30 days by plan and monthly allocations do not roll over.

Checked 2026-09-02

Purchased credits survive tier changes and cancellation, but rollover is capped at 2x the monthly plan rate; call transcripts export via API or CLI.

Checked 2026-09-02

Session transcripts are plain JSONL on your own disk and can be mirrored to S3, Redis or Postgres with a SessionStore adapter; expiry of unused prepaid API credit is not stated in the pages read.

Checked 2026-09-02

/export writes a readable transcript, transcripts sit locally as JSONL, and org analytics and spend reports export as CSV; prepaid usage credits mostly do not expire.

Checked 2026-09-02

Task history is plain JSON on your own disk and can be mirrored to your S3 or R2 bucket, but the terms make fees non-refundable and give nothing back for unused credits on cancellation.

Checked 2026-09-12

Review metrics export as CSV capped at 10,000 rows, with a larger Metrics API on Enterprise only; account deletion is irreversible and immediately cancels the subscription.

Checked 2026-09-15

Enterprise admins export supported records with published Bash and PowerShell download scripts; sessions are plain files on disk.

Completed objective data downloads as CSV at any time and webhooks push it live, the Terms grant export at any point, and unused paid-plan DMs roll over on upgrade while free-plan DMs do not.

Checked 2026-09-28

Reports and insights export to CSV, Excel, image or PDF in-product, and on termination the customer instructs deletion or return of all personal data; no credits exist to expire.

Checked 2026-09-12

Export exists but is tightly bounded: a ten-day self-service window after termination, after which Cresta may delete the content, and any Cresta-performed export needs a statement of work and professional-services fees. Default media retention is two years.

Checked 2026-09-13

Automation source can be pulled back as a ZIP over the API and traces can be shipped to your own OpenTelemetry collector; nothing published covers rollover of unused executions.

Checked 2026-09-13

Account deletion is self-serve and permanent with all data removed within 30 days, and your code stays local; included usage is not portable, resetting each billing cycle.

Checked 2026-09-02

Decagon asserts full data portability and no SDK lock-in, and its trust centre lists deletion on departure, but no export API or retention terms are published.

Checked 2026-09-14

Usage and per-request cost are exportable through the management API and 90 days of request logs, and unused credits are refundable within 30 days of purchase. Expiry depends on origin: card-purchased credits never expire, promotional credits expire a year after signup and contract credits expire with the contract.

Checked 2026-09-02

Purchased on-demand credits roll over and never expire; no account-wide data export is documented beyond invoices and per-resource API reads.

Checked 2026-09-02

Unspent extra-usage balance is refundable on request and admins can export analytics reports; the included plan quota resets daily and weekly rather than accumulating, and no agent-conversation export is documented.

Checked 2026-09-03

Workflow run history exports as monthly CSV archives (Professional/Team, owner or admin only); no statement found on whether unused message credits expire or refund.

Checked 2026-09-02

Analytics, audit logs and agent configurations can be exported via API or CSV, but credits are explicitly non-transferable, non-rolling and non-refundable, so unused balance is lost each period.

Checked 2026-10-01

Agents, tools and tests pull down as files via the CLI and conversations are readable over the API, but unused paid credits expire on cancel or downgrade and rollover caps at two months.

Checked 2026-09-02

Data export is broad (citations to RIS and BIB, review stages to CSV or XLSX, reports to PDF or DOCX), but unused monthly usage expires each cycle and cancelling refunds nothing already paid.

Checked 2026-09-14

You can email for a copy of your data or for deletion of devices, but export is manual rather than self-serve and no retention procedure is defined yet.

Checked 2026-10-09

Videos leave cleanly as unlimited exports with direct MP4 download URLs, but unused plan credits expire every month; only separately purchased credit packs survive.

Checked 2026-10-03

Purchased Extra Usage credits never expire and roll over, but monthly Standard Usage does not; no account-wide data export path is documented (AutoWiki has its own export).

Checked 2026-09-02

Report data can be exported as CSV on every plan and programmatically on higher ones, but the vendor publishes nothing about whether unused Operator credits roll over, and credits are described as a monthly inclusion.

Checked 2026-09-18

Usage and results are retrievable through the dashboard and credit-usage endpoints, but purchased credits are forfeited when you cancel the subscription.

Checked 2026-09-24

Chats export one at a time as PDF, DOCX or Markdown and tables as CSV or XLSX, with bulk download explicitly unavailable and full erasure by written request; unused credits are forfeited at the end of each term.

Checked 2026-09-14

There is nothing vendor-side to export, because prompts and responses are not stored; if you want a record you route it to your own Cloud Logging bucket. Licences are seats, so no credits expire.

Checked 2026-09-02

Files can be downloaded or exported from AI Drive without spending credits and personal data is portable on request, yet credits expire every cycle and unused ones are forfeited on downgrade or cancellation.

Checked 2026-09-15

Unused credits are forfeited each month rather than banked; organisation and enterprise owners can export Copilot user activity as a CSV report.

Checked 2026-09-02

Audit logs, usage tables, org charts and agent definitions export to CSV, and Glean can stream logs to storage you own; nothing published says whether unused FlexCredits expire.

Checked 2026-09-02

Account data can be edited or deleted from within account settings and deletion can be requested, but no data export or download of saved queries and bookmarks is documented, and no credits exist to expire.

Checked 2026-10-05

Conversation data is yours on disk: sessions save to a plain JSON file and can be pointed at your own database or storage service, and no credits exist to expire.

Checked 2026-09-15

Whole sessions export to JSON, YAML or Markdown from the desktop app or goose session export, and re-import elsewhere; there are no vendor credits that could expire because nothing is bought.

Checked 2026-09-16

Reports export to PDF, Word, Markdown, JSON and CSV, run logs download as JSON, and no credits exist that could expire.

Checked 2026-09-16

Organisation-wide data export and continuous drains are an Enterprise feature, and unused credits never carry over to the next month.

Checked 2026-09-30

Export is unconditional: you can export or delete data at any time, in a portable format, and before deletion on termination. Credits, however, are use-it-or-lose-it and are forfeited at the end of each billing month.

Checked 2026-09-10

Downgrading keeps local functionality and evidence export exists on Team, but no data-export format or credit-expiry terms are published.

Checked 2026-09-29

Cancellation is any-time and all data is deleted on account closure, but no customer-facing data export path is documented and the API only covers upload and deletion of content.

Checked 2026-09-24

Export and deletion are honoured, but only by emailing from your account address, with deletion completed within thirty days; nothing published says whether purchased credits expire.

Checked 2026-09-14

Nothing is locked in a vendor account: sessions are files on your disk, per-user state in the config directory is documented as copyable to another machine, and there are no credits that could expire.

Checked 2026-09-17

Your work leaves cleanly as PowerPoint, Google Slides, Excel or CSV and you can demand full deletion, but the money does not: unused credits expire every billing cycle, cannot be transferred and are forfeited on cancellation.

Checked 2026-09-17

Unused allowance is lost rather than carried, and purchased credits expire after a year; the site documents no bulk export of sessions, plans or agent configuration.

Checked 2026-09-18

Data comes out in CSV from the dashboard and in a structured JSON/CSV portability request, deletion is available on request, and there is nothing to forfeit on exit because usage is billed after the fact with no prepaid minute bundle.

Checked 2026-09-26

Usage data has documented export endpoints and credit purchases can be refunded (the 5% fee is not); the site states nothing about credits expiring.

Checked 2026-09-02

Traces can be queried through the SDK on any plan, but scheduled bulk export to your own S3 bucket in Parquet is now Enterprise-only for new customers, with older accounts cut off in 2027.

Checked 2026-09-18

Flows export to JSON, optionally stripped of API keys, and the underlying database is a file you control, so there is no lock-in and no credit balance that could expire.

Checked 2026-09-25

Bulk trace export to an S3-compatible bucket in Parquet is Enterprise-only for anyone who signed up after 3 August 2026. Usage is metered in arrears rather than prepaid, so there is no credit balance to expire.

Checked 2026-09-02

CSV export of leads and companies is a free-plan feature and the Terms point to export before closure; what is not stated is whether monthly credits roll over or expire.

Checked 2026-09-18

Deletion is documented: the vendor actions an account deletion request within 30 days. No bulk export of calls, transcripts or configuration is described, and there is no published credit balance to expire.

Checked 2026-09-09

Memory is git-backed files you can inspect and sync to your own GitHub repo; credit expiry is never stated.

Checked 2026-09-02

Unused plan credits expire every cycle while purchased top-ups carry over, and deletion and access rights are offered; we found no documented bulk export, and cancelling leaves the workspace live only to the end of the paid cycle.

Checked 2026-09-19

The deliverable arrives in the buyer's own inbox so the output is held outside the vendor, and there are no credits to expire, but no retention, deletion or export policy is published.

Checked 2026-10-10

Recordings go straight to your own S3, GCS or Azure bucket and traces export to any OpenTelemetry backend, but unused inference credits expire monthly, observability data is kept 30 days, and metrics export APIs are Scale and above.

Checked 2026-09-02

Results export as markdown, JSON, XLSX or parquet and files can be deleted, but credits do not roll over and bonus credits vanish on downgrade.

Checked 2026-09-02

Customers keep rights to their content and session data is not retained, but no export tool is published, fees are non-refundable by default and rollover of unused minutes is never addressed.

Checked 2026-09-09

Code for anything it builds can be downloaded whole or exported to your own GitHub repo, but credits are the opposite: unused plan credits are wiped each cycle and reset to zero when a subscription ends.

Checked 2026-09-19

You own your data and can cancel any time, but retention is capped by plan (15 days to 6 months), backups are your responsibility and downgrading may delete data over the new limit.

Checked 2026-09-02

Agent decisions and logs are described as exportable with SIEM integration, which covers operational records, but nothing read states how knowledge, conversation history or configuration leave the platform at contract end.

Checked 2026-09-25

Nothing is locked in a vendor store: sessions and history go to a session store you implement over your own database or blob storage, and there are no credits to expire.

Checked 2026-09-19

The trust centre lists a control for deleting customer data on departure, but the vendor publishes nothing about exporting agents or whether prepaid usage balances expire.

Checked 2026-09-20

Conversation history and reports export from the workspace and deletion can be requested by email, but exports and API reads reach back only six months, so older history cannot be taken out.

Checked 2026-10-03

Project export is unrestricted via ZIP or GitHub push and survives cancellation, but credits expire with the billing period and have no cash value.

Checked 2026-10-09

Interaction and analytics data can be pulled out through the Data API and SIEM SFTP export, but no contractual exit, deletion or unused-balance term is published.

Checked 2026-09-20

Sessions export locally as transcripts or full JSON trajectories and account data can be requested from support within about five business days, but the export is a support ticket rather than self-serve.

Checked 2026-09-20

Workflows leave as JSON from the editor, the Server CLI (workflows, credentials, whole entities) or .n8np packages; separately, the pricing FAQ says the monthly AI credit balance refreshes and unused credits do not roll over.

Checked 2026-09-02

Account deletion is a real 30-day hard delete and export rights are honoured on request, but purchased credits expire after twelve months and monthly credits never roll over.

Checked 2026-09-29

A whole workspace exports as a single .novastart file and data copies can be requested, but nothing states whether unused agent credits expire.

Checked 2026-10-08

The privacy policy grants access and deletion of personal data on request, but nothing is published about handing over delivered systems, code or operational data at the end of an engagement.

Checked 2026-09-26

Unused balance survives plan changes and top-ups with no published expiry, and transcripts and recordings can be pulled through the call-logs API, but deletion is a manual email request and no bulk account export is documented.

Checked 2026-09-09

Paused run state serialises to JSON you store yourself and sessions can be backed by your own SQLite or Redis, so data stays portable; nothing is documented about exporting traces already sent to OpenAI's backend.

Checked 2026-09-20

Purchased credits expire after a year and are non-refundable; on the data side /v1/realtime retains no application state and the Usage permission covers dashboard export.

Checked 2026-09-02

A first-class backup command exports state, config, credentials and sessions to a verifiable archive, with SQLite snapshots and versioned Git dumps, and restore writes only to a fresh target.

Checked 2026-09-21

Sessions and code stay on your own disk and the vendor disclaims ownership, but nothing is published about expiry of unused Zen balance.

Checked 2026-09-21

You can manage and delete stored content, and deletion is by email request; no bulk data export or credit-expiry terms are published.

Checked 2026-09-21

Portability is a request under the privacy notice rather than a self-serve export, and nothing published states whether unused Computer credits expire.

Checked 2026-09-02

The CLI pulls a local copy of agents, deployments and documents, and bought credits never expire, but plan credits reset each cycle without stacking and nothing is refundable on cancellation.

Checked 2026-09-09

Transcripts, recordings and metadata export via the Conversations API or a PolyAI-configured sync to your own S3 bucket, but unused CX Tokens expire each Contract Year and fees are non-refundable.

Checked 2026-09-02

Exit is contractual rather than self-serve: an export window precedes deletion, deletion runs as a reviewed preview, legal holds are respected, and firm encryption keys are destroyed once backups expire.

Checked 2026-10-06

Prepaid Gateway credits are non-refundable and expire after twelve months of account dormancy; Logfire data is exportable over its query API and Growth adds self-serve deletion.

Checked 2026-09-02

Data can be pulled out programmatically through the v2 API into a warehouse or CDP and individuals can be deleted by API, but API access sits in the Enterprise tier and no contract exit or credit-expiry terms are published.

Checked 2026-09-22

Data exports in CSV, Excel or JSON are available at any time, and unused Vendor Credits roll over indefinitely while the subscription stays active rather than expiring.

Checked 2026-09-22

Source leaves cleanly as a zip or through GitHub sync, but purchased credits expire six months out and do not roll over.

Checked 2026-09-22

Filtered call and chat history exports to CSV including transcripts, and list/get APIs cover the same data; purchased credits never expire but are non-refundable once bought.

Checked 2026-09-23

Leads and conversations can be pulled out through the API or pushed via webhooks and the subscription cancels in one click, but no bulk account export is documented.

Checked 2026-10-11

Transcripts can be copied one call at a time and calls deleted individually, but no bulk export is documented, unused minutes are never credited, and content retention after you leave is at the vendor's discretion.

Checked 2026-09-09

Unused Agent Actions expire every cycle and do not roll over; on the way out the DPA obliges Rox to return or destroy customer personal data on written request, and agent-generated artefacts download as PPTX or DOCX.

Checked 2026-09-03

You can request access or deletion, but the vendor explicitly refuses to promise a deletion period for voice-agent data and makes the outcome depend on each provider's capabilities.

Checked 2026-09-28

Data is exportable during the term and returnable for 30 days after termination, though insights, reports and scoring may be manual-export-only; unused Flex Credits do not roll over between subscription terms.

Checked 2026-09-03

Deletion or return at the customer's choice is contractual, but export is left to the customer before termination and scrape export links expire after seven days.

Checked 2026-09-25

Credits never expire and carry over between cycles, articles stay accessible after cancellation, and the REST API and client library let a buyer pull every published article out programmatically.

Checked 2026-09-25

Content exports to spreadsheet or JSON on any plan, published work stays in your own CMS if you cancel, and purchased credit packs roll over until used.

Checked 2026-10-03

A control commits to deleting customer data on departure, yet no customer-facing bulk export path or credit-expiry rule is published.

Checked 2026-09-26

Purchased credits never expire, but the weekly refresh allowance does not carry over; data leaves through the API, CLI and table exports rather than a one-click account export.

Checked 2026-09-03

Deletion is documented and self-service under the data-processing agreement, but no data-export path is published and nothing states whether unused package minutes roll over.

Checked 2026-09-03

Export and deletion exist as rights exercised by email plus some in-product purge controls, not as a self-serve export button; backups may retain data after deletion.

Checked 2026-10-03

Call notes and data export in three formats are listed as product capabilities and subscriptions cancel in one tap, but no bulk account-export or data-deletion procedure is documented.

Checked 2026-09-26

Export exists but is not self-serve: data is available for 30 days after termination through support or the DPA, and Tables has no export button at all.

Checked 2026-09-15

Projects export to a JSON file you can keep or re-import, and analytics are downloadable; runs are a monthly allowance rather than credits that accrue.

Checked 2026-09-09

Manual CSV export of call logs is available to all; scheduled exports to S3, BigQuery or SFTP are Enterprise-only, and unused minutes carry over only if the agreement says so.

Checked 2026-09-03

On termination the customer can demand return of all data in a machine-readable format or certified deletion, and there are no credits to expire.

Checked 2026-10-03

Statutory GDPR portability covers personal data, but nothing on the site describes exporting agent memory vaults or workflow definitions, and the same terms make fees non-refundable.

Checked 2026-09-12

You keep ownership of recordings and transcripts, may request a copy of personal data and can set retention yourself, but no self-serve bulk export is documented and metrics export is an Enterprise line; billing is metered, so no prepaid credits can expire.

Checked 2026-09-16

Conversations, CDRs and usage reports are exportable by API or CSV and deletion can be requested within thirty days, but Telnyx says account configurations cannot be transferred and states no policy on unused balance.

Checked 2026-09-09

Runs and their artifacts are retrievable through the API, and paid balance never expires, but promotional balance expires in 12 months and is forfeited on termination.

Checked 2026-09-03

You can export agent audit data from the AI Trust Layer Audit tab and request deletion, but export is documented as an Enterprise-plan feature, exports expire after seven days, and no UiPath page states what becomes of unused Platform or Agent units at contract end.

Checked 2026-09-03

You own inputs and outputs and can demand complete deletion at any time, but no bulk export path is documented and workspace files are only reachable through the app or MCP tools.

Checked 2026-09-26

A Bulk API exports large sequence datasets and unused top-up credits carry over twelve months, but the terms warn that account termination may destroy customer data.

Checked 2026-09-27

Credits are bought upfront and spent over any time frame rather than lapsing at month end.

Checked 2026-09-03

Results can be saved to the File Library or downloaded and an eligible top-up balance survives cancellation, but no bulk export of workspaces or task history is documented.

Checked 2026-09-27

The workspace is exportable at any time and deletable on request, and self-hosted installs can be archived to a tarball from the CLI before removal.

Checked 2026-09-27

Deletion is immediate and thorough and numbers are released back to the carrier, but no bulk export of calls, transcripts or messages is documented — the read-only connector is the nearest thing to a data-out path.

Checked 2026-09-22

Export is real: transcripts via API, CSV/JSON log exports from Growth up, and a 30-day post-termination export window. But no page states whether unused minutes or topped-up credits expire, and partial billing periods are non-refundable.

Checked 2026-09-03

Export is available during the term and deletion or return happens within about 30 days of termination, but prepaid minute packs and top-ups are non-refundable once applied, so unused balance is lost on exit.

Checked 2026-10-03

Data exports to CSV or syncs to the CRM, but the credit pool refills each calendar month rather than rolling unused credits over.

Checked 2026-09-03

Account and data deletion is self-serve within 30 days, and Drive notebooks and workflows export as Markdown and YAML, but no bulk export tool is documented. Monthly plan credits expire each cycle; purchased credits last 12 months and are forfeited if you leave the team.

Checked 2026-09-03

Outputs leave cleanly in ordinary formats and via an export endpoint, but the vendor states nothing about whether unused prepaid credits expire or can be refunded.

Checked 2026-09-27

There is nothing to export from a vendor: session state, event logs and tool output are plain JSON and JSONL files on your own disk.

Checked 2026-09-21

Threads can be opened and copied out as Markdown, and monthly included credit resets rather than accumulating, but no bulk account data export is documented.

Checked 2026-09-29

Audit logs and analytics export as CSV and repository indexes are deletable on demand, but plan credits expire every billing period with no rollover and top-ups are non-refundable.

Checked 2026-09-09

Unused resolution allowance expires each usage period; account data exports to JSON/CSV/XML exist off Team plans, and Zendesk's docs state AI agent tickets cannot be exported.

Checked 2026-09-03

Transcripts are plain local JSONL and can be exported to a portable session file or a JSON timeline dump; nothing is held server-side and no credits exist to expire.

Checked 2026-09-28