What happens if the company disappears?

You open a diary you have used for two years and find a sign-in screen where the pages used to be. The company has closed. Its servers no longer answer, and your own history has become an error message.

That possibility changes how a personal AI should be built. A companion is not only holding disposable prompts. Over time it can hold conversations, people, commitments, diary entries, job-search notes, and an account of how your days actually went. “Trust us to stay in business” is not an adequate storage format for any of that.

The app does not call home to exist

DT Life keeps its working data in a local SQLite database on your computer. The model runs on your CPU or GPU. Licence verification checks a signed key on the same machine; it does not ask an account server whether you are still allowed in. There is no product login whose disappearance can lock the door.

So if development stopped tomorrow, an installed copy would not immediately go dark because a remote service had been switched off. Its data would still be on the disk where it was the day before. The licence check would still be a local signature check. Features that run on-device would not suddenly need a new server.

This is an architectural property, not a promise that a future company will do the right thing. A promise can be broken. Software that never needed the server has no server dependency to break.

Independence is not the same as a perpetual feature licence

There is an important boundary here. DT Life is sold under an annual licence, with 12 months of updates, and nothing auto-renews. There is no card on file and no quiet charge in month thirteen. You decide again.

If the licence lapses, the app becomes read-only. Your diary, the twin’s memories, and your history remain readable and exportable permanently, at no additional cost. Nothing you created is withheld. But it would be misleading to turn that into “every feature keeps working forever,” especially in the very article meant to answer the uncomfortable question.

If the company disappeared before renewal, there might be nobody from whom to buy another annual term. The installed app would remain independent of a licence server, but the expiry already signed into the key would still exist. After it, read-only means read-only.

What you own, and what you should keep

You own the continuity of your information in a practical sense: it sits on your machine, can be read and exported without asking support, and can be carried in a passphrase-encrypted recovery bundle. A bundle includes the database and the data key, so a new Windows account can decrypt it after a staged restore.

That does not make the application immortal. Keep the installer and your licence key if long-term access matters to you. Make recovery bundles and store them away from the computer they protect. Export the records you would need in another tool. Local-first removes a company server from the critical path; it does not remove Windows changes, hardware failure, lost passphrases, or the eventual need to migrate software.

It also does not guarantee future security fixes or compatibility updates if development ends. A copy that runs today may meet an operating-system change years from now. No honest desktop vendor can promise otherwise.

The useful test is therefore narrower than “Will this company exist forever?” No company can answer that. Ask instead: if it does not, where are my records, what can I still do with them, and which parts stop?

For DT Life, the records remain on your disk and stay readable and exportable. The installed software does not need a company server to start. Full feature access, however, follows the annual licence and becomes read-only if that licence lapses. That is the whole answer, including the part a sales page might prefer to leave in small print.

Read the licence in plain terms →