The short version

<aside> 💡

SlidesWeft does not collect anything. There is no account, no server, no analytics and no crash reporting. Your decks stay in folders on your machine, and nothing about your use of the application is sent to the developer or to anyone else.

The application does use a network in a small number of situations, which are listed in full below. You start every one of them yourself, and all but one stays inside your own machine. The exception is sharing a handout with people in the room, which uses your local network.

</aside>

What the developer collects

Nothing.

The application has no telemetry, usage analytics, crash or error reporting, advertising identifier, update check or account system. It contains no code for any of these, and none of the libraries it uses provides them.

This is a property of the build rather than a promise about intent. The repository contains a check that fails if the application's network code ever reaches beyond your own machine.

The store you installed from is a separate matter. See The application stores.

What the application stores on your device

Everything below stays on your device. None of it is transmitted anywhere.

What Where
Your decks: text, stylesheet, images, and anything else you add Wherever you save them. A deck you have not saved yet is kept in the application's own storage until the first save asks where it belongs.
Settings: appearance, language, whether the assistant is on, which model it uses, connected-app and tool configuration The application's own storage (see below)
Recovery copies: the working copy that lets an interrupted session be recovered The application's own storage
Deck history: the snapshots taken when you save, which let you put an earlier version back Beside the deck, in a cache folder the application marks as not to be shared
Templates and themes you import The application's own storage
Assistant conversations, if you use the assistant Inside the deck they belong to
The local search index, if you use it The application's own storage

The application's own storage is the standard per-application folder that your platform provides:

You can read or delete any of these files with your file manager.

What uninstalling removes.

Decks you have saved to a folder of your choice are never touched by uninstalling. The application's own storage is a different story, and it depends on how you installed: