What goes into developing a private & secure service? Today we sit down with John Ozbay from Cryptee to discuss the inner-workings of their open source tools.

John Ozbay Website: https://johnozbay.com/ Cryptee Website: https://crypt.ee/

🔐 Our Website: https://techlore.tech 🏫 Techlore Coaching - to get direct support: https://techlore.tech/coaching 🕵 Go Incognito Course - to learn about privacy: https://techlore.tech/goincognito

Connect with our privacy community: ✉️ Blog: https://dispatch.techlore.tech 💻 Forum: https://discuss.techlore.tech Ⓜ️ Mastodon: https://social.lol/@techlore

We provide all content & resources for free, please consider supporting our work to help us expand our content: 🧡 Patreon: https://www.patreon.com/techlore 💖 All Other Support Methods: https://techlore.tech/support

Timestamps: 00:00:00 Introduction 00:02:01 Why is Cryptee a web app, rather than offering traditional clients? 00:07:32 What features are offered to give users deniability? 00:09:09 What are the several risks of being reliant on an app store? 00:12:00 How & why is Cryptee built without reliance on any 3rd parties? 00:16:41 Where might users have to sacrifice convenience for security? 00:19:29 What do people compromise with most services? 00:34:07 Is Cryptee for everyone? Who is the service targeted for? 00:46:11 How does Cryptee perform across different browsers? 00:55:54 Why is Cryptee's backend not open source? 01:02:32 Final questions, comments, and summaries #privacy #security #cryptee