Home/HighLevel/Features/Compliance/HighLevel security and compliance overview for agencies

Agency, Settings and Integrations

HighLevel security and compliance overview for agencies

In short

HighLevel’s security and compliance overview describes the safeguards built into the platform. It covers infrastructure hosting, network filtering, configuration automation, logging, encryption, backup, access controls, and compliance with standards such as SOC 2 and GDPR. The purpose is to protect customer data, ensure service availability, and meet regulatory expectations.

AreaCompliance · Compliance
Used forDigital marketing agency, Healthcare practice using the HIPAA add on, Ecommerce brand handling customer leads
Setup steps30 steps in 30 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Agency Founders who deliver marketing services to multiple clients, because the platform separates each client’s data with tenant level IDs.
  • Compliance officers at agencies, since the controls align with SOC 2, GDPR, and other industry standards.
  • IT managers responsible for data privacy, because encryption, backup retention, and access logging are built into the system.

02Security and compliance, explained

HighLevel hosts all product infrastructure on leading public cloud providers, Google Cloud Platform and Amazon Web Services, in the United States. Physical security and environmental controls are inherited from those providers.

The platform layers technical controls such as firewalls, network access lists, automated configuration management, and continuous monitoring. All actions generate logs that are stored centrally with restricted write access. Encryption protects data in transit with TLS 1.2/1.3 and at rest with AES 256. Backup processes retain seven days of database snapshots and protect backup files with access control and WORM settings.

Identity and access are managed through granular user roles, mandatory password complexity, and optional two factor authentication. Employee access to production systems follows a role based model and a Just In Time Access (JITA) process that limits exposure to customer portals. The overall design meets objectives for trust, availability, integrity, and compliance with standards such as SOC 2 Type II, GDPR, and HIPAA add on options.

03How businesses use security and compliance

  • Digital marketing agency. The agency creates separate user accounts for each client team, assigning role based permissions that restrict access to only that client’s data. Encryption and logging ensure that any activity on client campaigns is recorded and protected.
  • Healthcare practice using the HIPAA add on. The practice enables the HIPAA add on, which applies the same encryption, access controls, and logging while meeting the additional requirements for protected health information as outlined in the HIPAA compliance guide.
  • Ecommerce brand handling customer leads. The brand relies on automated backups that keep seven days of database snapshots and uses the recycle bin feature to restore contacts or leads that were accidentally deleted within 30 days.

04The numbers and rules that matter

  • Google provides a monthly uptime percentage of at least 99.5%.
  • AWS guarantees between 99.95% and 100% service reliability.
  • All data is encrypted in transit with TLS 1.2, 1.3 and 2,048 bit keys or better.
  • Stored data uses AES 256 encryption.
  • Passwords must be at least 8 characters with mixed case, special characters and numbers.
  • Portal JITA access is limited to 24 hours.

05How to set up and use security and compliance in HighLevel

Infrastructure security

  1. HighLevel hosts all product systems on Google Cloud Platform and Amazon Web Services, leveraging their audited physical and environmental controls.

Network and perimeter protection

  1. Firewalls and security groups deny any network connection that is not explicitly allowed, and access control lists are reviewed regularly.

Configuration management

  1. Server configurations are stored in images and configuration files; any deviation from the baseline is automatically corrected within 30 minutes.

Logging

  1. All application actions are recorded in a central logging system with write access limited to a small group of engineers.

Alerting and monitoring

  1. Automated monitors trigger alerts for error rates, abuse, or attacks, and can automatically throttle traffic or terminate processes at predefined thresholds.

Web application defenses

  1. Application firewalls and OWASP based rules block malicious traffic, including DDoS attacks, to keep customer sites available.

Development and release management

  1. Code changes undergo reviews, testing, and automated deployment; failed releases are rolled back automatically.

Vulnerability management

  1. Regular vulnerability scans and annual penetration tests identify risks, which are then prioritized for mitigation.

Data classification

  1. Customers are responsible for only capturing non sensitive data; credit card numbers, SSNs, and health information are prohibited unless a specific add on permits it.

Tenant separation

  1. Each customer’s data is isolated by unique identifiers, and authorization checks enforce that separation.

