What an export actually contains

An export is the only part of a companion app you can hold in your own hands, which makes it worth more attention than it usually gets. It is also a feature somebody built to a specification, so what appears in the file was decided rather than discovered. Requesting one while you have nothing at stake is the cheapest useful thing you can do with one of these products.

An export button and a data-access right are not the same thing

In some jurisdictions people have a statutory right to obtain a copy of personal data held about them. An export button is one way an operator can satisfy that, and it is not necessarily the same scope. The button returns what the engineering team put in it. A formal request under an access right returns what the law requires, which is often broader, and is handled by a process described in the privacy policy rather than by a button in settings.

So there are potentially two doors, and they open onto different rooms. The policy section headed your rights, access, or data subject requests describes the second one, usually with an address or a form and a response window in days. Most people only ever try the first.

What is usually in the file, and what usually is not

The reliable contents are your messages and the replies, with timestamps, organised by conversation. That is the core and it is what the product would be storing anyway.

Everything else varies, and the omissions are consistent enough to predict. The character description is generally absent, because it is the operator’s asset rather than your personal data — which is a defensible position and also means the thing that made the conversation what it was does not come with the conversation. There is no entity in the file, only the transcript.

Memory artefacts are usually absent too: the running summaries, the extracted fact list, the profile derived from your onboarding answers. Those are internal representations, and each kind of memory is a constructed thing rather than a record you submitted. Generated images and voice audio are often omitted or replaced by links that expire. Settings, subscription history and telemetry are sometimes included and sometimes not.

The practical upshot: an export typically preserves what was said and loses the apparatus that produced it.

Format decides whether you can actually read it

Three shapes are common and they are not equally useful.

A structured data file — JSON or CSV — is complete and awkward. Everything is there, nothing is readable at a glance, and a long history is a wall of syntax. It is the best archival option and the worst reading option.

A rendered document — HTML, or a PDF — is readable and lossy. Formatting choices become part of the record and metadata is often dropped.

A plain text dump sits in between and usually loses conversation boundaries.

None of these is wrong. What matters is checking which you got, because a file you cannot open in five years is not an archive. A structured file plus a rendered copy is the version that survives both problems, where both are offered.

Timing is a real constraint

Exports are frequently asynchronous: you request, and a link arrives by email later. Those links commonly expire after a stated number of days. The generation itself may be rate-limited to one request per period. Some apps place export behind a paid tier, which means the ability to take a copy can disappear at the same moment as everything else if a subscription lapses.

That is why the advice is always to do this early. The moment you most want an export is the moment a shutdown email arrives or a subscription ends, and both of those are the moments when the mechanism is least likely to be available. A wind-down is not when features get built.

THE PRODUCT — the export

  · "Export my data"
                    → a file built to a specification. Its
                      contents were chosen, not discovered.

  · What is in it
                    → messages and timestamps, reliably.

  · What is usually not
                    → the character description, memory
                      summaries, extracted facts, generated
                      media.

  · A download link
                    → often expiring, often rate-limited,
                      sometimes behind a paid tier.

  · Scope, format, expiry, availability
                    → THE OPERATOR DECIDES all four, and can
                      change them.

  · Whether a broader access right applies to you
                    → CHECK THE POLICY. Search "your rights",
                      "access", "portability", "request".

  · Whether an export exists at all
                    → VARIES BY APP.

What you can do

Request one now, not later. Then open it. Ten minutes establishes whether the export is a real archive or a gesture, and that finding does not change much over time.

Check it against what you would actually want back. If the conversation matters, does the file have the whole conversation. If the character mattered, note that it is not in there, and that this is not a bug.

Store it somewhere that is not the phone. An export sitting in a downloads folder is one lost device away from not existing.

If the button is thin, look for the rights process. A formal access request is slower and its scope is defined by law rather than by a product decision.

What this doesn’t tell you

It does not tell you what any specific app’s export contains. That is per-app, changes with releases, and would be invented if stated here.

It does not tell you what legal rights you have, which depends entirely on where you are and is outside what a product explainer can establish.

And it does not tell you that an export preserves the experience. It preserves the text. The rest of it was reassembled fresh on every turn and there was never a copy of that to take.