LeadConnector's primary security focus is to safeguard our customers’ data. LeadConnector has invested in the appropriate controls to protect and service our customers. This investment includes implementing dedicated corporate, product, and infrastructure security programs. Our Legal Team, in partnership with other departments, oversees the implementation of these programs.

Our Security and Compliance Objectives

We have developed our security framework using best practices for the SaaS industry.

Our key objectives include:

• Customer Trust and Protection: Deliver superior products and services while protecting the privacy and confidentiality of data.
• Availability and Continuity of Service: Ensure availability of the service and minimize risks to service continuity.
• Information and Service Integrity: Make sure that customer information is never corrupted or altered inappropriately.
• Compliance with Standards: Aim to comply with or exceed industry standard best practices.

Security Controls

To protect the data that is entrusted to us, LeadConnector utilizes layers of administrative, technical, and physical security controls throughout our organization. The following sections describe a subset of our most frequently asked questions about control.

Infrastructure Security

Cloud Hosting Provider

LeadConnector does not host any product systems or data within its physical offices.

LeadConnector outsources hosting of its product infrastructure to leading cloud infrastructure providers such as Google Cloud Platform Services and Amazon Web Services. Our product infrastructure resides in the United States. We place reliance on Google’s and AWS’s audited security and compliance programs for the efficacy of their physical, environmental, and infrastructure security controls.

• Google provides a monthly uptime percentage to customers of at least 99.5%. You can find more information about the controls, processes, and compliance measures implemented by Google on their publicly available Compliance Resource Center.
• AWS guarantees between 99.95% and 100% service reliability, ensuring redundancy to all power, network, and HVAC services. The business continuity and disaster recovery plans for AWS services have been independently validated as part of their SOC 2 Type 2 report and ISO 27001 certification. AWS’s compliance documentation and audit reports are publicly available at the AWS Cloud Compliance Page and the AWS Artifacts Portal.

Network and Perimeter

The LeadConnector product infrastructure enforces multiple layers of filtering and inspection on all connections across our web application, logical firewalls, and security groups. Network-level access control lists are implemented to prevent unauthorized access to our internal product infrastructure and resources. By default, firewalls are configured to deny network connections that are not explicitly authorized. Changes to our network and perimeter systems are controlled by standard change control processes. Firewall rulesets are reviewed periodically to help ensure that only necessary connections are configured.

Configuration Management

Automation drives LeadConnector's ability to scale with our customers’ needs, and rigorous configuration management is integrated into our day-to-day infrastructure processing. The product infrastructure is a highly automated environment that expands capacity as needed. All server configurations are embedded in images and configuration files, which are used when new containers are provisioned. Each container includes its own hardened configuration, and changes to the configuration and standard images are managed through a controlled change pipeline.

Server instances are tightly controlled from provisioning through de-provisioning, ensuring that deviations from configuration baselines are detected and reverted at a predefined cadence. In the event that a production server deviates or drifts from the baseline configuration, it will be overwritten with the baseline within 30 minutes. Patch management is handled using automated configuration management tools or by removing server instances that are no longer compliant with the expected baseline.

Logging

Actions and events that occur within the LeadConnector application are consistently and comprehensively logged. These logs are indexed and stored in a central logging solution hosted in LeadConnector's cloud environment. Security-relevant logs are also retained, indexed, and stored to facilitate investigation and response activities. The retention period of logs depends on the nature of the data logged. Write access to the storage service in which logs are stored is tightly controlled and limited to a small subset of engineers who require access.

Alerting and Monitoring

LeadConnector invests in automated monitoring, alerting, and response capabilities to continuously address potential issues.

The LeadConnector product infrastructure is instrumented to alert engineers and administrators when anomalies occur. In particular, error rates, abuse scenarios, application attacks, and other anomalies trigger automatic responses or alerts to the appropriate teams for response, investigation, and correction. Many automated triggers are also designed to immediately respond to anomalous situations. For example, traffic throttling, process termination, and similar functions are triggered at predefined thresholds.

Application Security

Web Application Defenses

All customer content hosted on the platform is protected by firewall and application security. The monitoring tools actively monitor the application layer and can alert on malicious behavior based on behavior type and session rate. The rules used to detect and block malicious traffic are aligned to the best practice guidelines documented by the Open Web Application Security Project (OWASP), specifically the OWASP Top 10 and similar recommendations. Protections from Distributed Denial of Service (DDoS) attacks are also incorporated, helping to ensure customers’ websites and other parts of the LeadConnector products are continuously available.

Development and Release Management

LeadConnector optimizes our products through a modern continuous delivery approach to software development. New code is regularly deployed. Code reviews, testing, and merge approval are performed before deployment. Static code analysis runs regularly against code repositories and blocks known misconfigurations from entering the code base. Approval is controlled by designated repository owners and once approved, code is automatically submitted to LeadConnector's continuous integration environment where compilation, packaging, and unit testing occur.

Dynamic testing for security vulnerabilities is performed periodically against our applications. Newly developed code is first deployed to a dedicated and separate QA environment for the last stage of testing before being promoted to production. Network-level and project-level segmentation prevents unauthorized access between QA and production environments. All code deployments are automated, and in case of failures, the changes can be reverted. The deploying team manages notifications regarding the health of their applications, and if a failure occurs, rollback processes are immediately engaged. We use extensive software gating and traffic management to control features based on customer preferences (private beta, public beta, full launch).