Encryption

  1. Data in transit uses TLS 1.2/1.3 with at least 2,048 bit keys; data at rest is encrypted with AES 256.

Key management

  1. Encryption keys are stored in a hardened Key Management System and rotated regularly; customer supplied keys are not supported.

System backups

  1. Databases are backed up daily, retaining seven days of snapshots; backup failures generate alerts for investigation.

Backup protections

  1. Backups are secured with access controls and write once read many (WORM) mechanisms.

Customer data backup restoration

  1. Users can restore deleted contacts, opportunities, and other records from the recycle bin within 30 days, or revert web page content via version history.

Product user management

  1. Admins create portal users, assign granular privileges, and limit access according to job responsibilities.

Product login protections

  1. Native login enforces an eight character password with mixed case, numbers, and special characters; two factor authentication can be required for all users.

Access to production infrastructure

  1. Employee access follows a role based model, requires bastion host authentication, and is limited to engineering staff.

Access to customer portals

  1. Support staff receive limited, time bound JITA access to a customer portal, logged and capped at 24 hours.

Corporate authentication and authorization

  1. Company network login requires multi factor authentication and adheres to password length and rotation policies.

Background checks and onboarding

  1. All new employees undergo third party background checks and acknowledge the employee handbook.

Policy management

  1. Written security policies are reviewed and approved at least annually.

Security awareness training

  1. Employees complete CyberSafety training upon hire and annually thereafter, covering phishing awareness.

Vendor management

  1. Third party vendors are required to provide contractual security and privacy controls; sub processors are listed in the Data Processing Agreement.

Endpoint protection

  1. Company laptops use full disk encryption and are managed via a mobile device management solution.

Sensitive data processing and storing

  1. HighLevel does not store credit card data and is not PCI DSS compliant; payment processing is handled by PCI compliant providers.

Privacy

  1. Personal data is not sold to third parties; privacy protections keep data private and unaltered.

Data retention and deletion

  1. Customer data remains while the account is active; written requests can delete data, but custom retention policies cannot be defined.

Breach response

  1. HighLevel notifies affected customers as required by law if a data breach occurs.

GDPR support

  1. Features help agencies meet GDPR requirements, but using HighLevel alone does not guarantee compliance.

06Settings that matter

  • Password policy. Requires a minimum of eight characters with mixed case, numbers, and special symbols for all native logins.
  • Two factor authentication. Provides an additional verification step for user logins; administrators can mandate its use for all users.
  • TLS encryption. Secures data in transit using TLS version 1.2 or 1.3 with keys of at least 2,048 bits.
  • AES, 256 encryption. Encrypts data at rest across the platform.
  • Backup retention period. Keeps seven days of database backups to enable restoration.

07Things to know before you rely on it

  • Customers cannot supply their own encryption keys; key management is handled only by HighLevel.
  • HighLevel does not store, process, or collect credit card information and is not PCI DSS compliant.
  • Custom data retention policies cannot be defined by customers; retention follows the platform default.
  • Customers cannot trigger a failover; disaster recovery is managed solely by HighLevel engineering teams.

08How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Businesses worry about keeping client information safe while still delivering fast, reliable marketing tools. The first setting to get right is the password policy and two factor authentication for every user in your portal.

Once the login protections are in place, I would verify that backups are running daily and that you can restore contacts from the recycle bin if needed.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about security and compliance.

Is HighLevel PCI DSS compliant?

No. HighLevel does not store or process credit card data and is not PCI DSS compliant. Payment transactions are handled by PCI compliant processors.

Can I use my own encryption keys with HighLevel?

Customer supplied encryption keys are not supported; HighLevel manages all encryption keys internally.

How long are database backups retained?

The platform retains seven days of database backups to enable restoration.

What password requirements does HighLevel enforce?

Passwords must be at least eight characters and include both lower and upper case letters, numbers, and special characters.

Does HighLevel provide a way for me to restore deleted contacts?

Yes. The recycle bin allows restoration of contacts, opportunities, custom fields, tags, notes, and tasks up to 30 days after deletion.

Will using HighLevel alone make my agency GDPR compliant?

HighLevel offers features that assist with GDPR compliance, but using the platform alone does not guarantee full compliance.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.