DATA PROCESSING ADDENDUM
Effective Date: 11/19/2026
This Data Processing Addendum (this “DPA”) forms part of the Terms of Service, Master Services Agreement or other principal agreement (the “Service Agreement”) between the customer of Vendor (“Customer”) and HoneyHive Inc., a Delaware corporation (“Vendor”, “HoneyHive” or “HoneyHive AI”). Customer and Vendor may be referred to herein together as the “Parties”, and each may be referred to herein as a “Party”. This DPA is hereby incorporated into, and subject to, the terms of the Service Agreement. With respect to provisions regarding Processing of Customer Data (each as defined below), in the event of a conflict between the terms of this DPA and the terms of the Service Agreement, the terms of this DPA shall control. For good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, Customer and Vendor hereby agree as follows:
1. Definitions.
1.1 “Applicable Laws” means, collectively, all now existing or hereinafter enacted or amended laws, rules, regulations, and/or sanctions programs applicable to a Party’s performance hereunder and/or obligations with respect to data protection.
1.2 “CCPA” means the California Consumer Privacy Act of 2018 (Title 1.81.5 of the Civil Code of the State of California), together with all effective regulations adopted thereunder (in each case, as amended from time to time).
1.3 “Customer Data” means all information, data, content and other materials, in any form or medium, that is submitted, posted, collected, transmitted or otherwise provided by or on behalf of Customer through the Services.
1.4 “Customer Personal Data” means Customer Data that is Personal Data processed by Vendor on behalf of Customer in the provision of the Services under the Service Agreement.
1.5 “Controller” means (i) under and in the context of European Data Protection Law, the data “controller” (as defined by GDPR), (ii) under and in the context of CCPA, the “business” or “third party” (each, as defined by CCPA), and (iii) under and in the context of any other privacy or data protection law, rule, or regulation applicable to a Party’s performance hereunder, a “controller”, “business”, or corresponding term denoting a substantially similar definition, role, and obligations under such law, rule or regulation.
1.6 “EU GDPR” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (and each successor regulation, directive or other text of the foregoing, in each case as amended from time to time).
1.7 “European Data Protection Law” means each of EU GDPR, UK GDPR, and the Federal Data Protection Act of 19 June 1992 (Switzerland) (as the same may be superseded by the Swiss Data Protection Act 2020 and as amended from time to time).
1.8 “GDPR” means, as applicable, (i) the EU GDPR and/or (ii) the UK GDPR.
1.9 “Personal Data” means any information that constitutes (a) “personal information” (as defined by, and in the context of, CCPA), (b) “personal data” (as defined by, and in the context of, European Data Protection Law), and/or (c) “personal data,” “personal information,” or other term denoting a substantially similar definition and obligations under, and in the context of, any other Applicable Laws.
1.10 “Process” means any operation or set of computer operations performed on Personal Data, including, but not limited to, collection, recording, organization, structuring, storage, access, adaptation, alteration, retrieval, consultation, use, transfer, transmit, sale, rental, disclosure, dissemination, making available, alignment, combination, deletion, erasure, or destruction.
1.11 “Processor” means (i) under and in the context of European Data Protection Law, the data “processor” (as defined by GDPR), (ii) under and in the context of CCPA, a “service provider” (as defined by CCPA), and (iii) under and in the context of any other privacy or data protection law, rule, or regulation applicable to a Party’s performance hereunder, a “processor”, “service provider”, or corresponding term denoting a substantially similar definition, role, and obligations under such law, rule or regulation.
1.12 “Security Incident” means (i) any accidental, unauthorized, or unlawful destruction, loss, alteration, disclosure of, or access to, Customer Personal Data or (ii) any other event that constitutes a “security breach”, “personal data breach”, or substantially similar term with respect to Customer Personal Data under Applicable Laws.
1.13 “Services” means, collectively, the products and/or services provided by Vendor to Customer under the Service Agreement.
1.14 “Sub-Processor” means a contractor, subcontractor, consultant, third-party service provider, or agent engaged by Vendor for further Processing of Customer Personal Data.
1.15 “UK GDPR” has the meaning ascribed thereto in section 3(10) (as supplemented by section 205(4)) of the UK Data Protection Act 2018 (as amended from time to time).
2. Data Processing Obligations.
2.1 General.
(a) Each Party shall comply with its obligations relating to Personal Data under this DPA and under Applicable Laws at its own cost. With respect to Customer Personal Data, (i) Customer is a Controller and (ii) Vendor is a Processor that Processes Customer Personal Data only upon the instructions of Customer, including, without limitation, in accordance with the applicable Service Agreement, this DPA, and any other documented instructions provided by Customer. Notwithstanding the foregoing, Vendor may Process Customer Personal Data as required by Applicable Laws. Schedule I sets forth specific details regarding Vendor’s processing of Customer Personal Data.
(b) With regard to Vendor employees and contractors engaged in Processing Customer Personal Data, Vendor shall ensure that such employees and contractors are informed of the confidential nature of the Customer Personal Data and are subject to appropriate confidentiality obligations sufficient to comply with the terms of the Service Agreement and this DPA.
(c) Customer will have sole responsibility for the accuracy, quality, and legality of Customer Personal Data and the means by which Customer obtains the Customer Personal Data, including, without limitation, obtaining appropriate consent to collect the Customer Personal Data and share such data with Vendor in accordance with Applicable Laws.
2.2 Standard Contractual Clauses. If Vendor Processes Customer Personal Data relating to an EEA, United Kingdom, or Switzerland data subject (including, without limitation, the transfer of such Customer Personal Data from the EEA, United Kingdom, or Switzerland to a third country not providing an adequate level of protection) outside of the EEA, United Kingdom, and Switzerland, the Processing will be further governed by Schedule II to this DPA (together with all Appendices and Annexes thereto, and as the same may be amended, supplemented, or otherwise modified from time to time, “Personal Data SCCs”), which is incorporated by reference into this DPA solely with respect to Customer Personal Data relating to EEA, United Kingdom and/or Switzerland data subjects. If there is any conflict between (x) the terms and conditions of either this DPA or the Service Agreement, on the one hand, and (y) the terms and conditions of the Personal Data SCCs, on the other hand, then, with respect to Customer Personal Data relating to an EEA, United Kingdom and/or Switzerland data subject(s), the terms and conditions of the Personal Data SCCs will prevail and control. Vendor may only transfer Customer Personal Data relating to an EEA, United Kingdom, or Switzerland data subject outside the EEA, United Kingdom, and Switzerland in compliance with Applicable Laws and the Personal Data SCCs.
2.3 CCPA. With respect to Customer Personal Data relating to a California “consumer” or “household” (each as defined by CCPA) (“CCPA Personal Data”):
(a) Customer will be disclosing such CCPA Personal Data under the Service Agreement to Vendor for a “business purpose” (as defined by CCPA), and Vendor shall Process such CCPA Personal Data solely on behalf of Customer and only as necessary to perform such business purpose for Customer; and
(b) Vendor shall not: (i) “sell” or “share” (each as defined by CCPA) CCPA Personal Data; (ii) retain, use, or disclose CCPA Personal Data (x) for any purpose (including a “commercial purpose” (as defined by CCPA)) other than for the specific purpose of performing for Customer the services specified in the Service Agreement or (y) outside of the direct business relationship between Vendor and Customer; or (iii) combine the Customer Personal Data with Personal Data that Vendor collects or receives from another source (except in the performance of any “business purpose”).
2.4 Changes in Applicable Laws. If, due to any change in Applicable Laws, a Party reasonably believes that (a) Vendor ceases to be able to provide the Services in whole or in part (e.g., with respect to a particular jurisdiction) and/or Customer ceases to be able to use the Services in whole or in part under the then-current terms and conditions of the Service Agreement and this DPA, each Party may terminate the Service Agreement (in whole or, if reasonably practicable, in part).
3. Security. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Vendor will implement and maintain appropriate technical and organizational measures to ensure a level of security for the Customer Personal Data appropriate to the risks. In assessing the appropriate level of security, account shall be taken in particular of the risks that are presented by Processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data transmitted, stored or otherwise processed. Such measures will include reasonable administrative, physical, and technical security controls (including those required by Applicable Laws) that prevent the collection, use, disclosure, or access to Customer Personal Data that the Service Agreement does not expressly authorize, including maintaining a comprehensive information security program that safeguards Customer Personal Data. These security measures include the measures set forth in Schedule III.
4. Supplementary Measures and Safeguards.
4.1 Assistance. Vendor shall assist Customer to ensure compliance with Applicable Laws in connection with the Processing of Customer Personal Data.
4.2 Orders. Vendor shall notify Customer in writing of any subpoena or other judicial or administrative order by a government authority or proceeding seeking access to or disclosure of Customer Personal Data. Customer shall have the right to defend such action in lieu of and/or on behalf of Vendor. Customer may, if it so chooses, seek a protective order. Vendor shall reasonably cooperate with Customer in such defense.
5. Notifications.
5.1 Security Incidents. Vendor has and will maintain a security incident response plan that includes procedures to be followed in the event of a Security Incident. Vendor will provide Customer with written notice promptly after discovering a Security Incident (including those affecting Vendor or its Sub-Processors), including any known information that Customer is required by Applicable Laws to provide to an applicable regulatory agency or to the individuals whose Personal Data was involved in the Security Incident.
5.2 Data Subject Requests. Vendor shall (i) promptly notify Customer about any request under Applicable Law(s) with respect to Customer Personal Data received from or on behalf of the applicable data subject and (ii) cooperate as required by Applicable Law(s) with Customer’s reasonable requests in connection with data subject requests with respect to Customer Personal Data. Vendor shall assist Customer, through appropriate technical and organizational measures, to fulfill its obligations with respect to requests of data subjects seeking to exercise rights under Applicable Law with respect to Customer Personal Data.
6. Sub-Processors.
6.1 Vendor shall not have Customer Personal Data Processed by a Sub-Processor unless such Sub-Processor is bound by a written agreement with Vendor that includes data protection obligations at least as protective as those contained in this DPA and the Service Agreement and that meet the requirements of Applicable Laws. Vendor is and shall remain fully liable to Customer for any failure by any Sub-Processor to fulfill Vendor’s data protection obligations under Applicable Laws.
6.2 Vendor’s list of all Sub-Processors who access Customer Personal Data is available at Annex III to Exhibit A of Schedule II (the “Sub-Processor List”). Customer authorizes and instructs Vendor to engage the Sub-Processors listed in the Sub-Processor List. Vendor will notify Customer of any changes to the Sub-Processors listed on the Sub-Processor List and grant Customer the opportunity to object to such change. Upon Customer’s request, Vendor will provide all information necessary to demonstrate that the Sub-Processors will meet all requirements pursuant to Section 6.1. If Customer objects to any Sub-Processor, Vendor can choose to either not engage the Sub-Processor or to terminate Customer’s Service Agreement with thirty (30) days’ prior written notice.
7. Deletion. Vendor shall, at the choice of Customer: (i) delete or return all Customer Data to Customer after such Customer Data is no longer necessary for the provision of the Services, and (ii) delete existing copies of such Customer Data.
8. Documentation; Audit.
8.1 Vendor shall, upon Customer’s request, provide Customer (a) comprehensive documentation of Vendor’s technical and organizational security measures, (b) any and all third-party audits and certifications available with respect to such security measures, and (c) all other information reasonably necessary to demonstrate compliance with the Vendor’s obligations under this DPA and/or under Applicable Laws. Where (a) – (c) of this section are not sufficient for compliance with Applicable Laws, then upon reasonable notice and appropriate confidentiality agreements, Vendor shall cooperate with assessments, audits, or other steps performed by or on behalf of Customer at Customer’s sole expense and in a manner that is minimally disruptive to Vendor’s business that are necessary to confirm that Vendor is processing Customer Personal Data in a manner consistent with this DPA.
9. Term; Termination. This DPA shall remain in effect until (a) the Service Agreement has terminated and (b) all obligations that Vendor has under the Service Agreement and under Applicable Laws with respect to Customer Personal Data, and all rights that Customer has under the Service Agreement and under Applicable Laws with respect to Customer Personal Data, have terminated. Notwithstanding termination of this DPA, any provisions hereof that by their nature are intended to survive, shall survive termination.
10. Limitation of Liability. NOTWITHSTANDING ANYTHING STATED IN THE SERVICE AGREEMENT, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER VENDOR NOR CUSTOMER SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES (INCLUDING DAMAGES FOR LOSS OF PROFITS, GOODWILL, USE, OR DATA) ARISING OUT OF OR IN CONNECTION WITH THIS DPA, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY AND WHETHER OR NOT A PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL EITHER PARTY’S CUMULATIVE LIABILITY ARISING OUT OF OR RELATED TO THIS DPA EXCEED THE SUM OF THE FEES PAID OR PAYABLE BY CUSTOMER TO VENDOR UNDER THE SERVICE AGREEMENT DURING THE ONE YEAR PERIOD IMMEDIATELY PRECEDING THE DATE THE CLAIM FOR SUCH DAMAGES AROSE, EXCEPT TO THE EXTENT SUCH LIMITATION IS NOT PERMITTED BY APPLICABLE LAW. THE FOREGOING LIMITATIONS OF LIABILITY SHALL NOT APPLY TO LIABILITY ARISING FROM WILLFUL MISCONDUCT OR BREACHES OF APPLICABLE LAW.
11. Miscellaneous.
11.1 Any notice made pursuant to this DPA will be in writing and will be deemed delivered on (a) the date of delivery if delivered personally, (b) five (5) calendar days (or upon written confirmed receipt) after mailing if duly deposited in registered or certified mail or express commercial carrier, or (c) one (1) calendar day (or upon written confirmed receipt) after being sent by email, addressed to Customer at the address or email address on record with Vendor, or addressed to Vendor at the address or email address designated below, or to such other address or email address as may be hereafter designated by either Party:
By email to: support@honeyhive.ai
By mail to:
HoneyHive Inc.524 Broadway, 11th Floor
New York, NY 10012
11.2 This DPA shall be governed by and construed in accordance with governing law and jurisdiction provisions in the Service Agreement, unless required otherwise by Applicable Laws.
11.3 Neither Party may assign or transfer any part of this DPA without the written consent of the other Party; provided, however, that this DPA, collectively with the Service Agreement, may be assigned without the other Party’s written consent by either Party to a person or entity who acquires, by sale, merger or otherwise, all or substantially all of such assigning Party’s assets, stock or business. Subject to the foregoing, this DPA shall bind and inure to the benefit of the Parties, their respective successors and permitted assigns. Any attempted assignment in violation of this section shall be void and of no effect.
[Signature Page Follows]
IN WITNESS WHEREOF, the Parties have executed this Data Processing Addendum as of the Effective Date.
| HONEYHIVE INC. | [CUSTOMER NAME] |
|---|---|
| By: _______________________________ | By: _______________________________ |
| Name: | Name: |
| Title: | Title: |
SCHEDULE I
Details of Customer Personal Data
Nature and Purpose of Processing
To provide the Services pursuant to the Service Agreement.
Categories of Personal Data Subject to Processing
• First name, last name, email address, company/employer name, role.
Categories of Data Subjects Whose Personal Data is Transferred
• Individual users, an entity customer’s employees and personnel, covered third parties.
Frequency of transfer
Continuous basis for the duration of the Services pursuant to the Service Agreement.
Duration of Processing
For the duration of the Services pursuant to the Service Agreement.
Period for which Personal Data will be retained
As long as necessary to provide the Services pursuant to the Service Agreement.
SCHEDULE II
EU SCCs
1. Definitions
a. “EU SCCs” means the Standard Contractual Clauses issued pursuant to Commission Implementing Decision (EU) 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, available at http://data.europa.eu/eli/dec_impl/2021/914/oj and completed as described in this Schedule II.
b. “UK SCCs” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, available as of the DPA Effective Date at https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/appropriate-safeguards/what-are-standard-data-protection-clauses-the-uk-idta-and-the-addendum/ and completed as described in this Schedule II.
2. With respect to Customer Personal Data transferred from the European Economic Area, the EU SCCs will apply and form part of this Schedule II, unless the European Commission issues updates to the EU SCCs, in which case the updated EU SCCs will control. Undefined capitalized terms used in this provision will have the meanings given to them (or their functional equivalents) in the definitions in the EU SCCs. For purposes of the EU SCCs, they will be deemed completed as follows:
a. Because Customer is a Controller and Vendor is a Processor of the Customer Personal Data, Module 2 applies.
b. Clause 7 (the optional docking clause) is not included.
c. Under Clause 11 (Redress), the optional dispute resolution body language is not included.
d. Under Clause 17 (Governing law), the Parties select Option 1 (the law of an EU Member State that allows for third-party beneficiary rights). The Parties select the law of Ireland.
e. Under Clause 18 (Choice of forum and jurisdiction), the Parties select the courts of Ireland.
f. Annexes I, II and III of the EU SCCs are set forth in Exhibit A to this Schedule II.
g. By entering into this DPA, the Parties are deemed to be signing the EU SCCs.
3. With respect to Customer Personal Data transferred from the United Kingdom for which the law of the United Kingdom (and not the law in any European Economic Area jurisdiction) governs the international nature of the transfer, the UK SCCs form part of this Schedule II and take precedence over the rest of this Schedule II as set forth in the UK SCCs, unless the United Kingdom issues updates to the UK SCCs, in which case the updated UK SCCs will control. Undefined capitalized terms used in this provision will have the meanings given to them (or their functional equivalents) in the definitions in the UK SCCs. For purposes of the UK SCCs, they will be deemed completed as follows:
a. Table 1 of the UK SCCs:
i. The Parties’ details are the Parties and their affiliates to the extent any of them is involved in such transfer, including those set forth in Exhibit A.
ii. The Key Contacts are the contacts set forth in Exhibit A.
b. Table 2 of the UK SCCs: The Approved EU SCCs referenced in Table 2 are the EU SCCs as executed by the Parties pursuant to this Schedule II.
c. Table 3 of the UK SCCs: Annex 1A, 1B, II and III are set forth in Exhibit A.
d. Table 4 of the UK SCCs: Either party may terminate the Service Agreement as set forth in Section 19 of the UK SCCs.
e. By entering into the DPA, the Parties are deemed to be signing the UK SCCs and their applicable Tables and Appendix Information.
4. With respect to Customer Personal Data transferred from Switzerland for which Swiss law (and not the law in any European Economic Area jurisdiction) governs the international nature of the transfer, the EU SCCs will apply and will be deemed to have the following differences to the extent required by the Swiss Federal Act on Data Protection (“FADP”):
a. References to the GDPR in the EU SCCs are to be understood as references to the FADP insofar as the data transfers are subject exclusively to the FADP and not to the GDPR.
b. The term “member state” in the EU SCCs will not be interpreted in such a way as to exclude data subjects in Switzerland from the possibility of suing for their rights in their place of habitual residence (Switzerland) in accordance with Clause 18(c) of the EU SCCs.
c. References to Personal Data in the EU SCCs also refer to data about identifiable legal entities until the entry into force of revisions to the FADP that eliminate this broader scope.
d. Under Annex I(C) of the EU SCCs (Competent supervisory authority): where the transfer is subject exclusively to the FADP and not the GDPR, the supervisory authority is the Swiss Federal Data Protection and Information Commissioner, and where the transfer is subject to both the FADP and the GDPR, the supervisory authority is the Swiss Federal Data Protection and Information Commissioner insofar as the transfer is governed by the FADP, and the supervisory authority is as set forth in the EU SCCs insofar as the transfer is governed by the GDPR.
EXHIBIT A TO SCHEDULE II
ANNEX I
A. LIST OF PARTIES
Data exporter(s):
Name: Entity identified as “Customer” in the DPA.
Address: See the Service Agreement.
Contact person’s name, position and contact details: See the Service Agreement.
Activities relevant to the data transferred under these Clauses: To receive the Services (as defined in the DPA).
Role (controller/processor): Controller.
Data importer(s):
Name: HoneyHive Inc. (“Vendor”)
Address: 77 Sands Street, Suite 7014, Floor 6, Brooklyn, NY 11201
Contact person’s name, position and contact details:
Name: Dhruv Singh
Role: Data Protection Officer
Address: 77 Sands Street, Suite 7014, Floor 6, Brooklyn, NY 11201
Activities relevant to the data transferred under these Clauses: To provide Customer with the Services (as defined in the DPA).
Role (controller/processor): Processor.
B. DESCRIPTION OF TRANSFER
Categories of data subjects whose personal data is transferred
See Schedule I
Categories of personal data transferred
See Schedule I
Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.
The parties do not anticipate that Vendor will process sensitive data pursuant to the Service Agreement, except to the extent the parties have entered into a separate written agreement (such as a business associate agreement and/or a customer-specific data processing addendum) expressly addressing Vendor's processing of such sensitive data on Customer's behalf.
The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis).
See Schedule I
Nature of the processing
See Schedule I
Purpose(s) of the data transfer and further processing
See Schedule I
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period
See Schedule I
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing
To provide the Services pursuant to the Service Agreement.
C. COMPETENT SUPERVISORY AUTHORITY
Identify the competent supervisory authority/ies in accordance with Clause 13
The supervisory authority of Ireland.
ANNEX II
TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
See Schedule III
ANNEX III
LIST OF SUB-PROCESSORS
The controller has authorised the use of the following sub-processors:
Please see: https://trust.honeyhive.ai
SCHEDULE III
Security Measures
INTRODUCTION
HoneyHive AI maintains an information security program designed to safeguard its systems, data, and Customer Data. This schedule describes the information security program and security standards that HoneyHive AI maintains with respect to its Services and handling of Customer Data. Capitalized terms not defined in this schedule have the meanings given in the DPA or the Service Agreement.
HoneyHive AI's information security program is supported by a comprehensive set of internal policies and procedures. These policies establish the framework, objectives, and responsibilities for information security activities and are regularly reviewed and updated.
To learn more about HoneyHive’s technical and organizational security measures to protect Customer Data, see the HoneyHive Trust Portal at https://trust.honeyhive.ai.
SECURITY MEASURES
HoneyHive AI implements and maintains the following technical and organizational measures to ensure the security of Customer Data and its systems:
Identity, Authentication, and Authorization Controls
HoneyHive AI maintains industry standard practices for authenticating and authorizing internal employee and customer access, including the following measures:
• Individual User Access: All user access is assigned to individual employees or other third parties with a clearly labelled full name.
• Authentication: Access is authenticated on all systems using strong password settings, multi-factor authentication (MFA), and/or single sign-on (SSO) where possible.
• Least Privilege: Access to systems and data follows the concept of least privilege, granted only for a legitimate business need and for the period required, restricted to the minimum level necessary for the role.
• Password Management: An approved enterprise password manager is required for employees to support quality passwords and secure handling of authentication information. MFA is applied to the password manager.
• Strong Passwords: Minimum password requirements include minimum 9 characters, maximum age less than 180 days, complexity (uppercase, lowercase, numbers, symbol), lockout threshold (6 invalid attempts), and lockout duration (until unlocked by admin or security questions).
• Privileged Access: Privileged access roles are restricted to the fewest number of employees possible while maintaining business continuity.
• Access Approval: User access requires approval prior to provisioning, documented through onboarding checklists, tickets, or other forms.
• Access Revocation: Access is removed within 24 hours upon termination or when no longer required, documented for audit trail purposes.
• Quarterly Access Review: Access to all systems is reviewed at least quarterly to ensure continued legitimate business need and identify provisioning/revocation failures.
• Authentication Secrets Management: Authentication secrets are kept secret, not shared or stored insecurely, and default passwords are modified upon first use. Passwords for system access are only stored on approved company devices.
• Secure Logon Procedures: Only encrypted (WPA2) Wi-Fi connections are used for business purposes on company devices; public networks are not used unless approved.
Cloud Infrastructure and Network Security
HoneyHive AI utilizes cloud-hosted networking, compute, and database components on Amazon Web Services (AWS) and maintains industry standard practices for securing this infrastructure:
• Segregated Environments: Separate development, testing, and production environments are maintained.
• Network Firewalls: Network firewalls are used at external connectivity points and configured for least-privilege access with a default deny policy.
• Web Application Firewalls (WAFs): WAFs are implemented to secure internet traffic against bots and DDoS attacks.
• Restricted Firewall Access: Access to firewall configurations is restricted to authorized administrators.
• Firewall Change Alerts: Firewall changes trigger automated alerts.
• Annual Firewall Review: Configuration settings for firewalls are reviewed at least annually.
• Data-in-Transit Encryption: Encryption is enforced for all network connections to protect data-in-transit.
• Security Hardening: Security hardening configuration requirements for critical infrastructure are defined and reviewed annually to verify adherence to minimum settings.
• System Monitoring: System monitoring software is used to monitor and log system events.
• Threat Detection: SIEM software is used to identify and alert for potential network threats.
• Network Traffic Alerts: Alerts are configured for suspicious network traffic and events.
• Security Monitoring Software: Security and compliance monitoring software (Drata) is used to monitor infrastructure and network security compliance.
System and Workstation Control
HoneyHive AI maintains industry standard practices for securing corporate systems and employee workstations:
• Endpoint Management: Endpoint management is implemented for corporate workstations and mobile devices.
• Security Configurations: Automatic application of security configurations to workstations.
• Patch Management: Mandatory patch management is enforced.
• Security Logs: Appropriate security logs are maintained.
• Hard Disk Encryption: Hard disk encryption is required on all corporate workstations.
• Device Firewalls: Device firewalls are required.
• Data Prohibitions: Sensitive data is prohibited from being stored on end user devices.
• Approved Devices/Services: HoneyHive AI system assets and other devices are used for intended business purposes only. Only approved cloud services can be used.
Data Security Measures
HoneyHive AI maintains industry standard practices for protecting data confidentiality, integrity, and availability:
• Data Classification: Data is classified (Restricted, PII, Confidential, Internal, Public) based on sensitivity and risk, guiding protection requirements.
• Secure Storage: All sensitive data is stored in approved and secure storage locations.
• Data-at-Rest Encryption: Encryption is applied to all production databases holding sensitive data. Data handled and stored by sub-processors is required to be encrypted at-rest.
• Key Management: Secure and controlled key generation, limited access, storage, backup, and periodic rotation of cryptographic keys are managed using AWS Key Management Service (KMS).
• Data Minimization: Private and confidential data collection and storage from customers is minimized to where there is a legitimate business need.
• Data Retention and Disposal: Data retention periods and triggers for disposal are defined based on regulatory, customer, and compliance requirements. Data is effectively erased, destroyed, or left unreadable upon disposal of assets.
• Archiving: Information is archived when not actively used but required for record keeping/compliance, retaining access restrictions, security, and backups.
• Logging of Data Activities: Log records are created for attempts to create, read, update, or delete sensitive or confidential authentication information. Audit trail for all data access requests for production datastores.
Availability Controls
HoneyHive AI maintains measures to ensure the continued availability of its Services:
• Backup and Restore: Automated backup schedules are run for regular snapshots to support data recoverability. Key information and documents are backed up regularly to separate and secure locations. Steps are established to restore production databases and recover critical system components.
• Disaster Recovery Strategy: A multi-region disaster recovery strategy is used, including multi-availability zones for failover and backup environments. Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) are defined (e.g., 1 hour for AWS Infrastructure and HoneyHive AI system availability).
• Restoration Testing: Restoration tests are conducted at least annually to ensure effective recoverability of production databases.
• Business Continuity Plan (BCP): A BCP is established and documented to respond to major adverse events threatening business function continuity (natural disasters, security breaches, etc.), including identifying continuity events and high-level response plans.
• Anti-malware: Anti-malware systems are implemented comprehensively.
• Monitoring: Systems are monitored to ensure they are functioning and faults are reported (Sentry, Data Dog). Failures of critical security control systems are detected, alerted, and addressed promptly.
Segregation Control
HoneyHive AI implements measures for separate processing of data collected for different purposes:
• Logical Segregation: Customer Data is logically segregated by organization account using unique identifiers.
• Role-Based Access: Access to data stored for different purposes is restricted according to staff roles and responsibilities.
• Environment Segregation: Separate change environments (development, testing, production) are maintained to ensure changes are tested and approved before migrating to production.
• Segregation of Duties: Segregation of incompatible duties is applied, particularly between software development and approval roles, ensuring independent review and approval of changes.
Risk Management
HoneyHive AI maintains a program for detecting and managing cybersecurity risks, including the following measures:
• Risk Management Framework: Defines the methodology for identifying, assessing, treating, monitoring, and reporting risks.
• Risk Assessment Process: A cyclical approach involving quarterly reviews by the Management Team, reporting key risks to the Board. Risks are evaluated based on likelihood, impact, and overall risk rating using defined criteria.
• Threat Modeling: Threat modeling is performed to document and triage sources of security risk.
• Vulnerability Management Program: Includes systematic identification, assessment, logging, and resolution of technical vulnerabilities before exploitation. Vulnerabilities are assessed based on likelihood and impact (using OWASP methodology) to determine resolution timeframes (e.g., Critical: 1 day, High: 3 days, Medium: 7 days, Low: 30 days).
• Penetration Testing: Independent penetration testing is conducted at least annually by a qualified third party. Summary details of tests and remediation status are available upon request.
• Static Code Analysis: Performed on code repositories to identify common, known vulnerabilities.
• Network/Web Application Scanning: Vulnerability scanning is performed on networks and live web applications.
• Risk Treatment: Risk treatment actions are devised for risks rated Medium or above, based on assessment.
• Monitoring and Reporting: Provides feedback into the risk process; operational incidents, complaints, and events feed into assessments.
• Vendor Governance Framework: Manages third-party security risks; includes a formal vendor assessment process, review of accreditations, business dependency assessment, and a Vendor Register tracking material vendors and their risks. Written contracts ensure vendor safeguards.
Personnel Security
HoneyHive AI maintains practices related to personnel security:
• Security Awareness Training: Mandatory annual security awareness training is provided to all employees.
• Policy Adherence: All employees are responsible for reading, acknowledging, and adhering to security policies, including the Code of Conduct and Acceptable Use Policy, and reporting non-compliance.
• Defined Responsibilities: Roles and responsibilities related to information security are clearly defined and assigned across all policies.
Physical Security
HoneyHive AI operates a modern remote-workforce environment and provides direction to employees to facilitate employee security behaviors as there are no permanent physical locations storing sensitive assets under HoneyHive AI's responsibility:
• Remote Workforce Security: Information assets, including endpoint devices, are subject to the Acceptable Use Policy requirements for maintaining appropriate security protections at remote-working locations.
• Employee Behaviors: Direction is provided to employees to facilitate their exercise of appropriate behaviors, such as not printing confidential information or storing it on unsecured devices, reporting device loss/theft, and applying screen locks.
Security Incident Response
HoneyHive AI maintains a security incident response plan for responding to and resolving events impacting the Services or Customer Data:
• Incident Management Policy: Defines the approach for consistent and effective management of incidents, including classification based on Severity (Urgency + Impact).
• Incident Response Team (ERT): Mobilized for major incidents; responsible for handling, communication, and timely resolution. Contacts and roles are defined.
• Incident Identification: Incidents are identified through live system testing, system monitoring tools, system log reviews, employee reporting channels, and external reporting channels.
• Centralized Logging: Incidents are centrally logged for oversight, monitoring, resolution, and retrospective analysis. System logs are aggregated for detection and response.
• Incident Handling Steps: Follows a defined process including Preparation, Identification and Classification, Containment, Eradication, and Recovery.
• Post-Incident Review (PIR): Completed for incidents with a Severity rating of S2 and above to formally assess lessons learned, identify cause/resolution, and improve processes.
• Stakeholder Communications: Defined processes for notifying relevant parties (customers, regulators, internal personnel) about incidents, including documentation of decisions. HoneyHive AI will notify Customer of a Personal Data Breach in accordance with the DPA. Generally available at https://status.honeyhive.ai
• Annual Testing: Incident response plans are tested at least annually, potentially as part of BCP/DR testing, to ensure viability and readiness.
Security Evaluations
HoneyHive AI performs regular security evaluations to assess its controls and compliance:
• Controls Assessment Program: Defines responsibilities and methods for tracking, monitoring, and assessing control activities, ensuring they are appropriate, effective, and documented. Drata is used for compliance automation and continuous monitoring.
• Control Self-Assessments: Conducted annually to verify key controls.
• Internal Audits: Conducted semi-annually to perform independent assessments and testing of key control activities.
• External Audits: Conducted at least annually by a qualified, independent external auditor (including SOC 2 Type II certification audits) to review security practices against recognized standards. Summary details are available upon reasonable request.
• Vulnerability Management Evaluations: Includes assessing identified vulnerabilities, logging them, and reporting on resolution status to management.
• Risk Management Reporting: Key risks and the status of risk treatment plans are reported to management and the Board.
***