LogiqLeadBack to Home

Legal

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Acceptable Use Policy
  • Email Compliance
  • Data Processing Addendum
  • Subprocessors
  • Security Overview

Security Overview

Effective 2026-06-30Updated 2026-06-30

This document describes the security practices and infrastructure of the LogiqLead platform operated by Logiqcube Consulting.

Important: Logiqcube Consulting does not currently hold SOC 2, ISO 27001, HIPAA, or PCI-DSS certifications. We implement security practices appropriate for our scale and the nature of the data processed. We may pursue certifications in the future as the platform matures.

1. Infrastructure

1.1 Cloud Provider

LogiqLead is hosted on enterprise-grade cloud infrastructure (AWS/Azure) designed for high availability and resilience.

Our hosting providers maintain SOC 2 Type II, ISO 27001, and PCI-DSS Level 1 compliance certifications.

1.2 Data Center Locations

  • Primary: Secure cloud data center region with redundant availability zones.
  • Backup: Geographically separated automated daily encrypted backups.

1.3 Network Security

  • Distributed Denial of Service (DDoS) mitigation and rate limiting.
  • Web Application Firewall (WAF) inspects incoming requests against OWASP Top 10 threats.
  • Network segmentation and access controls
  • Regular vulnerability scanning

2. Data Protection

2.1 Encryption in Transit

  • All traffic encrypted via TLS (minimum TLS 1.2)
  • HTTP Strict Transport Security (HSTS) enforced
  • Certificate management and rotation

2.2 Encryption at Rest

  • Database encryption at rest using AES-256 standard.
  • File and object storage encrypted at rest with server-side AES-256 encryption.
  • Backup encryption

2.3 Key Management

Cryptographic keys are managed via secure cloud Key Management Services (KMS) with automated rotation.

3. Authentication and Access

3.1 User Authentication

  • Password-based authentication with bcrypt hashing
  • Multi-factor authentication (MFA) support for enhanced account security.
  • Session management with secure tokens
  • Account lockout after failed attempts

3.2 Administrative Access

  • Role-Based Access Control (RBAC)
  • Principle of least privilege
  • Separate administrative accounts
  • Multi-factor authentication required for admin access
  • All admin actions logged and auditable

3.3 API Security

  • API key authentication for programmatic access
  • Rate limiting per Account
  • Input validation and output encoding
  • Protection against common attack vectors

4. Application Security

4.1 Development Practices

  • Secure coding guidelines based on OWASP recommendations
  • Code review requirements for changes
  • Dependency vulnerability scanning
  • Regular security training for development team

4.2 Vulnerability Management

  • Regular internal security reviews
  • Security audits and vulnerability scans are conducted on a scheduled annual basis.
  • Bug bounty program

4.3 Incident Response

  • Incident response plan with defined escalation paths
  • Security monitoring and alerting
  • Post-incident review process

5. Data Handling

5.1 Data Classification

Level Examples Protection
Public Marketing content, public documentation Standard
Internal Usage analytics, aggregated data Access control
Confidential User data, email content, leads Encryption, access logging
Restricted Passwords, payment data, API keys Encryption, strict access control

5.2 Data Backup

  • Regular automated backups
  • Backup restoration testing

5.3 Data Deletion

  • Secure deletion when data is removed
  • Verification of deletion across systems

6. Email Security

6.1 Email Authentication

  • SPF records configured for sending domains
  • DKIM signing for email authentication
  • DMARC policy support

6.2 Reputation Management

  • Bounce and complaint handling
  • Sending volume monitoring

7. Monitoring and Logging

  • Application logging with structured format
  • Access logging for administrative actions
  • real-time cloud observability and APM monitoring.

8. Business Continuity

  • Regular backup restoration testing

9. Reporting Security Issues

If you discover a security vulnerability, please report it responsibly:

Email: [email protected]

We commit to:

  • Acknowledging receipt within 48 hours
  • Providing a remediation timeline within 7 days
  • Not taking legal action against good-faith security researchers who follow responsible disclosure

Contact

For security-related inquiries, contact:

Logiqcube Consulting

Email: [email protected]

© 2026 Logiqcube Consulting. All rights reserved.