Privacy Question for Logseq Sync

JimWrites · June 11, 2023, 6:38pm

I have a question that I haven’t found a clear answer for so-far. If a government entity (ie the US govt.) requested (demanded) access to a vault the is using Logseq Sync, would Logseq provide that access, or does the encryption make those files unreadable?

I know that a lot of us are concerned about privacy, but do we give up that privacy when we use the sync service?

Bader · June 11, 2023, 7:08pm

Logseq does not store your password. Logseq employs the Age encryption format, utilizing the password you set to ensure your data is secure. Encryption specifications:

github.com

C2SP/C2SP/blob/main/age.md

# age

[c2sp.org/age](https://c2sp.org/age),
[age-encryption.org/v1](https://age-encryption.org/v1)

age is a modern file encryption format with multiple pluggable recipients, and
seekable streaming encryption.

## Conventions used in this document

ABNF syntax follows [RFC 5234][] and [RFC 7405][] and references the core rules
in RFC 5234, Appendix B.1.

The base64 encoding used throughout is the standard Base 64 encoding specified
in [RFC 4648][], Section 4, without `=` padding characters (sometimes referred
to as "raw" or "unpadded" base64). Encoders MUST generate canonical base64
according to RFC 4648, Section 3.5, and decoders MUST reject non-canonical
encodings and encodings ending with `=` padding characters.

Keys derived with HKDF-SHA-256 are produced by applying HKDF-Extract with the

This file has been truncated. show original