What Import is

Import is a section of the Ployed console. Opening it starts nothing: no file is read and no account is contacted until you pick a source and start an import yourself. Previewing a file doesn't start ongoing capture either.

Imported records are observations of work done elsewhere. Ployed never re-runs that work, never repeats a tool call it finds in a transcript, and never treats imported text as instructions.

Your Ployed employees

Every organization sees one built-in row for its own Ployed employees. It shows how complete the recorded history is and links to the places those records already live: Work, Ledger and Workflows. Import keeps no second copy of that history.

Supported products

This table is generated from the same product registry the service uses, so it changes only when the product does. Available means it works in every organization. Limited release means it is built and tested with sample files but is not open to every organization. Not available yet means it cannot be used today; the row says what is still missing. "Planned" describes how a product would connect once it opens, not something you can turn on now.

Scroll sideways to see all six columns: Product, Provider, How it connects, History it can read, Ongoing capture, and Status today.

Product	Provider	How it connects	History it can read	Ongoing capture	Status today
Your Ployed employees' work	Ployed	Already in Ployed	Work your Ployed employees already did	Yes, as work happens	Available in every organization
Codex local sessions	OpenAI	Upload session files from your computer	What the file contains when you upload it	No	Limited release. Built and tested with sample files; opens only where Ployed has opened archive import for your organization. Still needs an approved consent notice, approval of where records are stored, testing with a real account.
Claude Code local sessions	Anthropic	Upload session files from your computer	What the file contains when you upload it	No	Limited release. Built and tested with sample files; opens only where Ployed has opened archive import for your organization. Still needs an approved consent notice, approval of where records are stored, testing with a real account.
OpenCode sessions (export JSON)	OpenCode	Upload session files from your computer	What the file contains when you upload it	No	Not available yet. Still needs an approved consent notice, approval of where records are stored, a review of the provider's terms, testing with a real account.
Kimi Code sessions (kimi export)	Moonshot	Upload session files from your computer	What the file contains when you upload it	No	Not available yet. Still needs an approved consent notice, approval of where records are stored, a review of the provider's terms, testing with a real account.
Qwen Code sessions (chat JSONL and /export jsonl)	Qwen	Upload session files from your computer	What the file contains when you upload it	No	Not available yet. Still needs testing with a real export, an approved consent notice, approval of where records are stored, a review of the provider's terms, testing with a real account.
Personal ChatGPT archive	OpenAI	Upload a data export from your own account	What the file contains when you upload it	No	Not available yet. Still needs a review of the provider's terms, testing with a real export, an approved consent notice, approval of where records are stored.
Personal and Team Claude archive	Anthropic	Upload a data export from your own account	What the file contains when you upload it	No	Not available yet. Still needs a review of the provider's terms, testing with a real export, an approved consent notice, approval of where records are stored.
Gemini Apps Takeout	Google	Upload a data export from your own account	What the file contains when you upload it	No	Not available yet. Still needs a review of the provider's terms, testing with a real export, an approved consent notice, approval of where records are stored.
DeepSeek chat export	DeepSeek	Upload a data export from your own account	What the file contains when you upload it	No	Not available yet. Still needs a review of the provider's terms, testing with a real export, an approved consent notice, approval of where records are stored.
Ollama application	Ollama	Instrumentation in your own application	Only what was logged after logging was turned on	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Stored Chat Completions	OpenAI	Read what the provider kept, through your connected account; Instrumentation in your own application	What the provider still keeps	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
Responses and Conversations	OpenAI	Read what the provider kept, through your connected account; Instrumentation in your own application	Only items whose IDs your own logging recorded	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
Hosted Agents sessions	OpenAI	Read what the provider kept, through your connected account	What the provider still keeps	Planned: yes, as work happens	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
Claude Managed Agents sessions	Anthropic	Read what the provider kept, through your connected account	What the provider still keeps	Planned: yes, as work happens	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
Message Batches results	Anthropic	Read what the provider kept, through your connected account	What the provider still keeps	No	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
Conversations (Agents API)	Mistral	Read what the provider kept, through your connected account	What the provider still keeps	No	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
Grok API stored responses	xAI	Read what the provider kept, through your connected account; Instrumentation in your own application	Only items whose IDs your own logging recorded	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
Gemini API Interactions	Google	Read what the provider kept, through your connected account; Instrumentation in your own application	Only items whose IDs your own logging recorded	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, testing with a real account, a review of the provider's terms.
AI Studio logs and datasets export	Google	Upload session files from your computer	Only what was logged after logging was turned on	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Vibe account export	Mistral	Upload a data export from your own account	What the file contains when you upload it	No	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Grok Build Markdown export	xAI	Upload a data export from your own account	What the file contains when you upload it	No	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Messages API	Anthropic	Telemetry your own exporter sends; Instrumentation in your own application	Only what was logged after logging was turned on	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Cloud model and agent logs	Google	Model logs in your own cloud account	Only what was logged after logging was turned on	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Generation logs and Broadcast	OpenRouter	Read what the provider kept, through your connected account; Telemetry your own exporter sends	Only items whose IDs your own logging recorded	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
ChatGPT, Work and Codex cloud	OpenAI	An enterprise compliance feed	What the provider still keeps	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Dots	OpenAI	An enterprise compliance feed	What the provider still keeps	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Claude Enterprise	Anthropic	An enterprise compliance feed	What the provider still keeps	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Claude Design and Artifacts	Anthropic	An enterprise compliance feed; Upload a data export from your own account	What the provider still keeps	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Kimi and Moonshot API	Moonshot	Instrumentation in your own application; Upload session files from your computer	Only what was logged after logging was turned on	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
DeepSeek API and archive	DeepSeek	Instrumentation in your own application; Upload a data export from your own account	Only what was logged after logging was turned on	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
GLM API	Z.AI	Instrumentation in your own application	Only what was logged after logging was turned on	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
MiniMax API	MiniMax	Instrumentation in your own application	Only what was logged after logging was turned on	Planned: only from code you instrument	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Grok Bot enterprise	xAI	An enterprise compliance feed; Telemetry your own exporter sends	Only what was logged after logging was turned on	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Bedrock invocation logs	Amazon	Model logs in your own cloud account	Only what was logged after logging was turned on	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
Azure model gateway logs	Microsoft	Model logs in your own cloud account	Only what was logged after logging was turned on	Planned: after each request completes	Not available yet. Still needs an approved way to hold provider access, a review of the provider's terms, testing with a real account.
OTLP exporter and Ployed capture SDKs	OpenTelemetry	Telemetry your own exporter sends; Instrumentation in your own application	Only what was logged after logging was turned on	Planned: only from code you instrument	Not available yet. Still needs a release decision, testing with a real account, a review of the provider's terms.

