The data is sent in a secured way to Google or Microsoft Azure services based on rules set in Document Solution executed via configured GraphQL query. Data is processed by the merge engine (Google or Azure) and applied to the templates (that are stored in the user’s Salesforce Org or Google Drive or OneDrive optionally). This data only lives once when triggered by the user in an isolated transaction and ends up in the generated document stored in the location of choice.
Maven Documents uses HTTPS for secure communication between Salesforce and Google or Microsoft Azure services. This ensures that the data transmitted is encrypted and secure.
Maven Documents does not store any user business data on Azure or Google. Instead, data is stored in the customer's Salesforce orgs, ensuring that only the customer has access to their data based on the Salesforce security model and Org setup. The merge of the document template and Salesforce data is done in an isolated transaction triggered by the user. There are no logs produced from user data. Storage of user templates and output documents is inside secured environments like the user’s Salesforce Org and/or optionally user's Google Drive or Microsoft OneDrive.
The application communicates with various remote services, including Google APIs and Maven Mule's Azure APIs. This communication is secure and managed within the Salesforce environment. Authentication is done via Google or Azure applications with scopes provided to authenticated users while connecting APIs to Salesforce.
To manage Salesforce file storage limits, Maven Documents allows users to send files to the cloud. It also supports automating the deletion of Salesforce files, which can be critical for managing sensitive data and adhering to storage policies.
Maven Documents adheres to several security practices and compliance standards, including:
MFA is enabled for code repositories and credentials, enhancing the security of the development and deployment processes together with cloud infrastructure on Google or Azure.
The application complies with GDPR and other privacy or data protection requirements, such as the California Consumer Privacy Act (CCPA). It also has an external-facing privacy notice detailing its data collection, usage, sharing, and storage practices.
Maven Documents has established processes for information security risk management and a documented security incident response process, which are critical for promptly addressing any security threats or breaches.
These points cover a broad spectrum of security aspects, from data storage and transmission security to compliance with privacy regulations and security best practices. If you have specific questions or need more detailed information on any of these points, feel free to ask!
Maven Documents uses the “Always Encrypted” feature to keep your sensitive data safe. We encrypt the provided sensitive data in the database, and only the application has access to the decryption key managed by Key Vault. Data is consumed by Maven Documents only in isolated transactions initiated by authenticated application users.