Office Privacy Shield (alpha)

The Office Shield give you the option of encrypting certain chat content in RingCentral or UnifyOffice. Shielded content will not be exposed to the browser's DOM tree and RingCentral or UnifyOffice admins will not be able to export your content in clear readable text (only you can read the text via this extension). Only you, or members of the same conversation, will be able to expose the readable text form of the chat. Office Shield also protects your shielded content from potential Client Cross Site Scripting (Client XSS) attacks. The Office Shield is designed so that you can protect personal data within conversations by encrypting the strings that get stored in the RingCentral or Unify Office database. RingCentral own a key to protect all the data stored in their database, which can be decrypted by RingCentral if needed except for Office Shielded content. Tenant admins (companies who use the RingCentral cloud service) will be able to have their own key in the coming future. RingCentral will not be able to decrypt the tenant's data stored in the RIngCentral database. Tenant admins can decrypt their own data but not Office Shielded content. The Office Shield iplaces is your very own personal key independent from RingCentral, UnifyOffice, or your tenant administrator. Google Deceptive Installation Policy Declaration (effective 1st July 2019): This extension connects to your current RingCentral or UnifyOffice session in the active browser tab. It does not collect or read any other information from RingCentral or UnifyOffice or any other services. All encryption is carried out locally and no data is transmitted away from your local browser. Description (RingCentral or UnifyOffice account needed for this Extension to work): Simply select your text, encrypt and save (send conversation). The UnifyOffice Content Shield (Office Shield) is a "Chrome browser" privacy application that uses the AES 256 CBC encryption standard (mobile devices are not currently supported). All processing is carried out locally and no data leaves your browser before, during, or after encryption PERIOD. This app contains no adds and does not track you. The app is designed to respect the GDPR legislation wherever you are. No ads or 3rd Party services involved. Privacy can be fun if done right. I hope you enjoy Update Notes: 0.0.1 - Convert the Circuit Vault extension to be used with RingCentral and UnifyOffice 0.0.2 - Hyperlinks inside the generated shield did not open. Updated 'Settings' page. Fixed bottom line dropping off shield after opening. 0.0.3 - Classes used to identify buttons randomly change from time to time. This update finds the classes even after their class names have been changed. 0.0.4 - Migrated manifest from v2 to v3 (sync storage needs to be tested after publishing) - Fixed bug where right click on blue text (markup) fails to lift the shield. - Fixed bug where clear text directly around the shielded content was opened incorrectly. - Added new functionality to prompt if shield string does not belong to the owner is pasted into the edit field and decrypted. The field is also not cleared. - Changed the colour of the security watermark that is used on all shields. 0.0.5 - Fixed buttons being added every time the conversation changed (too many buttons being added) - The new manifest sync storage is working in the settings but the values are not being read properly (on initial install). Console.logs have been added to the encrypter to see if the values are coming though (can only debug from published app as the development version is treated as local sync not a Google sync). 0.0.6 - Fixed bug where people could not unshield messages. Non-owner was incorrectly identified when unshielding message outside of the edit box (unshield in read only mode) 0.0.7 - Updated CryptoJS to version 4.1.1. References of Math.random() now use random methods of the native crypto module - Upgraded all JQuery to version 3.6.0 0.0.8 - Performance and stability improvements - removed the 'tabs' permission from the manifest (no longer needed) 0.0.9 - renamed Privacy Shield - using UnifyOffice causes the CPU to run at 100% causing a delay when opening content. Increased timeout to allow for the decrypt to be built Status: Migrating from Circuit Vault to Office Shield (Unify Office). Currently, you can only create and open Privacy Shields without a private key. The function to allow for private keys will be developed once full stability has been achieved. Tidy Shields has not yet been implemented. This will be finalised once the point above has been completed. Issues: Watermarks and legal prompts are not working fully after migrating from MV2 to MV3. This is due to the syncing of the setting from the user's Google account. Investigating issue. Circuit has been discontinued by Unify and will no longer be supported: https://chrome.google.com/webstore/detail/circuit-conversation-vaul/lgoocbkpfeafaihbmdiomonmpcanepjg?hl=en-GB&authuser=0