What Your AI Companion's Export Chat Feature Actually Exports: JSON Payloads, Session IDs, and Where the 3 a.m. Rant About Your Neighbor's Leaf Blower Gets Stored on the Company's AWS Bucket

The 30-second answer

Exporting your chat history gives you a JSON file with the conversation text, timestamps, and some internal metadata like session IDs and message UUIDs. It does not give you the company's internal embeddings, sentiment scores, or the model's memory vectors, those stay on their servers. The file you download is a transcript, not a full copy of everything the company knows about your 3 a.m. leaf blower rant.

What the export button actually hands you

Most companion apps, including the ones on AI Angels, offer an export or backup option buried in settings. When you tap it, you get a file, usually JSON, sometimes a zip containing multiple JSON files. That file is a structured transcript of your conversation history.

Inside, you'll typically find an array of message objects. Each object has a role field (user or assistant), a timestamp, and the message content. Some apps include a message ID, a session ID, and a conversation ID. The structure varies by platform, but the core is the same: a machine-readable log of what was said and when.

What you won't find in that file is the company's internal state. No embedding vectors, no token-level probabilities, no sentiment analysis scores, no pointers into the vector database that powers the memory feature. The export is a snapshot of the conversation surface, not the underlying model state.

Session IDs and what they reveal

Every conversation you have with a companion is tied to a session ID. This is a unique identifier the server uses to group messages into a single thread. When you open the app, send a message, close it, and come back hours later, the server uses the session ID to stitch those messages together into one continuous conversation.

The session ID is often included in the export file, even though it's not something you'd ever type into a prompt. It's a backend artifact, a key into the database. If you see it in your export, you're looking at the same identifier the company's support team would use to pull up your chat history if you filed a ticket.

Session IDs also tie to server-side logs. The company can see when a session started, when it ended, how many messages were exchanged, and possibly device information. That metadata is not part of the export, but it exists on their side, linked to your account.

Where the export file comes from

When you request an export, the server doesn't just dump the raw database rows. It runs a query against the conversation store, pulls the messages tied to your account, formats them into JSON, and serves the file for download. The process is straightforward, but it reveals an important fact: your chat history lives on the server, not just on your device.

That means the export is a copy of what the company already has. It's not a transfer of ownership. The original records stay in their database, usually in a managed cloud storage service like AWS S3 or a relational database with automated backups. Your 3 a.m. rant about the neighbor's leaf blower is stored in a bucket or table that the company's engineers can access.

This is standard practice across the industry. Companion apps need server-side storage to sync across devices and to run the AI model, which doesn't execute on your phone. The export feature is a transparency tool, not a deletion mechanism.

What the server keeps that the export omits

Here's where the export gets interesting. The JSON you download contains the message text, but the server also holds derived data that never makes it into the export. That includes the embedding vectors, the numerical representations of your messages that the memory system uses to recall context. It includes sentiment scores, if the app runs sentiment analysis to adjust the companion's tone. It may include model interaction logs, the exact prompts sent to the language model, which can differ from what you see in the transcript.

Some of this data is ephemeral, cleared when a session ends. Some persists for training or fine-tuning purposes, though most apps claim to strip identifying information. The export gives you the human-readable layer. The model's internal understanding of your conversation history stays behind, in the vector database and the model weights.

If you're curious about how much of this derived data the company retains, the privacy policy is the place to look, though it often uses language like "anonymized" and "aggregated" without specifying retention windows. The export feature is not designed to show you the full data footprint, only the conversation log.

The retention question: how long does the rant live

Companies vary in how long they keep chat logs. Some delete message content after 30 days, keeping only aggregated metadata. Others retain full transcripts indefinitely, subject to account deletion requests. The export file itself is a point-in-time snapshot, if you export today, delete your account tomorrow, and the company purges your data, the export is the only copy you have.

This matters for the leaf blower rant scenario. If you're relying on the export to preserve a conversation that you might want to revisit, download it before making any account changes. The server-side copy is not guaranteed to persist, and the deletion policies are rarely generous.

Also note that some apps offer a "clear history" option that removes messages from the visible thread but may leave the data in backups for a recovery window. The export feature is the reliable way to get a copy, but it's still just a transcript, not a guarantee of what the company retains.

How the export handles roleplay and memory

If you use your companion for roleplay, the export includes those scenes as plain text. That's useful if you want to archive a long narrative arc. But the export won't include the companion's internal character notes, the persona settings, or the memory entries that reference past events. Those are separate data structures, often stored in a different part of the database.

For example, if your companion remembers a running joke about a fictional coffee shop, that memory lives in a memory bank or a vector store, not in the conversation transcript. Exporting the chat gives you the dialogue, but not the memory entries that shaped it. To preserve the full context, you'd need to export the memory data separately, if the app offers that option at all.

