Security Policy

Last Updated: October 2, 2025

At Clients.ai (operated by KC Meta Ventures, Inc.), we take the security and protection of your data seriously. This Security Policy describes the technical and organizational security measures we implement to safeguard personal information, platform infrastructure, and user data in connection with our AI-powered marketing platform and Services.

This Security Policy supplements our Privacy Policy and Terms of Service and should be read in conjunction with those documents.

IMPORTANT SECURITY DISCLAIMER

While we implement robust security measures, no security system is absolutely infallible or impenetrable. We cannot guarantee that unauthorized access, hacking, data breaches, or other security violations will never occur.

By using Clients.ai Services, you acknowledge and accept the inherent security risks of internet-based services and electronic data transmission and storage. You agree that Clients.ai shall not be liable for any security breach or unauthorized access except as required by applicable law.

1. Technical Security Measures

1.1 Data Encryption

  • Encryption in Transit: All data transmitted between your browser and our servers is encrypted using Transport Layer Security (TLS) 1.2 or higher with strong cipher suites. We enforce HTTPS for all connections.
  • Encryption at Rest: Sensitive data stored in our databases and file systems is encrypted using industry-standard AES-256 encryption or equivalent.
  • End-to-End Encryption: Where applicable, we implement end-to-end encryption for sensitive communications and data transfers.

1.2 Authentication and Access Controls

  • Password Security: User passwords are hashed using bcrypt or Argon2 with salt, making them computationally infeasible to reverse-engineer.
  • Multi-Factor Authentication (MFA): We support optional MFA for user accounts to add an additional layer of security.
  • Role-Based Access Control (RBAC): Access to systems, data, and administrative functions is restricted based on job responsibilities and follows the principle of least privilege.
  • Session Management: User sessions are secured with httpOnly and secure cookies, automatic timeouts, and protection against session fixation and hijacking.
  • API Authentication: API access requires secure API keys or OAuth 2.0 tokens with appropriate scopes and rate limiting.

1.3 Network Security

  • Firewalls: Network firewalls and web application firewalls (WAFs) protect against unauthorized access and malicious traffic.
  • DDoS Protection: Distributed Denial of Service (DDoS) mitigation services protect against volumetric attacks and ensure service availability.
  • Intrusion Detection and Prevention: Automated systems monitor for suspicious network activity, unauthorized access attempts, and known attack patterns.
  • Network Segmentation: Production, staging, and development environments are logically separated with restricted network access between segments.

1.4 Application Security

  • Secure Development Practices: We follow secure coding standards (OWASP Top 10) and conduct code reviews to identify and remediate vulnerabilities.
  • Input Validation: All user inputs are validated, sanitized, and escaped to prevent injection attacks (SQL injection, cross-site scripting, command injection).
  • CSRF Protection: Cross-Site Request Forgery (CSRF) tokens protect against unauthorized actions.
  • Security Headers: HTTP security headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) protect against common web vulnerabilities.
  • Dependency Management: Third-party libraries and dependencies are regularly updated and scanned for known vulnerabilities.

1.5 Infrastructure Security

  • Cloud Infrastructure: We leverage enterprise-grade cloud infrastructure providers (AWS, Google Cloud, Azure) with SOC 2, ISO 27001, and other security certifications.
  • Server Hardening: Servers are configured following security best practices, with unnecessary services disabled and security patches applied regularly.
  • Automated Patching: Operating systems, software, and infrastructure components receive timely security updates and patches.
  • Backup and Disaster Recovery: Regular automated backups ensure data recoverability. Backups are encrypted and stored in geographically separate locations.
  • High Availability: Redundant systems, load balancing, and failover mechanisms ensure service continuity.

2. Organizational Security Measures

2.1 Security Policies and Procedures

  • Information Security Policy: Comprehensive internal security policies govern data handling, access controls, and security practices.
  • Incident Response Plan: Documented procedures for detecting, responding to, and recovering from security incidents and data breaches.
  • Business Continuity Plan: Plans and procedures to maintain operations during disruptions or disasters.
  • Change Management: Formal processes for reviewing, testing, and approving changes to production systems.

2.2 Employee Security

  • Background Checks: Employees with access to sensitive data undergo background checks where permitted by law.
  • Security Training: All employees receive regular security awareness training covering phishing, social engineering, password security, and data protection.
  • Confidentiality Agreements: Employees sign confidentiality and non-disclosure agreements.
  • Access Revocation: Access credentials are immediately revoked upon employee termination or role change.
  • Principle of Least Privilege: Employees have access only to systems and data necessary for their job functions.

2.3 Vendor and Third-Party Security

  • Vendor Risk Assessment: Third-party vendors and service providers are evaluated for security practices before engagement.
  • Contractual Safeguards: Vendor contracts include data protection and security requirements, including confidentiality obligations and incident notification requirements.
  • Ongoing Monitoring: We periodically review vendor security posture and compliance with contractual obligations.

2.4 Physical Security

  • Data Center Security: Our cloud infrastructure providers maintain SOC 2-compliant data centers with physical access controls, video surveillance, and 24/7 monitoring.
  • Office Security: Corporate offices have badge access systems, visitor logs, and security protocols.
  • Device Security: Company devices are encrypted, password-protected, and subject to remote wipe capabilities.

3. Security Monitoring and Testing

3.1 Continuous Monitoring

  • Security Information and Event Management (SIEM): Centralized logging and real-time analysis of security events across infrastructure.
  • Intrusion Detection: Automated systems monitor for unauthorized access, suspicious behavior, and anomalous patterns.
  • Vulnerability Scanning: Regular automated scans identify potential security weaknesses in applications and infrastructure.
  • Log Retention: Security logs are retained for analysis, forensics, and compliance purposes.

