ClickUp is hosted entirely on Amazon Web Services (AWS), providing end-to-end security and privacy features built in. Our team takes additional proactive measures to ensure a secure infrastructure environment. For additional, more specific details regarding AWS security, please refer to https://aws.amazon.com/security/.
What is this document, why does it exist, what does it cover, and who is in charge of it?
This policy defines behavioral, process, technical, and governance controls pertaining to security at ClickUp that all personnel are required to implement in order to ensure the confidentiality, integrity, and availability of the ClickUp service and data (“Policy”). All personnel must review and be familiar with the rules and actions set forth below.
This Policy defines security requirements for:
In the event of a conflict, the more restrictive measures apply.
This Policy was created in close collaboration with and approved by ClickUp executives. At least annually, it is reviewed and modified as needed to ensure clarity, sufficiency of scope, concern for customer and personnel interests, and general responsiveness to the evolving security landscape and industry best practices.
The ClickUp security team oversees the implementation of this Policy, including
The security team maintains a Risk Management Framework derived from NIST SP 800-39 - “Managing Information Security Risk: Organization, Mission, and System View” and NIST SP 800-30 - “Guide for Conducting Risk Assessments”. Risk assessment exercises inform prioritization for ongoing improvements to ClickUp’s security posture, which may include changes to this Policy itself.
Our Risk Management Framework incorporates the following:
What are ClickUp’s expectations of its personnel and the workplace regarding systems and data?
ClickUp is committed to protecting its customers, personnel, partners, and the company from illegal or damaging actions by individuals, either knowingly or unknowingly in the context of its established employment culture of openness, trust, maturity, and integrity.
This section outlines expected personnel behaviors affecting security and the acceptable use of computer systems at ClickUp. These rules are in place to protect our personnel and ClickUp itself, in that inappropriate use may expose customers and partners to risks including malware, viruses, compromise of networked systems and services, and legal issues.
The first line of defense in data security is the informed behavior of personnel, who play a significant role in ensuring the security of all data, regardless of format. Such behaviors include those listed in this section as well as any additional requirements specified in the employee handbook, specific security processes, and other applicable codes of conduct.
All employees and contractors must attend the ClickUp security training program, offered at least twice annually, to inform all users of the requirements of this Policy.
It is the responsibility of all personnel to take positive action to maintain physical security. Challenge any unrecognized person present in a restricted office location. Any challenged person who does not respond appropriately should be immediately reported to supervisory staff and the security team. All visitors to ClickUp offices must be registered as such or accompanied by a ClickUp employee.
Personnel should maintain workspaces clear of sensitive or confidential material and take care to clear workspaces of such material at the end of each workday.
Unattended devices must be locked. All devices will have an automatic screen lock function set to automatically activate upon no more than fifteen minutes of inactivity.
Systems are to be used for business purposes in serving the interests of the company, and of our clients and partners in the course of normal business operations. Personnel are responsible for exercising good judgment regarding the reasonableness of personal use of systems. Only ClickUp-managed hardware and software is permitted to be connected to or installed on corporate equipment or networks and used to access ClickUp data. ClickUp-managed hardware and software includes those either owned by ClickUp or owned by ClickUp personnel but enrolled in a ClickUp device management system. Only software that has been approved for corporate use by ClickUp may be installed on corporate equipment. All personnel must read and understand the list of prohibited activities outlined in this Policy. Modifications or configuration changes are not permitted without explicit written consent by the ClickUp security team.
Personnel may not configure work devices to make backups of device data. Instead, personnel are expected to operate primarily “in the cloud” and treat local storage on computing devices as ephemeral. Making a practice of keeping important work artifacts replicated into company-approved secure cloud storage (e.g. Google Docs) ensures that even in the event of a corporate device being lost, stolen, or damaged, such work artifacts will be immediately recoverable on a replacement device.
The following activities are prohibited. Under certain conditions and with the explicit written consent of the security team, personnel may be exempted from certain of these restrictions during the course of their legitimate job responsibilities (e.g. planned penetration testing, systems administration staff may have a need to disable the network access of a host if that host is disrupting production services).
The list below is by no means exhaustive, but attempts to provide a framework for activities which fall into the category of unacceptable use.
Personnel devices and their software configuration may be managed remotely by members of the security team via configuration-enforcement technology. Such technology may be used for purposes including auditing/installing/removing software applications or system services, managing network configuration, enforcing password policy, encrypting disks, copying data files to/from employee devices, and any other allowed interaction to ensure that employee devices comply with this Policy.
All software programs, data, and documentation generated or provided by personnel while providing services to ClickUp or for the benefit of ClickUp are the property of ClickUp unless otherwise covered by a contractual agreement.
While ClickUp’s network administration desires to provide a reasonable level of privacy, users should be aware that the data they create on the corporate systems remains the property of ClickUp. Due to the need to protect ClickUp’s network, management does not intend to guarantee the privacy of personnel’s personal information stored on any network device belonging to ClickUp. Personnel are responsible for exercising good judgment regarding the reasonableness of personal use such as general web browsing or personal email. If there is any uncertainty, personnel should consult the security team or their manager.
Personnel should structure all electronic communication with recognition of the fact that the content could be monitored and that any electronic communication could be forwarded, intercepted, printed, or stored by others.
ClickUp reserves the right, at its discretion, to review personnel’s files or electronic communications to the extent necessary to ensure all electronic media and services are used in compliance with all applicable laws and regulations as well as corporate policies.
ClickUp reserves the right to audit networks and systems on a periodic basis to ensure compliance with this policy. For security and network maintenance purposes, authorized individuals within ClickUp may monitor equipment, systems and network traffic at any time.
Background checks are conducted on all employees prior to their start date. The consequences of problematic background check results may range from a limitation of security privileges, to revocation of employment offer, to termination.
The security team maintains a company-wide security awareness program delivered to all personnel at least annually. The program covers security awareness, policies, processes, and training to ensure that personnel are sufficiently informed to meet their obligations. Those most responsible for maintaining security at ClickUp, including the security team itself as well as key engineering/operations staff, undergo more technical continuing education.
In the case of personnel termination or resignation, the security team coordinates with human resources to implement a standardized separation process to ensure that all accounts, credentials, and access of outgoing employees are reliably disabled.
Access to ClickUp offices is mediated by an electronic control system that provides for identity-aware
entrance, programmable control over access time of day, and audits of use. All doors shall remain locked at all
times under normal business conditions. The security team may provide approval to unlock doors for short periods
of time in order to accommodate extenuating physical access needs.
Internet-based security cameras are positioned to record time-stamped video of ingress/egress, which are stored off-site.
Internet access shall be provided to devices via wired ethernet and WPA2 wifi. Networking switches and routers shall be placed in a locked networking closet with only the security team having access. ClickUp executives and the security team may grant access to the networking closet to individuals on a case-by-case and as-needed basis. A network firewall that blocks all WAN-sourced traffic shall be put in place. WAN-accessible network services shall not be hosted within the office environment.
How does ClickUp define, control, and maintain user identity and permissions for personnel?
Each individual having access to any ClickUp-controlled system does so via a G Suite user account denoting their system identity. Such user accounts are required to have a unique username, strong password of at least 8 characters, and two-factor authentication (2FA) mechanism.
Logins by personnel may originate only from ClickUp-managed devices. Authentication is performed by Google’s account management system, details of which can be found at https://gsuite.google.com/security. ClickUp leverages G Suite’s facilities of detecting malicious authentication attempts. Repeated failed attempts to authenticate may result in the offending user account being locked or revoked.
Whenever available, third-party systems must be configured to delegate authentication to ClickUp’s G Suite account authentication system (described above) thereby consolidating authentication controls into a single user account system that is centrally managed by the security team.
User accounts are revoked (that is, disabled but not deleted) immediately upon personnel separation. As a further precaution, all user accounts are audited at least quarterly, and any inactive user accounts are revoked.
ClickUp adheres to the principle of least privilege, and every action attempted by a user account is subject to access control checks.
ClickUp employs a role-based access control (RBAC) model utilizing Google-supplied facilities such as organizational units, user accounts, user groups, and sharing controls.
ClickUp may require use of a specified web browser(s) for normal business use and for access to corporate data such as email. For certain specified roles such as software development and web design, job activities beyond those mentioned above necessitate the use of a variety of browsers, and these roles may do so as needed for those activities.
Any browser that is allowed to access corporate data such as email is subject to a whitelist-based restriction on the which browser extensions can be installed.
Access to administrative operations is strictly limited to security team members and further restricted still as a function of tenure and the principle of least privilege.
Access control policies are reviewed regularly with the goal of reducing or refining access whenever possible. Changes in job function by personnel trigger an access review as well.
Upon termination of personnel, whether voluntary or involuntary, the security team will follow ClickUp’s personnel exit procedure, which includes revocation of the associated user account and reclamation of company-owned devices, office keys or access cards, and all other corporate equipment and property prior to the final day of employment.
How does ClickUp build, adopt, configure, and maintain technology to fulfill its security intentions?
ClickUp stores source code and configuration files in private GitHub repositories. The security and development teams conduct code reviews and execute a static code analysis tools on every code commit. Reviewers shall check for compliance with ClickUp’s conventions and style, potential bugs, potential performance issues, and that the commit is bounded to only its intended purpose.
Security reviews shall be conducted on every code commit to security-sensitive modules. Such modules include those that pertain directly to authentication, authorization, access control, auditing, and encryption.
All major pieces of incorporated open source software libraries and tools shall be reviewed for robustness, stability, performance, security, and maintainability.
The security and development teams shall establish and adhere to a formal software release process.
The ClickUp security and development teams shall document the configuration of all adopted systems and services, whether hosted by ClickUp or are third party hosted. Industry best practices and vendor-specific guidance shall be identified and incorporated into system configurations. All configurations shall be reviewed on at least an annual basis. Any changes to configurations must be approved by appointed individuals and documented in a timely fashion.
System configurations must address the following controls in a risk-based fashion and in accordance with the remainder of this policy:
For every third-party service that ClickUp adopts, the security team shall review the service and vendor, on an annual basis, to gain assurance that their security posture is consistent with ClickUp’s for the type and sensitivity of data the service will store.
How does ClickUp manage data classifications and data processing?
ClickUp maintains the following classes and processing rules of customer data. For each data class, the ClickUp security and development teams must provision and dedicate specific information systems in Amazon Web Services to store and process data of that class, and only data of that class, unless otherwise explicitly stated throughout Section 5. For all classes of customer data, the corresponding systems may store and process data items needed to keep each customer’s data properly segmented, such as ClickUp customer identifiers.
Customer User Account Data - This is data pertaining to login accounts for the www.clickup.com customer web interface, used by ClickUp customer agents. This data shall be encrypted-at-rest so as to protect the data in the event of unauthorized access attempts. User account credentials shall be hashed in such a manner that the plaintext passwords cannot be recovered.
Customer Contact Data - This is contact data about ClickUp customers and customer agents.
Customer Preferences Data - This is data pertaining to the customer-specific preferences and configurations of the ClickUp service made by customer agents.
Customer Recorded Data - This is data that the ClickUp service collects during session recording. The ClickUp security and development teams must provision specific systems within Amazon Web Services to store and process this class of data. This data shall be encrypted-at-rest so as to protect the data in the event of unauthorized access attempts.
Customer Event Transaction Metadata - This is metadata about transactions conducted on all other classes of customer data. This includes customer organization and user identifiers, standard syslog data pertaining to customer users, and instances of Customer Contact Data and Customer Preferences Data. This class does not include Customer Recorded Data.
Customer Contact Data, Customer Preferences Data, and Customer Event Transaction Metadata may be stored and processed in systems hosted in environments other than Amazon Web Services, as approved by the security team.
ClickUp employees may access Customer Data only under the following conditions.
ClickUp provides web user interfaces (UIs), application programming interfaces (APIs), and data export facilities to provide customers access to their data.
The security team in conjunction with executive management may approve emergency exceptions to any of the above rules, in response to security incidents, service outages, or significant changes to the ClickUp operating environment, when it is deemed that such exceptions will benefit and protect the security and mission of ClickUp, ClickUp customers, and visitors of ClickUp customers’ websites.
How does ClickUp detect, and respond to vulnerabilities and security incidents?
The ClickUp security and development teams shall use all of the following measures to detect vulnerabilities that may arise in ClickUp’s information systems.
The ClickUp security team shall evaluate the severity of every detected vulnerability in terms of the likelihood and potential impact of an exploit, and shall develop mitigation strategies and schedules accordingly. Suitable mitigations include complete remediation or implementing compensating controls.
The ClickUp security team shall use all of the following measures to detect security incidents.
The ClickUp security team shall make a determination of whether every indicator is representative of an actual security incident. The severity, scope, and root cause of every incident shall be evaluated, and every incident shall be resolved in a manner and timeframe commensurate with the severity and scope.
In the event that a data breach affecting a customer has been detected, ClickUp will maintain communication with the customer about the severity, scope, root cause, and resolution of the breach.
How will ClickUp prevent and recover from events that could interfere with expected operations?
ClickUp services hosted in AWS shall be configured in such a manner so as to withstand long-term outages to an availability zone. Controls such as automated replication or automated data recovery processes may be used to achieve this desired level of availability.