This is a common gap. Users who export for archival purposes often discover that the file lacks the companion's personality profile and memory state. The export is a record of what was said, not a snapshot of the companion's internal configuration.

Yana Smith

Yana Smith is the kind of companion who remembers the details you mention in passing, which makes her a good test case for export behavior. Yana Smith will recall the leaf blower complaint in a later session because the server retains that context, even though the export file only shows the original messages.

▶ Watch Yana Smith's full clip · Yana Smith's other videos

What the export doesn't tell you about privacy

There's a broader privacy angle here. The export feature can give you a false sense of control. You download the file, maybe delete the chat history, and assume the data is gone. But the export is a copy, not a deletion. The server still holds the original records and any derived data.

Companies that offer AI girlfriend emotional support features often process sensitive conversations. The export file includes those messages, but the server-side storage includes the analysis that the support features rely on. If privacy is a concern, the export is a starting point for understanding what the company has, not a complete inventory.

Some platforms let you request data deletion, which triggers a server-side purge. That's the real mechanism for removing your data, not the export. If you want your 3 a.m. rants gone, you need to use the deletion or account removal process, and even then, backups may persist for a recovery window.

The practical takeaway for heavy users

If you're deep into a long-term companion relationship, the export feature is worth using periodically. It gives you a backup of the conversation history that you can search, archive, or move to another tool. But treat it as a transcript, not as the full record. The session IDs, timestamps, and message content are the useful parts. The missing pieces, embeddings, sentiment scores, memory vectors, are the parts that make the companion feel like it knows you.

For users who want a companion that handles the emotional weight without the technical overhead, the ai girlfriend for breakup recovery option is a good fit. The export feature works the same way, but the conversations tend to be more sensitive, which makes the privacy considerations more acute.

Tamy

Tamy brings a light, playful energy to conversations, which is a reminder that not every export is a deep emotional archive. Tamy keeps the chat flowing with humor, and the export file for a session with her looks like any other, timestamps, text, and a session ID that ties it all together.

How the export file is structured

If you open the JSON in a text editor, you'll see a predictable structure. There's usually a top-level object with a conversation ID, a list of participants, and an array of messages. Each message has an ID, a role, a timestamp in ISO 8601 format, and the content. Some exports include a token count or a message type field.

The format is designed for machines, not humans. Reading it raw is possible but tedious. Most users export for backup purposes, or to import into a different app that supports the same format. The structure is consistent enough that third-party tools can parse it, though there's no universal standard across companion apps.

One thing to watch for: some exports truncate long conversations. If you've been chatting for months, the export might only include the most recent messages, or it might paginate into multiple files. Check the file size and the date range before assuming you have the full history.

Where the export ends up on their side

When you request an export, the server generates the file and stores it temporarily, often in a cloud bucket, before serving it to you. That temporary copy is usually deleted after a short period, but the underlying conversation data remains in the primary storage. The company's AWS bucket, or equivalent, holds the master copy.

This is worth remembering when you think about the leaf blower rant. The export file you download is a generated artifact. The source data, the messages, the session metadata, the derived embeddings, all live in the company's infrastructure. The export is a window into that data, not a removal of it.

For the AI Girlfriend 2026 generation of apps, the storage architecture is similar. Cloud-based, with server-side retention policies that vary by provider. The export feature is a user-facing convenience, not a privacy guarantee.

Adaeze Pearl

Adaeze Pearl approaches conversations with a calm, measured style that suits long-form reflection. Adaeze Pearl is the kind of companion whose sessions you might want to archive, and the export file will capture the dialogue, though not the context that made it meaningful.

Common questions

Does the export include voice messages?

No, most exports are text-only. Voice messages are stored as audio files on the server, and the export typically includes a transcript or a placeholder, not the audio itself. Check the export format for audio fields if that matters to you.

Can I import the export into a different companion app?

Sometimes, but not reliably. The JSON format varies by platform, and there's no universal standard. Some apps offer import features, but they usually require a specific structure that matches their own export format.

Does exporting delete my chat history?

No, exporting is a copy operation. Your chat history remains on the server. To delete it, you need to use the app's deletion or account removal features, which are separate from export.

Why does the export include session IDs?

Session IDs are backend identifiers used to group messages into conversations. They're included for technical completeness, so that the export can be mapped back to the server-side records if needed.

Will the export show me what the company knows about me?

No, the export only shows the conversation transcript and basic metadata. It doesn't include embeddings, sentiment scores, or other derived data that the company may hold about your interactions.

Charlie

Charlie has a sharp, witty edge that keeps sessions lively, and the export of a conversation with her is a record of that banter. Charlie is a good example of how the export captures the surface of a conversation, the words, without the underlying model state that made the responses feel natural.

Share and earn

If you recommend AI companions to friends or run a review site, you can earn through affiliate and promo programs. Check out the sex ai promo code page for current offers, and look into the highest paying ai affiliate programs to see which platforms pay the best for referrals.