Souspli

Souspli / Docs / Use

What leaks when

Souspli's rule is that nothing touches the network unless you asked, and you are told the cost before it happens. This page is the whole list.

Reading a letter: nothing

Opening, reading and interacting with a letter reveals nothing to anyone — not to its author, not to a server, not to an advertiser.

This is enforced, not promised. The container a letter runs in has no network at four independent layers, no cookies or storage that survive, no access to your files, and is told almost nothing about you: your language and whether you prefer a dark theme. No time zone, no screen size, no identifier. An author cannot learn that you opened their letter, when, how often, or what you clicked.

By action

You do this Who learns what
Open a .thing file, drag one in, paste a bundle Nobody learns anything.
Write, edit or publish a letter Nobody. Publishing signs; it does not send.
Save as file / Copy bundle Nobody, beyond the channel you then use.
Paste bundle:<hash> Nobody. It is looked up in your own store.
Paste an https:// link That server learns your IP address and the time. No cookies or credentials are sent. The box shows ⚠ tells <host> your IP before you press Ingest.
Paste a magnet: link The BitTorrent DHT and every peer learn your IP and that you want this letter. Shown as ⚠ contacts the BitTorrent network first.
Seed over BitTorrent The DHT and peers learn your IP and that you hold this letter — even a sealed one, whose content stays secret.
Add a relay That relay learns your IP and what you subscribe to — the one thing none of the other channels leak.
Say yes to Find people… Exactly the row above, for relay.souspli.org, plus the welcome forum's roster is added to your library from inside the app — no fetch. Until you say yes: nothing. The offer itself contacts nobody.
Join the community forum (the Forum page) The row above, plus the name you chose, published as a signed letter: the relay and everyone reading the forum learn your key's chosen name. Until you press Join: nothing. Not now contacts nobody.
Post, comment, ▲ or unvote in the forum you joined Goes out at once, with no further prompt — the Join was the consent. The relay learns your IP; the relay and everyone reading learn that your key wrote or voted on this, permanently. Everywhere else, posting to relays stays a separate act each time.
Post to relays Each relay learns your IP; the relay and all its readers learn that your key published this letter.
Send privately to relays (or the box in the confirm when you seal a letter) Each relay learns your IP, the time, and that an encrypted letter of about this size was posted. It doesn't learn who wrote it or who it's for. The post uses a key made for it alone. Everyone reading the relay receives it; only the recipients can open it.
Press Fetch on an offer Whatever the offer's link type reveals (above). Until you press it, nothing: no tracker contacted, no byte pulled.
Give a key a petname Nobody. It never leaves your machine.
Publish a vouch Everyone who receives it learns you know that key. It discloses your social graph, permanently.
Vote, comment, attest, co-sign Nothing until you share the resulting letter — then its readers learn your key's opinion.
Say yes to Check for updates?, or choose Help → Check for updates… GitHub learns your IP address and which version of Souspli you run, once a day (or once, for the menu item). Until you answer: nothing.
Press Download on an update GitHub learns your IP and that you are fetching that version. Nothing is downloaded until you press it; restarting into it is a separate click.

Defaults

Things a signature makes permanent

What Souspli itself collects

Nothing. There is no telemetry, no crash reporting, no analytics, and no server operated by the project for the app to talk to. The one contact the app itself can make is the update check above, and only if you agree to it: it goes to GitHub, which hosts the releases, and it carries no identifier beyond what any web request does.