Your words do not need to become an archive.

A conversation needs context, but it does not need to become a permanent record.

When you send a message, The Companion uses that message and, when it is still relevant, part of the recent conversation so it can understand the context and respond without losing the thread.

That does not mean every conversation needs to be kept. When continuity matters, The Companion carries only the context it needs, not a complete running copy of your life over time.

In the service today, temporary context used to keep a session connected can remain for up to 24 hours. After that period, it is cleared.

A small amount of continuity may also remain on the device you use. It is not a full transcript and it is not a record of your life. The boundary is simple: The Companion is not designed to know as much as possible about you.

Your history stays on the device you use.

If you use Journey, copies of conversations may be stored on your device so you can read them again or return to something you discussed before.

History is different from The Companion's memory. Being able to read a conversation again does not mean everything in it has become something The Companion remembers about you.

You can delete Journey entries from the app. Clearing app or site data on the device may also remove history stored there. Someone else who can open the same device may be able to see that history too, so use a device you trust for private conversations.

The Companion's memory is deliberately narrow.

The Companion can keep a small number of things you clearly teach it and that are useful later, such as how you prefer to be spoken to or what a term you use means.

A difficult experience, a personal problem, or something you share during one period of your life does not automatically become a permanent fact about you. Memory is not designed to grow into a record of your life.

Privacy here does not mean that The Companion processes nothing. It means The Companion tries not to take or keep more than it needs in order to accompany you.

Some conversations rely on technology outside The Companion.

Part of the processing needed to understand and answer a message may be carried out by technology providers used by The Companion.

What is sent is limited to what the request needs. Your current message has to be processed in order to answer it. Recent conversation, a limited summary, or narrow memory may also be included when they are relevant.

For those requests, The Companion uses settings that ask the provider not to keep the response as conversation history. Third-party providers still have their own terms and data-processing obligations. Our first boundary is therefore to limit what is sent in the first place.

There are things The Companion is not built to make from your conversations.

The Companion is not designed to know as much as possible about a person. It needs only enough context to accompany you well.

History that you can return to is not meant to become a comprehensive archive of your life.

Private conversations are not used to build advertising profiles or traded as a source of revenue.

The Companion is also not designed to turn a sequence of conversations into a permanent psychological profile of a person.

Some service information is still needed to keep access working.

Outside the conversation itself, The Companion may need information such as account and device data, an email address if you choose to use one, access or membership status, acceptance of the Terms and Privacy notice, usage counts, and transaction information.

If you arrive through a campaign link, a short campaign code may be stored so results can be counted in aggregate. The code does not contain the raw referrer, a full query string, location, or conversation content, and it is not used to build a personal profile.

Before a new anonymous access grant is created, Cloudflare Turnstile may run an automated check. The check token is validated once at Cloudflare's edge and then discarded. It is not passed to The Companion's backend.

To limit repeated orientation grants through incognito browsing, cleared browser data, or network changes, Cloudflare may create a one-way marker from a small set of technical signals. The Companion's backend receives only a signed digest, orientation grant status, and network bucket counts, not the raw IP address, a raw fingerprint, cookies, or the Turnstile token. If a temporary device signal is available, only a one-way digest is stored.

Those records are used to provide access, account for usage, protect the service, handle payments, and prevent abuse. They are not used to build conversation, Journey, or advertising profiles.

Email sign-in remains optional. If you choose it, your email address is used to verify and recover your identity and access rights when you change devices. Journey is not moved or synchronized through the email account.

Service records are not copies of your conversations.

The Companion needs to record things such as whether a request succeeded, response time, usage, access limits, or a service failure.

Those operational records are not designed to store your messages and responses as a copy of the conversation.

No digital service is completely free of risk. Privacy therefore depends not only on technical safeguards, but also on limiting what is collected, kept, and made accessible in the first place.

Some information is better kept out of the conversation.

Do not enter passwords, PINs, one-time codes, full card numbers, or other secret access keys into The Companion. If something is not needed for The Companion to help, it is better left out.

Sensitive payment information is handled through the appropriate payment flow when that feature is used, not requested inside a conversation with The Companion.