Data retention | Runtype Documentation

Runtype saves your application configuration, conversations, and run history. Model providers and connected services can keep their own copies of content that you send them. Deleting data in one place doesn’t delete those other copies.

This guide lists what is stored, when it expires, and how to request deletion. Zero data retention (ZDR) applies to supported model requests, not to all data in your Runtype account.

Saved application data

The following data doesn’t expire when your log retention period ends:

Data	What Runtype stores	How long it stays	How to delete it
Flows, Agents, Apps, Products, Surfaces, Tools, Skills, and Schedules	Prompts, configuration, saved versions, and permissions.	Until you delete the saved resource. Pausing or unpublishing it doesn’t delete it.	Delete the resource from its dashboard page or through the API. Copies in logs and audit entries can remain.
Records and collections	Record content, metadata, messages, results saved to Records, and collection definitions.	Until you delete them.	Delete Records on the Records page. Deleting a collection definition doesn’t delete its Records.
Conversations	Messages, participants, channel details, and references to attachments. This includes saved chats and messaging conversations.	Until you delete the conversation. Turning verbose logging off doesn’t delete saved messages.	Delete the conversation in Runtype. Also delete any exported transcript or copy in Slack, email, or another messaging service.
Agent memory	Facts, saved text, and summaries used in later runs.	Runtype doesn’t set an automatic expiry for saved memory.	Contact support to request deletion. Include the Agent and memory profile. Turning memory off or deleting a chat doesn’t erase saved memory.
Retrieval and vector search	Source documents, extracted content, and search embeddings.	Saved Records stay until deleted. A connected vector database has its own retention settings.	Delete the source Records and any copies in the vector database. Disconnecting the database doesn’t delete its contents.
Evals, simulations, and test datasets	Saved test cases, expected answers, scores, and run results.	Saved test cases and scores don’t have an automatic expiry. Detailed run logs follow your plan’s log window.	Delete cases or the Eval suite. Deleting a suite removes its cases but preserves past scores. Contact support to request removal of those scores.
API keys and provider connections	API key records, encrypted provider credentials, and connection settings.	Until you delete them. Disabling or revoking access doesn’t delete saved records.	Delete the key or connection in Settings. Revoke unused provider keys with the provider too. Audit entries can retain identifying details.
Membership, billing, and usage	Account details, organization membership, invoices, and usage records.	These records don’t use the log retention window. This guide doesn’t specify a fixed deletion period for them.	Contact support for account closure or deletion of account, billing, or usage data.

For Record deletion, including the single-Record undo window, see Creating and managing Records. For case and suite deletion, see Managing Eval suites.

Logs, traces, and audit history

Run logs can contain status, timing, errors, inputs, outputs, and model transcripts. The following plan windows determine how far back you can view logs:

Plan	Log history available
Launch	1 day
Team	90 days
Enterprise	Your agreed retention window

The Logs page shows your plan’s window. Entries outside that window are no longer available to query. Deleting stored copies can take longer, so the window isn’t a deadline for erasing every copy. For a required deletion date, contact support. For plan details, see Log retention by plan.

Audit entries record who changed a resource and can include its content before and after the change. The Activity views show the last 30 days. The Logs page also provides audit history, subject to plan limits. Deleting a resource doesn’t erase its audit entries. For a deletion request that includes previous versions of content, include audit history in your request.

Exported logs stay wherever you saved them until you delete them there.

Files, pages, and sandbox data

File expiry and download-link expiry are different. An expired download link stops that link from working; it doesn’t delete the file.

The following table covers files and temporary environments:

Data	What is stored	Expiry	How to remove it
Private stored files	Uploaded or generated files, including documents, images, and audio.	Files expire 30 days after storage. A signed download link expires after 1 hour by default.	Contact support for early removal of a stored file. Delete downloaded copies wherever you saved them.
HTML preview pages	The published HTML.	The expiry returned when you publish the page depends on your plan and requested lifetime. Some plans allow no expiry.	Contact support for early removal. Include the page URL or asset ID.
Public stored files	Files published at a public URL.	No expiry unless one was set when the file was stored.	Contact support to remove a stored file. Removing a link from your app doesn’t remove the public file.
Sandbox deployments	Files and running software inside the sandbox.	The deployment response shows its expiry, or no automatic expiry. An idle timeout stops the server, not every saved copy.	Destroy the sandbox with the `destroy_sandbox` tool or the sandbox deletion API. Delete exported files separately.
CLI Marathon tasks	Local conversation history, checkpoints, and saved tool outputs.	Local task files remain on your computer until you delete them.	Delete the task’s saved files and any backups on your computer. Stopping a task keeps its resumable state.

