Riva is built using the Microsoft .NET Framework and Microsoft technology stack. Riva implements security based on Microsoft security best practices.
Communication from Riva to and from your CRM and email systems is made via SSL encryption. Riva communicates with your email server/system using SSL-encrypted access and communicates with your CRM using encrypted web services.
Riva uses a data pass-through model and architecture. Unlike BlackBerry Enterprise Server, Good Technologies Sync Server or other data sync solutions, Riva does not retain a local copy of your Exchange message and data store. Nor does Riva retain a copy of your CRM data. Riva does not do a store and forward data transfer of email content. Riva does not store email content at any time.
Riva stores certain minimum types of information in memory for performance improvement. In order to keep communication with Exchange and your CRM as efficiently as possible, Riva caches a dynamic mapping of company email domains and related contact email addresses in the Riva server RAM so it doesn’t have to look up email addresses it has already stored in memory. This information is not written to local storage.
Riva keeps sync log files in order to carry out trouble shooting activities. These log files are retained for 14 days. In the logs, Riva retains the name of the users being synchronised, the subject of emails that are being archived or SmartConverted and the name of the folder in which the SmartConvert or email archive process is carried out. The content of the email is never read or stored by Riva and is therefore not kept in cache or in the log files. Companies interested in reviewing the specific information that is being cached for their accounts can receive a link to the meta directory information to see exactly what is being retained.
Riva support personnel have no access to the Riva server file system unless approved by the customer. Riva support personnel will only work on customer Riva servers under direct supervision of the customer.
Riva communicates with email systems using a user impersonation method supported by the vendor supplied API. By implementing user impersonation, Riva synchronises each individual user’s account as if the individual user were accessing the system. This ensures that CRM visibility and security and mailbox access are respected by Riva. Using impersonation, if a user modifies a contact in their email client address book, the “modified by:” field is preserved in your CRM as the user who made the modification in Outlook.