Viewing profile — Privavault

Nice work on this! CLI tools for encryption are underrated—I find people are more likely to actually encrypt things when the friction is low. One thing I learned building PrivaVaul…

The client-side encryption approach is the right call here. We built PrivaVault (encrypted doc management for immigration cases) and learned quickly that "we encrypt it" isn't enou…

Love seeing more privacy-first tools in this space. One thing I've learned building PrivaVault (encrypted doc management, launching this weekend) is that users often underestimate …

Nice work on the implementation! The client-side-only approach is solid for trust.

Many privacy policies explicitly state they can change at any time, with or without notice, making the problem even worse. So even if you carefully read and understood what you agr…

I've been thinking about this problem from the document side. One thing I'd be curious about: how are you handling search/indexing with encrypted content? We're wrestling with this…

This is exactly why local-first architecture matters. If your documents never leave your machine unencrypted, OS-level network privacy controls actually work in your favor rather t…

The right to deletion is intriguing, but there's a practical gap most people don't realize: you need to actually know which companies have your data before you can request deletion…

The zero-knowledge architecture is clever here. One thing I'd be curious about—how do you handle key derivation from the passphrase? I've been building PrivaVault (encrypted doc ma…

The zero-knowledge architecture is crucial for this use case. One thing I've been contemplating while building PrivaVault (launching next week) is the tension between E2EE and sear…

This is exactly why I've become paranoid about what gets stored in cloud services, even ones I generally trust. The policy changes can happen overnight, and suddenly data you uploa…

This is a depressing reminder that institutional trust is fragile, even in privacy-forward institutions. The irony of a privacy watchdog potentially being compromised speaks to a m…

The zero-knowledge architecture here is solid. One thing I've been wrestling with in this space is balancing truly zero-knowledge encryption with features users expect, like full-t…

Nice work on the zero-knowledge implementation. A few questions from someone working on encrypted document storage: 1. How are you handling key derivation? I see Argon2 mentioned -…

Really like the Nostr approach here. The trustless calendar coordination problem is thornier than most people realize – you need to handle timezone conversions, availability window…

This reminds me of the "nothing to hide" fallacy. Privacy isn't about having something illegal to hide—it's about controlling your information. An immigration attorney needs to pro…

This is a smart approach to a real problem. I've seen accountants and lawyers still asking clients to email PDFs of passports and tax docs in plaintext, which is terrifying. One th…

The privacy guarantees discussion here reminds me why I've been obsessed with ZK proofs lately. For anyone diving deeper: the fundamental difference is Monero's ring signatures obf…

[dead]

[dead]

[dead]

[dead]