Some providers keep only part of your history, keep it for a limited time, or record only what you logged after turning logging on. Import shows a gap where a provider didn't keep something; it never fills one in. If a source doesn't report usage or cost, Import shows it as unknown, not zero.

What you need for each product

Ployed never asks for your provider password, session cookies or browser login, and never signs in to a provider as you.

Scroll sideways to see all two columns: Product, and What you need.

Product	What you need
Your Ployed employees' work	None. This is your own Ployed organization.
Codex local sessions	Session files on your own computer. No login or provider key is shared with Ployed.
Claude Code local sessions	Session files on your own computer. No login or provider key is shared with Ployed.
OpenCode sessions (export JSON)	Session files on your own computer. No login or provider key is shared with Ployed.
Kimi Code sessions (kimi export)	Session files on your own computer. No login or provider key is shared with Ployed.
Qwen Code sessions (chat JSONL and /export jsonl)	Session files on your own computer. No login or provider key is shared with Ployed.
Personal ChatGPT archive	A data export you download from your own account. No login or provider key is shared with Ployed.
Personal and Team Claude archive	A data export you download from your own account. No login or provider key is shared with Ployed.
Gemini Apps Takeout	A data export you download from your own account. No login or provider key is shared with Ployed.
DeepSeek chat export	A data export you download from your own account. No login or provider key is shared with Ployed.
Ollama application	Instrumentation in your own application.
Stored Chat Completions	Your own provider API account, connected to Ployed.
Responses and Conversations	Your own provider API account, connected to Ployed.
Hosted Agents sessions	Your own provider API account, connected to Ployed.
Claude Managed Agents sessions	Your own provider API account, connected to Ployed.
Message Batches results	Your own provider API account, connected to Ployed.
Conversations (Agents API)	Your own provider API account, connected to Ployed.
Grok API stored responses	Your own provider API account, connected to Ployed.
Gemini API Interactions	Your own provider API account, connected to Ployed.
AI Studio logs and datasets export	An export from your own account.
Vibe account export	An export from your own account.
Grok Build Markdown export	An export from your own account.
Messages API	Telemetry export turned on in your own provider account.
Cloud model and agent logs	Your own cloud account, with model logging turned on.
Generation logs and Broadcast	Your own provider API account, connected to Ployed.
ChatGPT, Work and Codex cloud	An entitled enterprise workspace and an administrator or compliance key.
Dots	An entitled enterprise workspace and an administrator or compliance key.
Claude Enterprise	An entitled enterprise workspace and an administrator or compliance key.
Claude Design and Artifacts	An entitled enterprise workspace and an administrator or compliance key.
Kimi and Moonshot API	An export from your own account.
DeepSeek API and archive	An export from your own account.
GLM API	Instrumentation in your own application.
MiniMax API	Instrumentation in your own application.
Grok Bot enterprise	An entitled enterprise workspace and an administrator or compliance key.
Bedrock invocation logs	Your own cloud account, with model logging turned on.
Azure model gateway logs	Your own cloud account, with model logging turned on.
OTLP exporter and Ployed capture SDKs	Your own exporter or SDK, sending to a Ployed ingest credential that can only write to that one source.

