A native export from ChatGPT, Claude, or another supported tool goes in. Separated, indexed, readable files come out, with visible warnings for anything missing or malformed.
No public file uploads. Local software does not require sending source files at all.
Most clean exports do not need a human being involved. FlameSync would rather hand you the tool than bill you for work software can do.
The Archive & Evidence Studio runs on your computer. Nothing is uploaded, nothing is retained by FlameSync, and the free edition covers a single supported export.
Choose this when your export is clean, in a supported format, and you are comfortable running an application.
See the StudioA bounded human service for when you want someone to validate the package before you rely on it, or when the source is malformed, mixed, or incomplete.
Choose this when the archive matters enough that a second pair of eyes is worth paying for, or the export already failed.
See human-checked archivesOne-time licenses, no forced subscription, no account required for core use.
A local-first starting point for converting one supported AI export into readable, organized files on your own computer.
In development
In development. The Studio is released only after its export-integrity, installer, backup and restore, privacy, documentation, and support test gates pass. Join the waitlist to be notified.
Best for: Anyone who wants to see their AI export as organized files before deciding whether they need anything more.
Scope boundary: Personal, non-commercial use. One export processed at a time.
Next step: Start here, then move up an edition only if you need manifests, checksums, or project continuity.
Full local archive packaging with manifests, checksums, warnings, and a searchable index.
In development
In development. The Studio is released only after its export-integrity, installer, backup and restore, privacy, documentation, and support test gates pass. Join the waitlist to be notified.
Best for: Archive owners who want a verifiable, portable record of their AI work without sending files to anyone.
Scope boundary: Personal use on one device. Supported export formats are published with each release.
Next step: Move to Professional if you need project workspaces, decisions, and handoff packages.
Manual archive work is deliberately capped so it never crowds out the diagnostic and evidence work it exists to support.
A person checks and validates the packaged archive when you want more than software output.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Clean supported exports where someone needs a human to confirm the package is sound before relying on it.
Scope boundary: Bounded limits confirmed at preflight. Manual archive jobs are capped at 12 in the first full year.
Next step: Request a Readiness Scan if the archive turns out to be mixed or unclear.
The same human-checked packaging for a larger clean export, quoted after a compatibility preflight.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Larger archives that are still clean and in a supported format.
Scope boundary: Quoted after preflight. Counts toward the 12 manual archive jobs available in the first full year.
Next step: Move to a Readiness Scan if the preflight shows mixed or damaged sources.
Best-effort reconstruction when an export is malformed, copied, mixed, or incomplete.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Archives that failed a normal conversion, or sources assembled from several places over time.
Scope boundary: Best effort only, quoted after a paid preflight. Some sources cannot be recovered.
Next step: Decide, with the preflight in hand, whether recovery is worth doing at all.
Conversion verifies package structure: file counts, hashes, manifests, and warnings. It does not verify whether anything said inside those conversations is accurate, complete, or authentic. A successful conversion demonstrates only that the supplied data was processed under the documented rules.
Describe the archive and what you are trying to do with it. FlameSync recommends the smallest responsible option, including the free one.