3.2 Security Testing

  • Penetration Testing: Periodic third-party penetration tests simulate real-world attacks to identify vulnerabilities.
  • Vulnerability Assessments: Regular security assessments evaluate the overall security posture of systems and applications.
  • Security Code Reviews: Code is reviewed for security vulnerabilities during development and deployment.
  • Automated Security Scanning: Continuous integration pipelines include automated security testing (SAST, DAST).

3.3 Compliance Audits

We conduct periodic internal and external audits to assess compliance with security policies, industry standards, and regulatory requirements. Our goal is to achieve and maintain relevant certifications such as:

  • SOC 2 Type II (in progress)
  • ISO 27001 (planned)
  • PIPEDA compliance (current)

4. Incident Response and Breach Notification

4.1 Incident Response Process

In the event of a suspected or confirmed security incident, we follow a structured incident response process:

  1. Detection and Analysis: Identify the nature, scope, and impact of the incident
  2. Containment: Isolate affected systems to prevent further damage
  3. Eradication: Remove the threat and close security vulnerabilities
  4. Recovery: Restore systems and data to normal operations
  5. Post-Incident Review: Analyze the incident, identify lessons learned, and implement improvements

4.2 Data Breach Notification

If a data breach involving personal information occurs, we will:

  • Notify Affected Individuals: Provide timely notification to individuals whose personal information was compromised, as required by applicable law (PIPEDA, GDPR, state breach notification laws)
  • Notify Authorities: Report the breach to relevant privacy regulators (Office of the Privacy Commissioner of Canada, supervisory authorities) as required
  • Provide Information: Include details about the breach, types of information affected, steps taken, and recommended actions for affected individuals
  • Offer Assistance: Provide support, resources, or credit monitoring services where appropriate

Reporting Security Issues: If you discover a security vulnerability or incident related to Clients.ai, please report it immediately to security@Clients.ai. For legal or privacy-related security concerns, you may also contact legal@clients.ai.

5. Data Protection and Privacy

5.1 Data Minimization

We collect and retain only the personal information necessary to provide the Services and fulfill legitimate business purposes.

5.2 Data Segregation

Customer data is logically segregated to prevent unauthorized access between accounts. Each customer's data is isolated and accessible only by authorized users.

5.3 Secure Data Disposal

When personal information is no longer needed, it is securely deleted or anonymized using industry-standard data sanitization methods to prevent recovery.

5.4 Privacy by Design

Security and privacy considerations are integrated into the design and development of new features and systems from the outset.

6. User Responsibilities for Security

Security is a shared responsibility. While we implement robust security measures, you also play a critical role in protecting your account and data:

6.1 Account Security

  • Strong Passwords: Use unique, complex passwords (minimum 12 characters with uppercase, lowercase, numbers, and symbols)
  • Password Management: Do not share passwords or reuse passwords across multiple services
  • Enable MFA: Enable multi-factor authentication for an additional security layer
  • Monitor Account Activity: Regularly review account activity and report suspicious behavior immediately
  • Secure Devices: Ensure devices used to access Clients.ai are secured with antivirus software, firewalls, and up-to-date operating systems

6.2 Phishing and Social Engineering

  • Be cautious of unsolicited emails, phone calls, or messages requesting login credentials or sensitive information
  • Verify the authenticity of communications claiming to be from Clients.ai
  • Do not click on suspicious links or download attachments from unknown sources
  • Report suspected phishing attempts to security@Clients.ai

6.3 Reporting Security Issues

If you suspect unauthorized access to your account, discover a security vulnerability, or observe suspicious activity:

  • Change your password immediately
  • Contact us at security@Clients.ai
  • Provide details about the issue or incident

You are solely responsible for maintaining the confidentiality of your account credentials and for all activities that occur under your account.

7. Security Limitations and Disclaimers

No Guarantee of Absolute Security: Despite our comprehensive security measures, we cannot and do not guarantee that:

  • The Services will be completely secure or free from vulnerabilities
  • Unauthorized access, hacking, data breaches, or security incidents will never occur
  • Data transmission over the internet or wireless networks is completely secure
  • Third-party services or infrastructure we rely upon will remain secure

You acknowledge and accept these inherent security risks. To the maximum extent permitted by law, Clients.ai shall not be liable for any damages, losses, or consequences arising from security breaches, unauthorized access, or data loss, except as required by applicable law.

7.1 Third-Party Security

We rely on third-party service providers (cloud infrastructure, payment processors, AI model providers, etc.) for certain aspects of our Services. While we select reputable vendors and require contractual security commitments, we are not responsible for the security practices of third parties. Security breaches or failures by third-party providers are beyond our control.

7.2 User-Generated Content and Links

The Services may allow you to upload content, integrate with third-party services, or access external websites. We are not responsible for the security of content you upload or third-party services you choose to integrate. Exercise caution and implement your own security measures for such content and integrations.

8. Updates to This Security Policy

We may update this Security Policy periodically to reflect changes in our security practices, technologies, or legal requirements. We will post the updated Security Policy on this page and update the "Last Updated" date.

Material changes to this Security Policy will be communicated via email or prominent notice on our website.

9. Contact Information

For questions about this Security Policy, to report security vulnerabilities, or for security-related inquiries, please contact:

KC Meta Ventures, Inc.
Attention: Security Team
141 Sandwich Street North
Amherstburg, Ontario, N9V 2V1
Canada

Email: security@Clients.ai

For legal matters: legal@clients.ai
For privacy & compliance: compliance@Clients.ai

Legal Entity

Clients.ai is operated by KC Meta Ventures, Inc., an Ontario corporation with principal offices at 141 Sandwich Street North, Amherstburg, Ontario, N9V 2V1, Canada.

Note: This Security Policy should be read in conjunction with our Terms of Service, Privacy Policy, and Acceptable Use Policy.