File expiry stops Runtype from serving the file. It isn’t a guaranteed deadline for deleting every stored copy. Use the returned file expiry rather than the expiry on a download link when deciding how long a file remains available.

For sandbox expiry settings and deletion commands, see Sandbox deployments. For the location of local task files, see Where Marathon stores state.

For hosted long-running Agents, stopping a run doesn’t delete its saved conversation, checkpoints, or exported files. To request removal of saved session data, contact support with the Agent and session IDs.

Model providers and connected services

A model request can include your prompt, conversation history, retrieved Records, tool results, and files. This includes voice, image, and other media requests. The provider’s retention agreement determines how long it keeps that content.

Bring your own key (BYOK) selects your provider connection. It doesn’t bypass Runtype or give your provider account a ZDR agreement. With inference ZDR enabled, Runtype sends supported requests through Vercel AI Gateway with ZDR required. Unsupported requests fail rather than run without that requirement.

If you store your provider keys in Vercel, mark them as ZDR-eligible only when your provider agreement covers ZDR. Otherwise, Vercel excludes those keys from ZDR requests. Your Vercel fallback settings still apply. For details, see Vercel’s ZDR policy.

Prompt caches, uploaded files, background jobs, and provider-hosted tools can have different retention rules. Turning caching off doesn’t delete content already cached. Check the provider’s rules for each feature you use, such as OpenAI’s API data controls. For Runtype cache settings, see Prompt caching.

Connected apps and tools keep the messages, documents, and other content you send them according to their own policies. Delete those copies in the destination service. Disconnecting an integration doesn’t delete content already sent.

Webhook payloads can remain stored while delivery or retries are pending. Runtype deletes the payload after processing finishes, including after a final failure. The log window doesn’t control that deletion. To request removal of a pending payload, contact support with the Surface and delivery details.

For self-hosted execution, you control data stored by your application. Logs and results that you export to Runtype follow the Runtype rules in this guide. Other monitoring services apply their own retention settings to exported copies.

What the privacy controls change

The settings affect different copies of your data:

Control	What it changes	What it doesn’t delete
Require your own model keys	Requires your organization’s model connection and blocks fallback to Runtype platform keys.	Saved content in Runtype or data already sent to a provider.
Zero data retention (ZDR)	Requires ZDR for supported model requests.	Records, conversations, memory, logs, files, or data already sent to a provider.
Verbose logging	Turning it off omits detailed inputs, outputs, and model transcripts from future run logs. Status, timing, and errors can still be recorded.	Existing logs, saved conversations, Records, or memory.
PII redaction	Masks supported personal-data patterns in log content.	Original messages, saved conversations, or content sent to models and tools. It doesn’t detect every kind of sensitive data.

For model controls, open Settings > Models > Advanced settings and see Managing AI models. For logging controls, see Logging policy and PII redaction. Error messages can contain sensitive content even when verbose logging is off. Avoid putting secrets in prompts, resource names, or errors.

Deletion requests and account closure

Deleting a Record, conversation, or other resource removes that saved item. Logs, audit entries, memory, exported files, and provider copies can still contain some of the same content. Backups can also retain data after you delete the live copy. This guide doesn’t promise a single deletion deadline for all those copies.

For account closure, backup deletion, or data without a self-service delete option, email Runtype support. Include the following:

Your organization and the affected resource IDs or URLs.
The data to remove, including any conversations, memory, logs, audit history, files, and backups.
Any deletion deadline that you need confirmed.

Request deletion from model providers and connected services separately for copies held under your accounts there.

Next steps

Use these guides to manage saved data and exports:

Using memory steps: check what your Flows save for later use.
Working with logs: view and export run logs.
Audit trail: inspect changes and saved content snapshots.
Reporting external telemetry: choose what your application sends to Runtype.