Who can see an import

A source you import yourself is private to you. Organization owners and administrators can't open it, and your Ployed employees don't read it, use it as memory or act on it. Company-wide sources, shared with your organization, are not available yet.

What is stored

Credentials are removed first. Before anything is stored, Ployed removes text shaped like keys, tokens and passwords, and records only what kind of secret it removed and how many. A secret written as ordinary prose, with nothing marking it as one, can be missed, so check what you choose to upload.
Files a transcript mentions are not fetched. Attachments and files referenced by a session stay where they are.
Re-uploading is safe. Each upload is compared with what you already imported. Unchanged records are skipped, and an upload with nothing new reports "Already imported" instead of adding duplicates.
Records are kept until you delete them. Imports stay until you delete the source, you leave the organization, or the organization is deleted.

Pause, disconnect, delete and export

Scroll sideways to see all three columns: Action, What happens, and Your records.

Action	What happens	Your records
Pause	Stops new imports for the source. In-progress work stops where it is. You can resume later.	Kept and readable.
Disconnect	Stops the source for good. It can't be resumed; connecting again means setting the source up again.	Kept and readable until you delete them.
Delete	Removes the source and everything imported from it. The source is closed to reading at once, then storage and search indexes are cleared and checked. The source shows "deleting" until that check completes.	Deleted. A record of the deletion stays, so uploading the same files again won't bring the content back.
Export	Downloads your imported records as JSON, one bounded page at a time, with a manifest of stable record IDs and checksums.	Unchanged. Export before you delete: a deleted source can't be exported.

Deletion covers Ployed's active storage. How long backup copies persist is not yet published. If your organization has placed a legal hold, deletion waits until the hold is released. When you leave an organization, deletion of your private imports there is queued automatically.

Notices

Before an import starts, Import shows a notice for that kind of source and records which version you accepted. Each notice has a fixed name so you can tell which terms applied to which source.

Scroll sideways to see all two columns: Notice, and Covers.

Notice	Covers
`ployed.private-agent-archive/1`	Uploading your own coding-agent session files as a private source
`ployed.member-import-policy-narrowing/1`	Narrowing what an existing private source may keep (not available yet)
`ployed.private-local-collector/1`	A collector on your own computer (not available yet)
`ployed.private-telemetry-observations/1`	Telemetry from your own exporter (not available yet)
`ployed.private-retained-api-observations/2`	Reading what a provider kept, through your connected account (not available yet)
`ployed.private-portable-observations/1`	Bringing a Ployed export back in (not available yet)
`ployed.company-agent-observation/1`	Company-wide sources shared with your organization (not available yet)

Accepting a notice for Import doesn't permit any other use of your records. Using imported records for an assessment needs its own, separate consent.

Pricing

Removing data is free. Pausing, disconnecting and deleting never wait on a payment or a credit balance. Import has no price of its own published today. Where a part of Import may carry a charge, no price is published yet, and that part is not available yet.

Support

See Support. Email support@ployed.org with the source name as it appears in Import, what you did, and the UTC time. Never send session files, transcripts, exports, keys or tokens. For deletion or access requests, email privacy@ployed.org. Support can't open a private import on your behalf.

Your AI work, in one private view.