Skip to content
Liquid Vision
PlatformMethodProductsResultsSign inTalk to us
Legal

Security Policy

Last Updated: January 29, 2025

At Liquid Vision AI, Inc., we understand that the security of your business data is critical. Liquid Vision is built with security at its core, implementing industry-standard practices and controls to protect your information.

For security-related inquiries or to report a vulnerability, contact us at info@liquid-vision.ai

Liquid Vision AI, Inc.

500 8th Avenue FRNT 3, Manhattan, NY 10018, United States

info@liquid-vision.ai

Data Protection

Encryption

Data in Transit:

  • All data transmitted between your browser and our servers is encrypted using TLS 1.2 or higher
  • We enforce HTTPS across all connections
  • We use strong cipher suites and regularly update our TLS configuration

Data at Rest:

  • All customer data stored in our databases is encrypted using AES-256 encryption
  • Encryption keys are managed securely and rotated regularly
  • Backups are encrypted using the same standards as primary data

Data Isolation

Multi-Tenant Architecture:

  • Each organization's data is logically isolated from other organizations
  • Row-level security policies ensure users can only access data belonging to their organization
  • Database queries are scoped to prevent cross-tenant data access
  • API endpoints enforce organization-level access controls

Your Data Is Never:

  • Shared with other Liquid Vision customers
  • Combined with other organizations' data
  • Used to train AI models for other customers
  • Sold or transferred to third parties

Data Residency

  • Primary data storage is located in the United States
  • We use reputable cloud infrastructure providers with SOC 2 Type II certification
  • Backup data is stored in geographically separate data centers for redundancy

Access Controls

Authentication

Password Security:

  • Passwords are hashed using industry-standard algorithms (bcrypt)
  • We enforce minimum password complexity requirements
  • Passwords are never stored in plain text

Session Management:

  • Secure session tokens with automatic expiration
  • Sessions are invalidated upon logout
  • Concurrent session limits may be enforced based on subscription plan

Multi-Factor Authentication (MFA):

  • MFA is available for all accounts
  • We strongly recommend enabling MFA for all users
  • Enterprise plans may enforce mandatory MFA

Role-Based Access Control (RBAC)

We implement role-based access control to ensure users have appropriate permissions:

RoleDescriptionPermissions
Super AdminPlatform administratorsFull system access (Liquid Vision AI staff only)
Org AdminOrganization administratorsManage users, settings, billing, all data
UserStandard usersAccess assigned features and data
Read-OnlyView-only accessView reports and dashboards only

Principle of Least Privilege

  • Users are granted only the minimum permissions necessary for their role
  • Administrative access is restricted and monitored
  • Elevated privileges require additional authentication

Infrastructure Security

Cloud Infrastructure

Hosting Provider:

  • We use enterprise-grade cloud infrastructure providers
  • Our providers maintain SOC 2 Type II, ISO 27001, and other relevant certifications
  • Physical data centers are secured with 24/7 monitoring, biometric access, and environmental controls

Network Security:

  • Virtual private cloud (VPC) isolation
  • Network firewalls and security groups restrict traffic
  • DDoS protection and mitigation
  • Regular vulnerability scanning of network infrastructure

Server Security

  • Operating systems are hardened according to industry benchmarks
  • Regular security patches and updates
  • Unnecessary services and ports are disabled
  • Server access is restricted to authorized personnel via secure channels

Database Security

  • Databases are not directly accessible from the public internet
  • Database connections require authentication and encryption
  • Regular automated backups with point-in-time recovery capability
  • Database activity logging and monitoring

Application Security

Secure Development Practices

Secure Software Development Lifecycle (SDLC):

  • Security considerations are integrated throughout the development process
  • Code reviews include security review components
  • Developers receive security awareness training

Code Security:

  • Static code analysis to identify vulnerabilities
  • Dependency scanning for known vulnerabilities in third-party libraries
  • Regular updates to address security issues in dependencies

OWASP Top 10 Protection

We implement controls to protect against the OWASP Top 10 security risks:

RiskMitigation
InjectionParameterized queries, input validation, ORM usage
Broken AuthenticationSecure session management, MFA support, account lockout
Sensitive Data ExposureEncryption, secure transmission, access controls
XML External EntitiesDisabled XML external entity processing
Broken Access ControlRBAC, row-level security, authorization checks
Security MisconfigurationSecure defaults, hardened configurations, regular audits
Cross-Site Scripting (XSS)Output encoding, Content Security Policy, input sanitization
Insecure DeserializationInput validation, type checking, integrity verification
Vulnerable ComponentsDependency scanning, regular updates
Insufficient LoggingComprehensive logging, alerting, incident response

API Security

  • API authentication using secure tokens
  • Rate limiting to prevent abuse
  • Input validation on all API endpoints
  • API activity logging and monitoring

Data Backup and Recovery

Backup Procedures

Automated Backups:

  • Daily automated backups of all customer data
  • Point-in-time recovery capability
  • Backups are encrypted and stored in geographically separate locations

Backup Retention:

  • Daily backups retained for 30 days
  • Weekly backups retained for 90 days
  • Monthly backups retained for 1 year

Disaster Recovery

Recovery Time Objective (RTO)

4 hours

Recovery Point Objective (RPO)

1 hour

Business Continuity:

  • Documented disaster recovery procedures
  • Regular testing of recovery procedures
  • Redundant infrastructure to minimize single points of failure

Monitoring and Incident Response

Security Monitoring

Continuous Monitoring:

  • 24/7 infrastructure and application monitoring
  • Automated alerting for anomalous activity
  • Log aggregation and analysis
  • Intrusion detection systems

Audit Logging:

  • User authentication events
  • Administrative actions
  • Data access and modifications
  • API requests

Logs are retained for a minimum of 90 days and are protected against tampering.

Incident Response Plan

We maintain a documented incident response plan that includes:

1
Detection:Automated monitoring and alerting systems
2
Analysis:Rapid assessment of incident scope and severity
3
Containment:Immediate actions to limit impact
4
Eradication:Removal of threat and root cause
5
Recovery:Restoration of normal operations
6
Post-Incident:Review, documentation, and improvements

Incident Classification

SeverityDescriptionResponse Time
CriticalActive breach, data compromiseImmediate (< 1 hour)
HighSignificant vulnerability, potential breach< 4 hours
MediumSecurity issue requiring attention< 24 hours
LowMinor issue, no immediate risk< 72 hours

Breach Notification

In the event of a security breach affecting your data, we will:

  • Notify affected customers within 72 hours of becoming aware of the breach
  • Provide details about the nature of the breach
  • Describe the data potentially affected
  • Outline steps we are taking to address the incident
  • Provide recommendations for protective measures you can take

Vendor and Third-Party Security

Third-Party Risk Management

We carefully evaluate the security practices of third-party vendors and service providers:

  • Security assessments prior to engagement
  • Review of certifications and compliance reports
  • Contractual security requirements
  • Ongoing monitoring of vendor security posture

Third-Party Services

Our platform integrates with the following categories of third-party services:

Service TypeSecurity Requirements
Cloud InfrastructureSOC 2 Type II, encryption, access controls
Payment ProcessingPCI DSS compliance
Email ServicesTLS encryption, authentication
AnalyticsData anonymization, privacy controls
AI/ML ProcessingData encryption, processing agreements

All third-party services are contractually obligated to maintain appropriate security measures.

Employee Security

Personnel Security

Background Checks:

  • Background checks conducted for employees with access to customer data
  • Verification of employment history and references

Security Training:

  • Security awareness training for all employees
  • Role-specific security training for technical staff
  • Regular updates on emerging threats and best practices

Access Management:

  • Access to production systems limited to essential personnel
  • Access reviewed and revoked upon role change or termination
  • Privileged access requires additional authorization

Acceptable Use

All employees are required to adhere to our acceptable use policies, including:

  • Secure handling of customer data
  • Use of strong passwords and MFA
  • Reporting of security incidents
  • Protection of company assets and information

Compliance and Certifications

Regulatory Compliance

