XooG | Decentrailized security platform

1. What is XooG?

2. What are the USPs of XooG?

3. What is the encryption technology used for XooG?

4. Who all will have access to my key?

5. What information related to me will be stored in XooG?

6. In my mail / attachment, what level of access XooG will have?

7. Can I use XooG for my personal mail id ?

8. What if I use my mail service [ XooG ] from mobile? Any difference or process to be followed ?

9. What if I delete the email ?

10. What are the specific hardware and software requirements for using XooG?

11. If any legal requirement, XooG will be able to share our information to the Governments / Courts without our concurrence or approval ?

12. What if someone accessed my mail? Should I reset XooG after resetting my email password?

13. Can I use XooG alongside my email provider’s built-in encryption?

14. I would like to buy XooG for my personal mail id. Is it possible to subscribe?

15. I have multiple mail ids. Is there a plan where I can buy one XooG subscription for all ?

16. During XooGing, the “Compute Node” which does the encryption is based out of which country ? Do I have a say on that?

17. What is the involvement of validators here, if any?

18. Is it possible to use any other chain for XooG?

19. The authenticity of the block chain platform (MOI) and IOME protocol? Are there third party certifications like HIPAA, GDPR or SOC2 compliant?

20. Competitive comparison / battle cards to Microsoft encryption etc.

21. What will it take for someone to replicate this over another blockchain network? What will be our positioning then?

22. Are there any vendors who do mail encryption at rest?

23. Are there other vendors offering selective text encryption?

24. It was mentioned that the private key gets downloaded automatically when the XooG login is done. Do we have any technical write up /certification / patent / IPR around this?

25. Have we conducted a bug bounty program for the platform to prove its security?

26. What is the compliance and regulatory burden that we should take on?

27. Does the performance get impacted depending on the size of the email?

28. Does IOMe interface with XooG, have the “Data Subject Request”(DSR) in accordance with GDPR where the customer can choose the type of Request(Either Right to Access or Right to Erasure)?

29. Why was ZES chosen over other algorithms?

30. How is the encryption key managed? Is it shared between sender and receiver, and if so, how is it transmitted securely?

31. Does the encryption process work offline, or is an internet connection required?

32. Are there character limitations or restrictions for the text that can be encrypted?

33. Can the “Subject” of the email be encrypted?

34. What measures are in place to prevent brute force attacks or unauthorized decryption?

35. Can the encrypted text be shared across different platforms (e.g., forwarding the email), and how is security maintained in such cases?

36. How are updates to the extension handled, and how is backward compatibility ensured for older versions?

37. Is there any visual indication in the email body to alert the recipient that part of the email is encrypted?

38. Is the extension free, freemium, or subscription-based? If paid, what is the pricing model?

39. Are there plans to integrate advanced features, such as two-factor authentication for decryption or blockchain-based encryption keys?

40. How are users informed about critical updates, security patches, or feature changes?

41. Outlook by itself is an encrypted email service. Why is there a need for having an additional layer of encryption in the form of Xoog?

42. Why has Xoog been built on MOI blockchain? What does it do better than traditional L1s such as Bitcoin, Ethereum or Solana?

43. What are Xoog’s limitations?

Frequently Asked Questions