TransferChain

@tugce_icozu Thank you 🙏

@mertbaser @prakhar_tandon_1 thank you!

Hi @janis_wilczura We've seen multiple customers that use TransferChain for dataroom purposes (including ourselves 🙂). We lacked the preview feature, but that will be going live next week as well! If you have any specific recommendations for dataroom purposes we'd love to hear them as well! Btw our roadmap is public (https://transferchain.canny.io) :)

@shivam_singh63 Hello Shivam, thank you !

Hi @naveed_rehman Attaching docs to an email means you'll be utilizing the providers' servers (providers have access to your files), you might face man-in-the-middle attacks, or the recipient might not protect their email account properly so any phishing attack might bring out bigger problems. There could also be multiple other reasons why you might prefer something else besides emailing attachments: - The file you're sending out might be confidential/classified - If it's a large-sized file - If you're looking for better control (download limits, two-factor-auth, expiration) TransferChain is the right way to go in all the cases mentioned above. But we also launched our Microsoft Outlook add-in, meaning you can even send transfer files within your Outlook interface along with your email (check it out > https://appsource.microsoft.com/...)

@mertbaser so if i zip the file with very long password crackable in 200 yrs via brute force, would that not be secure? also any case study where gmail or hotmail got middle man issues?

@mertbaser @naveed_rehman This is a good point. I feel like most people, if not everyone, trusts gmail.

@naveed_rehman @brandon_yan Happy New Year, wishing you guys a prosperous new year! Here is an actual MitM attack that happened before [https://www.securityweek.com/mit...]. Zipping your files with very long passwords would be a good way to start taking additional security measures, on the other hand, it might be a very time-consuming manual process for each of the files you upload. Instead, you may use TransferChain for that scenario because our protocol encrypts (on your client-side), splits each file into pieces, and distributes each chunk to different data centers - and unlike the manual zipping process you've mentioned our protocol handles everything automatically within just seconds. I'd definitely recommend you guys try it out if you haven't already :) Your feedback is very valuable to us.

@je_suis_yaroslav Thanks so much!