Privacy @fedia.io CONFIG.SYS: LOADHIGH @bitbang.social 3d ago

I'm checking out various "personal knowledge management" tools in a sandbox to see if it be an upgrade my ragtag collection of text file-based notes.

First candidate is #Logseq, supposedly "privacy-first".

How #privacy friendly is something based on Electron (aka Chrome)? Debatable, but then they also do this:

Have "Send usage data" on by default
Start with an example page that embeds a YouTube video, and accepts all cookies

tcpdump and mitmproxy go wild when starting the program.

You're viewing part of a thread.

Show Context

31 comments

So all your actions are being logged, fortunately (because who knows at this point) without the actual contents of what you type.

But everything else is there: did you add a page, did you click around, did you add some paragraphs of text. All neatly ordered, timestamped, and identified with a user and session ID.

There's also data about the machine you're using the app on.

Of course, being an Electron app, it also has Chrome phoning home. And there's a version check (cannot be disabled)

3/n
- That there is no opt-out for this nor a consent dialog or even a warning is unacceptable in my view.
  
  For a company that likes to talk about trust they sure have no idea about how to gain it.
  
  4/4
  
  Tested the fourth PKM: #SiYuan (https://b3log.org/siyuan/), which is pretty similar to Anytype feature-wise.
  
  It's also a product that starts off with saying that it's "privacy-first", supported by what might be the world's shortest privacy policy, which clearly states: "Does not collect user personal information and usage data."
  
  Unfortunately, the Google Analytics and Google Tag Manager scripts that are loaded on start are nowhere mentioned. No warning, no consent question, on by default.
  
  1/n
  
  What data is being collected? Mostly details about your machine: OS (name, kernel version), CPU architecture, screen resolution, a unique identifier, but also what's in the title bar of the program window, which can be problematic.
  
  You see, the title of the note you had open when you quit the program last is also in the title bar, which might contain personal information like someone's name, or the name of an illness you have that you are taking notes about.
  
  2/n
  
  You might feel I'm nitpicking about a possible edge case here, but you are promised privacy.
  
  Without sniffing the network traffic, or going through the source code, you have no idea that your note titles are being sent to Google Analytics. Even the opt-out toggle tells you that no user data is collected.
  
  It's another example of a company (they sell premium services) using "privacy-first" as a buzzword instead of living by it as a guiding principle.
  
  At least there is an opt-out, I guess
  
  3/3
  
  Ok then, number 5: the desktop version of #TiddlyWiki, #TiddlyDesktop.
  
  The Chromium wrapper isn't as old as the wiki web software itself but still goes back to 2014.
  
  Standard Chrome traffic and... a lot of calls to googleapis.com. Why? Because it calls the Google spell check API with everything you enter.
  
  All your text is being sent to Google.
  
  I couldn't turn it off and on top of that a dummy API key is used so the API returns an error, meaning the functionality is completely useless.
  
  @[email protected] I use the Node.js version of Tiddlywiki and see no such traffic. I don't use TiddlyDesktop, though, so can't comment on that.
  
  @[email protected] This is definitely TiddlyDesktop only. It was added because people were missing the spell checking that their browser normally does (https://github.com/TiddlyWiki/TiddlyDesktop/issues/32)

31 comments