Twig

Privacy

What stays on the phone, what leaves, and what Twig never builds.

Source of truth

Agents, conversations, memory files, skills, macros, and blobs live under the app’s private directory on the phone. The SQLite database is an index. You can throw it away and rebuild it from the files.

What leaves the device

  • The text (and optional attachments) of a turn, sent to the model provider whose key you configured.
  • Embedding requests, when deep recall is enabled and an embedding-capable key is present.
  • Nothing else. There is no Twig cloud, no analytics pipeline, and no account.

USB companion

When a laptop is plugged in, the phone dials a WebSocket through adb reverse. The laptop can run heavy model calls and scripts the phone asks for. Transcripts and files remain on the phone. The laptop is rented muscle, not a second brain.

Soft sharing only

Agents never get permanent shared homes. Folder access is a grant with an expiry. When it ends, access ends.

Backups

Export copies files through the Storage Access Framework into a folder you choose. The live database is not hosted on SAF — only import/export use it.