LeadConnector features seamless updates, and as a SaaS application, there is no downtime associated with releases. Major feature changes are communicated through in-app messages and/or product update posts.

Vulnerability Management

The LeadConnector team manages a multi-layered approach to vulnerability management, using a variety of industry-recognized tools and threat feeds to ensure comprehensive coverage of our technology stack. Vulnerability scans are configured to scan for vulnerabilities on a regular basis, using adaptive scanning inclusion lists for asset discovery as well as the latest vulnerability detection signatures. We perform annual penetration tests against our applications and infrastructures to identify vulnerabilities that may present security-related risks. Relevant findings are assessed, and mitigations are prioritized accordingly.

Customer Data Protection

Data Classification

Per the LeadConnector's Terms of Service, our customers are responsible for ensuring they only capture appropriate information to support their marketing, sales, services, content management, and operations processes. The LeadConnector products should not be used to collect or store sensitive information, such as credit or debit card numbers, financial account information, Social Security numbers, passport numbers, financial or health information except as otherwise permitted.

Tenant Separation

LeadConnector provides a multi-tenant SaaS solution where customer data is logically separated using unique IDs to associate data and objects to specific customers. Authorization rules are incorporated into the design architecture and validated on a continuous basis. Additionally, we log application authentication and associated changes, application availability, and user access and changes are logged.

Encryption

All data is encrypted in transit with TLS version 1.2, or 1.3 and 2,048-bit keys or better. Transport layer security (TLS) is also a default for customers who host their websites on the LeadConnector platform.

LeadConnector leverages several technologies to ensure stored data is encrypted at rest. Platform data is stored using AES-256 encryption. User passwords are hashed following industry best practices, and are encrypted at rest.

Key Management

Encryption keys for both in transit and at rest encryption are securely managed by the LeadConnector platform. TLS private keys for in-transit encryption are managed through our content delivery partner. Volume and field-level encryption keys for at rest encryption are stored in a hardened Key Management System (KMS). Keys are rotated at varying frequencies, depending upon the sensitivity of the data they govern. In general, TLS certificates are renewed annually. LeadConnector is unable to use customer-supplied encryption keys at this time.

Data Backup and Disaster Recovery

System Reliability and Recovery

LeadConnector is committed to minimizing system downtime. All LeadConnector product services are built with redundancy. Server infrastructure is strategically distributed across multiple distinct availability zones and virtual private cloud networks within our infrastructure providers, and all web, application, and database components are deployed with a point-in-time recovery.

Backup Strategy

• System Backups: Systems are backed up on a regular basis with established schedules and frequencies. Seven days’ worth of backups are kept for any database in a way that ensures restoration can occur easily.
• System Backups: Systems are backed up on a regular basis with established schedules and frequencies. Seven days’ worth of backups are kept for any database in a way that ensures restoration can occur easily.
• System Backups: Systems are backed up on a regular basis with established schedules and frequencies. Seven days’ worth of backups are kept for any database in a way that ensures restoration can occur easily.

Identity and Access Control

Product User Management

The LeadConnector products allow for granular authorization rules. Customers are empowered to create and manage the users in their portals, assign the privileges that are appropriate, and limit access as they see fit.

Product Login Protections

The LeadConnector products allow users to login to their LeadConnector accounts using the native LeadConnector login. The native login enforces a uniform password policy which requires a minimum of 8 characters and a

Combination of lower and upper case letters, special characters, and numbers. Portal administrators may require all users to have two-factor authentication enabled.

LeadConnector Employee Access to Customer Data

• Access to Production Infrastructure: User access to internal data stores and production infrastructure is strictly controlled. LeadConnector employees are granted access using a role-based access control (RBAC) model. Day-to-day access is minimized to members of the Engineering team and persistent administrative access is restricted. Additionally, direct network connections to product infrastructure devices over SSH or similar protocols are prohibited, and engineers are required to authenticate first through a bastion host or "jump box" or have assigned IAM role to the resource before accessing server environments.

Organizational and Corporate Security

Background Checks and Onboarding

LeadConnector employees undergo a third-party background check prior to formal employment offers. Upon hire, all employees must read and acknowledge LeadConnector's Employee Handbook and Code of Conduct, which help to define employee's security responsibilities in protecting company assets and data.

Security Awareness Training

LeadConnector employees are required to complete CyberSafety training when they start their employment, and training is made available annually thereafter. The CyberSafety training also includes phishing awareness.

Compliance

Sensitive Data Processing and Storing

Please see our Terms of Service and Privacy Policy for additional information on how and why we process data. LeadConnector does not store, process, or collect credit card information submitted to us by customers, and we are not PCI-DSS compliant. We leverage PCI-compliant payment card processors to ensure that our payment transactions are handled securely.

Data Retention and Data Deletion

Customer data is retained for as long as you remain an active customer. Current and former customers can make written requests to have certain data deleted, and LeadConnector will fulfill those requests as required by privacy rules and regulations. LeadConnector retains certain data like logs and related metadata in order to address security, compliance, or statutory needs.

Privacy Program Management

LeadConnector's Legal Team collaborates with our engineering and product development teams to implement an effective privacy program. Information about our commitment to the privacy of your data is described in greater detail in our Privacy Policy and Data Processing Agreement.

Breach Response

LeadConnector will notify customers as required by law if it becomes aware of a data breach that impacts your personal data.