Can a couples app read what you write? Usually, yes

The honest starting point is that most apps of any kind can read what you put into them. Not because anyone is sitting there reading it, but because the data arrives on a server in a form the operator can open.

That is the default architecture for almost all software, and it is worth understanding rather than being alarmed by, because it determines what is possible later.

What "can read" actually means

It does not mean an employee is browsing your entries. Reputable companies restrict internal access and log it.

It means the capability exists. And capability is what matters, because capability is what can be:

compelled by a court, accessed by an attacker who gets into the system, sold or transferred when a company changes hands, quietly repurposed when a privacy policy is updated, and used to train or improve a model.

None of those require anyone to have bad intentions today. They require only that the data is readable.

The question is not whether a company would read your data. It is whether they could, if circumstances changed.

Encryption in transit is not the same thing

This is the most common confusion and companies are not always eager to clear it up.

Almost everything uses encryption in transit. That protects data on its way between your phone and the server, and it means someone on the same café network cannot see it. It is table stakes and it says nothing about what happens at the other end.

Encryption at rest means the data is stored encrypted on the server. Better, and usually the operator holds the key, which means they can decrypt it whenever they need to.

End to end encryption means the key exists only on the devices. The server holds material it cannot open. That is the only one of the three where the operator genuinely cannot read the content.

How to check what yours does

Look for the specific phrase "end to end" rather than "encrypted", which is used loosely.

Look for a statement about where keys are held. If the answer is that the company holds or manages the keys, the company can read the content.

Look in the privacy policy for what happens on an account transfer or acquisition. "Your data may be transferred as part of a business transaction" is standard and it tells you the data is readable and transferable.

Look for whether content is used to improve services. That phrase generally implies access to content.

And check the data export. If you can request a copy of everything and it comes back readable, the company could read it too.

The trade-off is real

End to end encryption is not free. It makes several ordinary features difficult or impossible.

Server-side search across your history. Password recovery that restores your content. Web access without the key. Content moderation. Server-side backup that can be restored to a new device without any user-held secret.

Companies that choose readable storage are usually choosing those features, and for many products that is a defensible trade. For a product that holds what two people say to each other when nobody else is listening, it is a worse trade, which is the case for building it the other way.

What Duoheart does

Questions, answers, messages and calls are encrypted on the devices, with a key generated there that is never sent to our servers. We hold material we cannot open.

The consequences are visible in the product and we would rather state them than hide them: content cannot be recovered by us if both devices and the key are lost, and there is no server-side search of your history.

Those are the costs of the choice. We think they are the right costs for this particular thing.

What to do with any of this

You do not have to become an expert. Two questions cover most of it: who holds the key, and what does the policy say happens if the company is sold.

If an app will not answer the first one clearly, that is itself an answer.