Standard Security Response Campaign Monitor

As a small company offering a low-cost, self-service solution, we strive to make our products affordable and user-friendly. While we don’t have the margins to create custom technical documentation or conduct individual reviews for each customer, we have provided detailed information below to address your security concerns. 

We'd also point out that our product is a native Salesforce solution that uses Campaign Monitor and its secure APIs. We don't have any middleware. In short, our product is installed in your Salesforce Org and uses Campaign Monitor and Salesforce resources. Unlike middleware products like Zappier, we don’t store your security token and, therefore, don’t have access to your Salesforce instance.

So based on this, if you have not already, we recommend sending your questions to Salesforce or Campaign Monitor as their answers apply to our product. If you have done that already and the points below don't answer your questions.  Our in-house technical team can only be reached via support@beaufort12.com should you have any specific follow-up questions.

Data Storage and Handling

• No Independent Data Storage: The Campaign Monitor for Salesforce integration does not store any customer data independently. All your customer data remains within your Salesforce and Campaign Monitor accounts.
• Data Flow: The integration acts solely as a conduit, facilitating the direct data transfer between Salesforce and Campaign Monitor according to your instructions. We do not store, manage, or manipulate personal data.

API Calls and Metadata Access

• Outbound Connections Only: The integration does not independently initiate inbound API calls to your Salesforce environment. All connections are outbound from Salesforce to Campaign Monitor, initiated by your users and using Salesforce encryption.
• API Call Usage: Since we don’t make independent calls into Salesforce, our integration does not consume your API call limits (typically 15,000 per 24 hours).
• Beaufort 12 API - You will be asked to grant access to .beaufort12 during installation. This is used to host the AI chatbot you see at the bottom right-hand corner of your screen in certain spots. No customer data is sent via Beaufort 12. But anything you put into the chatbot will pass through our server. All customer data is point to point - I.e., from Salesforce to Campaign Monitor and does NOT pass through our servers (unlike most other integrations).

Metadata Retrieval

• Purpose: The only calls made back into Salesforce are to obtain metadata necessary for supporting features like list view imports and page layout configurations.
• User-Initiated Actions: Your Salesforce users initiate these metadata requests in real-time and do not store or cache them.
• Limited Metadata Scope: The metadata extracted is limited to what is necessary for the integration’s functionality and does not include user information.
• Opt-Out Capability: You can choose not to grant access to metadata if you do not use certain features, such as the data wizard with list views or bulk imports.

Data Encryption and Security Measures

• Latest Encryption: All data transmitted between Salesforce and Campaign Monitor through the integration is secured using the latest encryption, by Salesforce. This ensures that data is protected during transfer between systems.
• Secure Authentication: The integration uses secure authentication methods to connect to both Salesforce and Campaign Monitor, ensuring that only authorized users can initiate data transfers.
• Data Isolation: All data related to our application within your Salesforce environment is stored in objects that begin with the namespace "wbsendit". This allows for easy identification and management of data specific to the integration.

Operational Transparency

• No Hidden Operations: We do not perform any operations not directly initiated by your users. No background processes are accessing your data without your knowledge.
• User Control: You have full control over what data is shared between Salesforce and Campaign Monitor. No personally identifiable information (PII) is sent to Campaign Monitor without your explicit permission or action.
• Data Visibility: Any transferred PII is accessible within Campaign Monitor under subscriber custom fields. There are no hidden fields containing PII.

Security Best Practices

• Regular Updates: We continuously update the integration to patch security vulnerabilities and comply with the latest security standards.
• Access Controls: The integration respects the access controls and permissions set within your Salesforce environment, ensuring only authorized users can perform certain actions.
• Audit Trails: The integration's actions can be tracked within Salesforce and Campaign Monitor, providing an audit trail for security reviews.

Technical Documentation and Support

• Campaign Monitor API Documentation: For more technical details on what data is sent and how it’s handled, refer to the Campaign Monitor API documentation, which outlines all the APIs the integration uses.
• Beaufort 12 Technical guide.
• Salesforce security policies. 

Summary

The Campaign Monitor for Salesforce integration is designed with robust security features to protect your data. It is a secure bridge between your Salesforce and Campaign Monitor accounts without independently accessing or storing your customer data. By limiting operations to user-initiated actions and providing full control over data sharing, we ensure your information remains secure.