We design our security practices to support compliance with applicable regulations:

  • GDPR: Data protection measures for EU personal data
  • CCPA: Privacy protections for California residents
  • SOC 2: Controls relevant to security, availability, and confidentiality

Security Assessments

Internal Assessments:

  • Regular internal security reviews
  • Vulnerability assessments
  • Configuration audits

External Assessments:

  • Periodic third-party penetration testing
  • Independent security assessments as appropriate
  • Continuous vulnerability monitoring

Certifications (Planned)

We are working toward the following certifications:

  • SOC 2 Type II
  • ISO 27001

Please contact us for the current status of our certification efforts.

Customer Security Responsibilities

Security is a shared responsibility. While we secure the Liquid Vision platform, you are responsible for:

Account Security

  • Using strong, unique passwords
  • Enabling multi-factor authentication (MFA)
  • Protecting your login credentials
  • Promptly reporting suspected unauthorized access

User Management

  • Granting appropriate access levels to users
  • Promptly removing access for departed employees
  • Regularly reviewing user access and permissions

Data Security

  • Ensuring you have the right to upload data to the platform
  • Not uploading malicious content
  • Maintaining your own backup copies of critical data
  • Complying with applicable data protection laws

Security Best Practices

We recommend the following security practices:

  • Enable MFA for all user accounts
  • Use unique, strong passwords (consider a password manager)
  • Regularly review user access and remove inactive accounts
  • Keep your browser and devices updated
  • Be vigilant against phishing attempts
  • Report any suspicious activity immediately

Vulnerability Disclosure

Reporting Security Vulnerabilities

If you discover a security vulnerability in Liquid Vision, we encourage responsible disclosure. Please report vulnerabilities to:

Email: info@liquid-vision.ai

Subject Line: Security Vulnerability Report

Please include:

  • Description of the vulnerability
  • Steps to reproduce
  • Potential impact
  • Any suggested remediation

Our Commitment

When you report a vulnerability:

  • We will acknowledge receipt within 48 hours
  • We will investigate and validate the report
  • We will work to remediate confirmed vulnerabilities promptly
  • We will keep you informed of our progress
  • We will not take legal action against good-faith security researchers

Responsible Disclosure Guidelines

We ask that you:

  • Allow us reasonable time to address the issue before public disclosure
  • Avoid accessing or modifying other users' data
  • Do not perform denial of service attacks
  • Do not use social engineering against our employees

Security Updates

Keeping This Policy Current

We regularly review and update our security practices. This Security Policy will be updated to reflect material changes in our security measures.

Notification of Changes

We will notify customers of significant changes to this Security Policy via:

  • Email notification
  • Notice on the Liquid Vision platform
  • Update to this document

Version History

VersionDateSummary of Changes
1.0January 29, 2025Initial publication

Contact Us

For questions about our security practices or to report a security concern:

Liquid Vision AI, Inc.

500 8th Avenue FRNT 3, Manhattan, NY 10018, United States

info@liquid-vision.ai

For urgent security matters, please include "URGENT" in the subject line.

Summary of Key Security Measures

CategoryMeasures
EncryptionTLS 1.2+ in transit, AES-256 at rest
Data IsolationMulti-tenant isolation, row-level security
Access ControlRBAC, MFA support, least privilege
InfrastructureSOC 2 certified providers, VPC isolation, firewalls
ApplicationOWASP Top 10 protection, secure SDLC, code reviews
BackupDaily backups, encrypted, geographically distributed
Monitoring24/7 monitoring, audit logging, intrusion detection
Incident ResponseDocumented plan, 72-hour breach notification
ComplianceGDPR, CCPA, working toward SOC 2

This Security Policy is effective as of January 29, 2025.

Terms of ServicePrivacy PolicySecurity PolicySMS Terms & Conditions
Liquid Vision

The AI operating system for beverage alcohol.

PlatformLiquid Vision OSMethodResults
ProductsJetstreamPulse IDLead BuilderSales IQPerformance Plus
CompanyAbout usLV LabsContact us
© 2026 Liquid Vision AI, Inc.Terms · Privacy · Security · SMS Terms