LDImpact Information Security Practices

We collect and process only the data needed to provide the Service, and we handle it in accordance with our Privacy Policy.

• Data minimization. Optional AI-assisted insights transmit only a limited, aggregate summary of analysis results to our AI sub-processor; that summary is designed to exclude individual-level personal data.
• No sale of data; no advertising. We do not sell Customer Data and do not use it for advertising.
• Customer ownership. Customers retain ownership of their Customer Data; we process it to provide the Service and as instructed.
• Sub-processors. We use a limited set of vetted sub-processors for cloud infrastructure and AI functionality, described in our Privacy Policy.

Access to Customer Data is restricted based on the principle of least privilege.

• Role-based access control. The Service enforces distinct roles (for example, organization users, service-provider administrators, and LDImpact administrators), each with scoped permissions.
• Multi-tenant isolation. Each organization's data is logically isolated; users of one organization cannot access another organization's data, and each Service Provider's Client Organizations are separated from one another.
• Authentication. Access requires authentication with an email and password. Passwords are stored only as salted, one-way bcrypt hashes and are never stored or transmitted in plaintext; LDImpact personnel cannot retrieve user passwords.
• Session security. Authenticated sessions use signed, HTTP-only cookies with a limited lifetime, transmitted over encrypted connections.
• Administrative access. Internal administrative access to production systems is limited to authorized personnel and used only as necessary to operate and support the Service.

• Encryption in transit. All traffic between users and the Service is encrypted using industry-standard TLS (HTTPS).
• Authorization enforcement. Authorization checks are enforced server-side on requests, including data-scoping and administrative functions.
• Input handling. The application validates and constrains inputs and uses parameterized database access to guard against common injection attacks.
• Password policy. Self-registered accounts are subject to password-strength requirements.
• Change management and testing. Application changes are version-controlled and validated by an automated test suite — including tests covering authentication, access control, and data isolation — prior to deployment.
• Dependency management. We use maintained, widely-used software components and update them as appropriate.

• Managed cloud infrastructure. The Service runs on Amazon Web Services (AWS) using managed compute and database services designed for reliability.
• Health checks and automated recovery. The Service uses automated health checks; deployments that fail health checks are automatically rolled back to preserve availability.
• Backups. The Service's database runs on managed infrastructure with automated backup capabilities to support recovery.
• Monitoring. Operational logs and metrics are used to monitor the health of the Service.

• AWS data centers. The Service is hosted in AWS data centers located in the United States. AWS maintains extensive physical and environmental security controls and holds a range of independent certifications and attestations (for example, SOC 1/2/3 and ISO 27001) covering its infrastructure.
• Physical security. Physical access to the underlying infrastructure is managed by AWS and inherited by the Service; LDImpact does not operate its own data centers.
• Network security. The Service is accessed over encrypted HTTPS connections. Application and database resources run within AWS's network environment, and administrative interfaces require authentication.
• Encryption at rest. Stored data resides within AWS infrastructure, which provides encryption-at-rest capabilities for supported services.