{"version":3,"sources":["webpack:///./src/pages/data-processing.tsx","webpack:///./node_modules/@babel/runtime/helpers/esm/objectDestructuringEmpty.js"],"names":["DataProcessingDoc","className","name","content","href","id","target","Privacy","Fragment","_objectDestructuringEmpty","obj","TypeError"],"mappings":"kOAQMA,EAAoB,kBACxB,sBAAKC,UAAU,wCAAf,UACE,eAAC,SAAD,WACE,sBAAMC,KAAK,SAASC,QAAQ,QAC5B,+DACA,sBAAMD,KAAK,cAAcC,QAAQ,QAEnC,0DACA,qSAMA,uBACA,mDACA,+BACE,6BACE,mBAAGC,KAAK,eAAR,2BAEF,6BACE,mBAAGA,KAAK,8BAAR,0CAEF,6BACE,mBAAGA,KAAK,2BAAR,uCAEF,6BACE,mBAAGA,KAAK,YAAR,wBAEF,6BACE,mBAAGA,KAAK,iBAAR,6BAEF,6BACE,mBAAGA,KAAK,uBAAR,mCAEF,6BACE,mBAAGA,KAAK,kBAAR,8BAEF,6BACE,mBAAGA,KAAK,4BAAR,wCAEF,6BACE,mBAAGA,KAAK,gBAAR,4BAEF,6BACE,mBAAGA,KAAK,8BAAR,0CAEF,6BACE,mBAAGA,KAAK,aAAR,yBAEF,6BACE,mBAAGA,KAAK,wBAAR,uCAGJ,uBAEA,sBAAKC,GAAG,cAAcJ,UAAU,uBAAhC,UACE,6CACA,+BACE,uLAKA,mJAIA,2IAIA,+GAIA,8MAKA,0ZAQA,mIAIA,uUAOA,iKAIA,okBAYJ,uBACA,sBAAKI,GAAG,6BAA6BJ,UAAU,uBAA/C,UACE,4DACA,+BACE,mfASA,uYAQA,wVAOA,8UAOA,8pBAcJ,uBACA,sBAAKI,GAAG,0BAA0BJ,UAAU,uBAA5C,UACE,yDACA,+BACE,kQAMA,oTAOA,kWAOA,+OAKA,iVASJ,uBACA,sBAAKI,GAAG,WAAWJ,UAAU,uBAA7B,UACE,0CACA,+BACE,mpBAWE,qBAAIA,UAAU,OAAd,UACE,kFACA,2JAIA,qKAIA,uMAOJ,ibASA,mVAOA,yMAOJ,uBACA,sBAAKI,GAAG,gBAAgBJ,UAAU,uBAAlC,UACE,+CACA,+BACE,kRAKE,mBACEG,KAAK,mFACLE,OAAO,SAFT,yBALF,OAaA,mgBAUA,qZAQA,mSAQJ,uBACA,sBAAKD,GAAG,sBAAsBJ,UAAU,uBAAxC,UACE,qDACA,+BACE,sWAOA,wKAGE,qBAAIA,UAAU,OAAd,UACE,2GAIA,wEAGJ,0SAMA,oUAOA,oQAMA,+PAQJ,uBACA,sBAAKI,GAAG,iBAAiBJ,UAAU,uBAAnC,UACE,gDACA,+BACE,4OAKA,wfAUA,wbAQA,4ZAUJ,uBACA,qBAAKI,GAAG,2BAA2BJ,UAAU,uBAA7C,SACE,4DAEF,qdAUA,uBACA,4KAIA,+BACE,2DACA,6CACA,6CACA,0CACA,2DAEF,uBACA,uMAKA,uBACA,uNAKA,uBACA,8OAKA,+BACE,4EACA,uEACA,mFACA,uIAKF,uBACA,+OAKA,wTAMA,uBACA,qBAAKI,GAAG,eAAeJ,UAAU,uBAAjC,SACE,gDAEF,8bAQA,uBACA,yXAOA,uBACA,oXAOA,uBACA,+SAMA,uBACA,sBAAKI,GAAG,6BAA6BJ,UAAU,uBAA/C,UACE,4DACA,mBAAGA,UAAU,YAAb,0QAMA,+BACE,4UAOA,2NAKA,iWAOA,wVAOA,2NAOJ,uBACA,iLAIA,uBACA,sBAAKI,GAAG,YAAYJ,UAAU,uBAA9B,UACE,2CACA,+BACE,mYAQA,6QAMA,wLAOJ,uBACA,sBAAKI,GAAG,uBAAuBJ,UAAU,uBAAzC,UACE,sDACA,+BACE,sPAMA,2YAQA,sVAOA,2QAMA,0SAuBOM,UAZC,SAAC,GACf,OADsB,eAEpB,eAAC,IAAMC,SAAP,WACE,cAAC,IAAD,IACA,cAAC,IAAD,UACE,cAACR,EAAD,MAEF,cAAC,IAAD,S,oCCzmBS,SAASS,EAA0BC,GAChD,GAAW,MAAPA,EAAa,MAAM,IAAIC,UAAU,gCADvC","file":"component---src-pages-data-processing-tsx-02503114578975916868.js","sourcesContent":["/*  eslint-disable */\nimport React from \"react\"\nimport { Helmet } from \"react-helmet\"\n\nimport Header from \"src/componentsV2/sections/Header\"\nimport { Footer } from \"src/sections/landing\"\nimport WidthWrapper from \"src/components/widthWrapper\"\n\nconst DataProcessingDoc = () => (\n  <div className=\"leading-loose pb-24 pt-90/16 md:pt-40\">\n    <Helmet>\n      <meta name=\"robots\" content=\"all\" />\n      <title>AirMason | Data Processing</title>\n      <meta name=\"description\" content=\"\" />\n    </Helmet>\n    <h1>DATA PROCESSING ADDENDUM</h1>\n    <p>\n      This Data Processing Addendum (“Addendum”) is part of the Master Service\n      Agreement (\"Agreement\") between AirMason Inc. (\"Processor\") and the\n      customer entity that is a party to the Agreement as a Customer\n      (\"Controller\") (each a \"Party\"; together \"the Parties\").\n    </p>\n    <br />\n    <h2>Table of Contents</h2>\n    <ol>\n      <li>\n        <a href=\"#definitions\">DEFINITIONS</a>\n      </li>\n      <li>\n        <a href=\"#roles-and-responsibilities\">ROLES AND RESPONSIBILITIES</a>\n      </li>\n      <li>\n        <a href=\"#data-processing-details\">DATA PROCESSING DETAILS</a>\n      </li>\n      <li>\n        <a href=\"#security\">SECURITY</a>\n      </li>\n      <li>\n        <a href=\"#subprocessing\">SUBPROCESSING</a>\n      </li>\n      <li>\n        <a href=\"#data-subject-rights\">DATA SUBJECT RIGHTS</a>\n      </li>\n      <li>\n        <a href=\"#data-transfers\">DATA TRANSFERS</a>\n      </li>\n      <li>\n        <a href=\"#data-breach-notification\">DATA BREACH NOTIFICATION</a>\n      </li>\n      <li>\n        <a href=\"#audit-rights\">AUDIT RIGHTS</a>\n      </li>\n      <li>\n        <a href=\"#return-or-deletion-of-data\">RETURN OR DELETION OF DATA</a>\n      </li>\n      <li>\n        <a href=\"#liability\">LIABILITY</a>\n      </li>\n      <li>\n        <a href=\"#term-and-termination\">TERM AND TERMINATION</a>\n      </li>\n    </ol>\n    <br />\n\n    <div id=\"definitions\" className=\"data-process-content\">\n      <h2>DEFINITIONS</h2>\n      <ol>\n        <li>\n          Agreement refers to the Master Service Agreement between AirMason and\n          the Controller, including any and all schedules, exhibits, and annexes\n          thereto.\n        </li>\n        <li>\n          Controller refers to the client of AirMason who determines the\n          purposes and means of Processing of Personal Data.\n        </li>\n        <li>\n          Data Subject means any identified or identifiable natural person who\n          is the subject of the Personal Data.\n        </li>\n        <li>\n          GDPR means the General Data Protection Regulation (Regulation (EU)\n          2016/679).\n        </li>\n        <li>\n          Personal Data means any information relating to a Data Subject that\n          Controller provides to Processor under the Agreement, which is\n          protected under the Data Protection Laws.\n        </li>\n        <li>\n          Processing means any operation or set of operations performed upon\n          Personal Data, whether or not by automated means, such as collection,\n          recording, organization, structuring, storage, adaptation or\n          alteration, retrieval, consultation, use, disclosure by transmission,\n          dissemination or otherwise making available, alignment or combination,\n          restriction, erasure, or destruction.\n        </li>\n        <li>\n          Processor refers to AirMason, a company that Processes Personal Data\n          on behalf of the Controller.\n        </li>\n        <li>\n          Data Protection Laws means all laws and regulations, including laws\n          and regulations of the European Union, the European Economic Area,\n          their member states, Switzerland, the United Kingdom, and the United\n          States and its states, applicable to the Processing of Personal Data\n          under the Agreement.\n        </li>\n        <li>\n          Subprocessor means any third-party appointed by or on behalf of\n          Processor to Process Personal Data on behalf of the Controller.\n        </li>\n        <li>\n          Service refers to the provision by AirMason of its employee handbook\n          creation platform that allows Controller to create, distribute, and\n          manage digital employee handbooks. The Service includes but is not\n          limited to the storage and processing of personal data related to\n          Controller's employees, the ability to send automated reminders to\n          employees for handbook signing, integration with Controller's existing\n          HRIS systems, Single Sign-On (SSO) capabilities, and any other\n          functionalities or services provided by AirMason under the Agreement.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"roles-and-responsibilities\" className=\"data-process-content\">\n      <h2>ROLES AND RESPONSIBILITIES</h2>\n      <ol>\n        <li>\n          Data Controller: The Controller (the client of AirMason) determines\n          the purposes and means of the Processing of Personal Data in\n          connection with the use of the Service. The Controller is responsible\n          for ensuring that the Personal Data it provides or directs to be\n          provided to AirMason for Processing in connection with the Service is\n          collected and transferred in compliance with applicable laws,\n          including securing necessary permissions and consents where required.\n        </li>\n        <li>\n          Data Processor: AirMason, as a Data Processor, Processes Personal Data\n          on behalf of the Controller in accordance with the terms of the\n          Agreement and this DPA, and will follow the Controller's instructions\n          unless such instructions are not technically feasible, violate any\n          applicable laws, or are not in alignment with the terms of the\n          Agreement or this DPA.\n        </li>\n        <li>\n          Data Subjects: Data Subjects are the identified or identifiable\n          natural persons to whom the Personal Data pertains. These may include,\n          for example, the Controller's employees or users, to whom AirMason may\n          send automated reminders for handbook signing or provide other\n          services as instructed by the Controller.\n        </li>\n        <li>\n          Subprocessors: AirMason may engage Subprocessors to provide certain\n          parts of the Service. AirMason will enter into written agreements with\n          each Subprocessor that imposes data protection obligations to ensure a\n          level of security appropriate to the risk associated with the\n          Processing of Personal Data.\n        </li>\n        <li>\n          Prohibited Data: The Controller shall not transfer or provide to\n          AirMason any Personal Data that falls under special categories of data\n          as defined by the GDPR or other applicable laws unless expressly\n          agreed to in writing by AirMason. Such data may include, but is not\n          limited to, sensitive Personal Data relating to racial or ethnic\n          origin, political opinions, religious beliefs, trade union membership,\n          physical or mental health or condition, sexual orientation, or\n          criminal offences (\"Prohibited Data\"). AirMason is not designed to\n          Process Prohibited Data and assumes no responsibility for such data\n          provided by the Controller.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"data-processing-details\" className=\"data-process-content\">\n      <h2>DATA PROCESSING DETAILS</h2>\n      <ol>\n        <li>\n          Purpose: AirMason shall Process Personal Data solely for the purpose\n          of providing the Services stipulated in the Agreement, and for no\n          other purpose, unless other purposes are expressly agreed upon in\n          writing by the Parties.\n        </li>\n        <li>\n          Processing Instructions: AirMason will only Process Personal Data in\n          accordance with the Controller’s documented instructions. The\n          Controller’s initial instructions to AirMason for the Processing of\n          Personal Data are to perform the Services in accordance with the\n          Agreement.\n        </li>\n        <li>\n          Security Measures: AirMason shall implement appropriate technical and\n          organizational measures to protect the Personal Data, taking into\n          account the state of technology, the costs of implementation, the\n          nature, scope, context, and purposes of Processing, as well as the\n          risk to the rights and freedoms of natural persons.\n        </li>\n        <li>\n          Confidentiality: AirMason shall ensure that persons authorized to\n          Process the Personal Data have committed themselves to confidentiality\n          or are under an appropriate statutory obligation of confidentiality.\n        </li>\n        <li>\n          Assistance: AirMason shall, taking into account the nature of the\n          Processing, assist the Controller by appropriate technical and\n          organizational measures, insofar as this is possible, for the\n          fulfilment of the Controller's obligation to respond to requests for\n          exercising the data subject's rights.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"security\" className=\"data-process-content\">\n      <h2>SECURITY</h2>\n      <ol>\n        <li>\n          Processor shall take all measures required pursuant to Article 32 of\n          the GDPR. Processor will implement and maintain appropriate technical\n          and organizational measures to protect the personal data against\n          unauthorized or unlawfol processing and against accidental loss,\n          destruction, damage, theft, alteration, or disclosure. These measures\n          shall be appropriate to the harm which might resolt from any\n          unauthorized or unlawfol processing, accidental loss, destruction,\n          damage or theft of the personal data and having regard to the nature\n          of the personal data which is to be protected. Such measures may\n          include, as appropriate:\n          <ul className=\"disc\">\n            <li>Pseudonymization and encryption of personal data</li>\n            <li>\n              Ability to ensure the ongoing confidentiality, integrity,\n              availability, and resilience of processing systems and services\n            </li>\n            <li>\n              Ability to restore the availability and access to personal data in\n              a timely manner in the event of a physical or technical incident\n            </li>\n            <li>\n              Process for regolarly testing, assessing, and evaluating the\n              effectiveness of technical and organizational measures for\n              ensuring the security of the processing\n            </li>\n          </ul>\n        </li>\n        <li>\n          Processor has implemented security measures which include, but are not\n          limited to, secure data transfer, data segregation, firewall\n          protections, system monitoring, logging and alerting, intrusion\n          detection and prevention, vulnerability management, and data\n          encryption at rest and in transit. Furthermore, Processor has in place\n          incident management processes and regularly carries out system\n          backups.\n        </li>\n        <li>\n          In addition to its obligations under Article 32 of the GDPR, Processor\n          commits to provide reasonable assistance to Controller in ensuring\n          compliance with the obligations pursuant to Articles 32 to 36 of the\n          GDPR, taking into account the nature of processing and the information\n          available to the Processor.\n        </li>\n        <li>\n          Details about specific technical and organizational measures\n          implemented by Processor may be further outlined in Annex 2 –\n          Technical and Organizational Measures.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"subprocessing\" className=\"data-process-content\">\n      <h2>SUBPROCESSING</h2>\n      <ol>\n        <li>\n          The Controller authorizes the Processor to engage sub-processors as\n          necessary to deliver the Service, subject to the requirements in this\n          Section. The Processor shall maintain an up-to-date list of its\n          sub-processors, which is available for\n          <a\n            href=\"https://storage.googleapis.com/airmason-handbook-us/AirMason%20Subprocessors.pdf\"\n            target=\"_blank\"\n          >\n            review here\n          </a>\n          .\n        </li>\n        <li>\n          The Processor shall enter into a written agreement with each\n          sub-processor containing data protection obligations at least as\n          protective as those in this Addendum, to the extent applicable to the\n          nature of the Service provided by such sub-processor. In such cases,\n          the Processor will ensure that such sub-processors are bound by\n          obligations consistent with this Addendum and that they implement\n          appropriate technical and organizational measures to comply with Data\n          Protection Laws.\n        </li>\n        <li>\n          In the event of any proposed change in sub-processor, the Processor\n          will notify the Controller at least 30 days in advance, allowing the\n          Controller to object to such changes. If the Controller objects to the\n          new sub-processor and the Processor chooses to retain that\n          sub-processor, the Controller may terminate this Agreement by\n          providing written notice to the Processor.\n        </li>\n        <li>\n          The Processor remains responsible at all times for the compliance of\n          each sub-processor with the obligations of this Addendum and for any\n          acts or omissions of the sub-processor that cause Processor to breach\n          any of its obligations under this Addendum.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"data-subject-rights\" className=\"data-process-content\">\n      <h2>DATA SUBJECT RIGHTS</h2>\n      <ol>\n        <li>\n          In accordance with Data Protection Laws, data subjects have certain\n          rights with respect to their Personal Data. As part of its Service,\n          AirMason provides the Controller with various self-service features,\n          which may be used to assist it in connection with its obligations\n          under Data Protection Laws pertaining to such rights.\n        </li>\n        <li>\n          These features enable the Controller to retrieve, correct, delete, or\n          restrict the use of Customer Data, including but not limited to:\n          <ul className=\"disc\">\n            <li>\n              Retrieval of all Signature Data and Employee Contacts through .csv\n              export\n            </li>\n            <li>PDF export of Employee Handbooks</li>\n          </ul>\n        </li>\n        <li>\n          In view of the nature of the processing, AirMason shall provide\n          reasonable assistance to the Controller, to the extent possible, to\n          enable the Controller to comply with its data protection obligations\n          with respect to data subject rights under Data Protection Laws.\n        </li>\n        <li>\n          If any request pertaining to data subject rights is made directly to\n          AirMason, AirMason will not respond to such communication directly,\n          except as necessary (e.g., to direct the data subject to contact the\n          Controller) or as legally required, without prior authorization from\n          the Controller.\n        </li>\n        <li>\n          If AirMason is required to respond to such a request and the\n          Controller is identifiable from the request, AirMason will promptly\n          notify the Controller and provide a copy of the request, unless\n          legally prohibited from doing so.\n        </li>\n        <li>\n          Nothing in the Agreement, including this DPA, shall restrict or\n          prevent AirMason from responding to any data subject or data\n          protection authority requests concerning Personal Data for which\n          AirMason is a controller.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"data-transfers\" className=\"data-process-content\">\n      <h2>DATA TRANSFERS</h2>\n      <ol>\n        <li>\n          In connection with the provision of the Service, AirMason may store\n          and process Personal Data in the United States, European Union, or\n          Canada, in accordance with the customer's location and preferences.\n        </li>\n        <li>\n          For US-based customers, Personal Data will be stored and processed\n          within US-based Google Cloud data centers, and no data is transferred\n          outside the United States. For EU-based customers, Personal Data is\n          stored and processed within the Brussels-based Google Cloud data\n          center, and no data is transferred outside the EU. For Canadian\n          customers who have specifically requested a single tenant VPC,\n          Personal Data is stored and processed within Canadian-based data\n          centers.\n        </li>\n        <li>\n          AirMason, in collaboration with Google Cloud's robust policies and\n          mechanisms, ensures that the storage and processing of Personal Data\n          complies with all applicable Data Protection Laws. In cases where\n          Personal Data is transferred, it is limited to what is necessary to\n          provide the Service. Access to Personal Data by AirMason's staff and\n          subcontractors is limited to those who need to provide the Service.\n        </li>\n        <li>\n          Although AirMason does not directly implement specific mechanisms such\n          as Standard Contractual Clauses or Privacy Shield certifications, the\n          adherence to such policies is enforced by Google Cloud. AirMason will\n          continue to adhere to all relevant data protection laws and ensure\n          that Personal Data is stored and processed securely, and in compliance\n          with the relevant laws.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"data-breach-notification\" className=\"data-process-content\">\n      <h2>DATA BREACH NOTIFICATION</h2>\n    </div>\n    <p>\n      In the event of a data breach, AirMason has a thorough internal procedure\n      in place to identify, contain, eradicate, recover from, and conduct\n      post-incident analysis of the breach. These procedures ensure an immediate\n      response and minimize the impact on the affected parties. AirMason\n      employees are required to report any unauthorized or suspicious activity\n      they notice in relation to production systems or related communication\n      systems.\n    </p>\n\n    <br />\n    <p>\n      Upon the discovery of a data breach, AirMason promptly commences an\n      in-depth, five-phase incident response procedure. These phases include:\n    </p>\n    <ol>\n      <li>Identification and Triage</li>\n      <li>Containment</li>\n      <li>Eradication</li>\n      <li>Recovery</li>\n      <li>Post-Incident Analysis</li>\n    </ol>\n    <br />\n    <p>\n      AirMason's incident response team conducts all stages of this process,\n      documenting all measures taken during each phase, including start and end\n      times of all efforts.\n    </p>\n    <br />\n    <p>\n      For significant events, such as the application of critical security\n      patches to the operating system or network, AirMason commits to notifying\n      clients within seven days of the event.\n    </p>\n    <br />\n    <p>\n      In the event of a data breach that results in a risk to the rights and\n      freedoms of individuals, AirMason will notify affected customers promptly\n      via email. This notification will contain details including:\n    </p>\n    <ol>\n      <li>A description of the nature of the breach,</li>\n      <li>The types of data that were involved,</li>\n      <li>Measures taken by AirMason to address the breach,</li>\n      <li>\n        Recommendations for steps users can take to protect themselves, such as\n        resetting their passwords.\n      </li>\n    </ol>\n    <br />\n    <p>\n      In the aftermath of a data breach, AirMason will assist its customers in\n      mitigating potential adverse effects. As part of its support, AirMason\n      will provide assistance to users in resetting their passwords.\n    </p>\n    <p>\n      AirMason is committed to safeguarding your data and will continue to\n      enhance and update its data breach procedures to ensure the highest level\n      of security. We believe in transparency and will do our best to keep our\n      customers informed and supported in the event of a data breach.\n    </p>\n    <br />\n    <div id=\"audit-rights\" className=\"data-process-content\">\n      <h2>AUDIT RIGHTS</h2>\n    </div>\n    <p>\n      AirMason is committed to maintaining the highest level of data protection\n      and understands the importance of transparency and accountability in this\n      regard. However, due to the nature of our service, the sensitive\n      information we handle, and the potential disruption to our operations, we\n      currently do not allow customers or their authorized third-party auditors\n      to conduct audits of our data processing activities.\n    </p>\n    <br />\n    <p>\n      We assure our customers that our data handling and processing practices\n      are designed to be compliant with the relevant Data Protection Laws. To\n      this end, we have rigorous internal policies and procedures in place to\n      ensure our compliance, and we regularly review and update these policies\n      in line with the best practices and legal requirements.\n    </p>\n    <br />\n    <p>\n      To provide transparency and demonstrate our compliance, we make available\n      relevant documentation such as privacy policies, security practices, and\n      data processing addendums. Additionally, we can provide a SOC 2 report\n      upon request, which is conducted by an independent auditor and provides a\n      thorough review of our data handling practices.\n    </p>\n    <br />\n    <p>\n      We understand the importance of verifying compliance with data protection\n      laws and regulations. Therefore, if a customer has specific compliance\n      requirements or queries, they should communicate these to us, and we will\n      strive to address them in the best possible manner.\n    </p>\n    <br />\n    <div id=\"return-or-deletion-of-data\" className=\"data-process-content\">\n      <h2>RETURN OR DELETION OF DATA</h2>\n      <p className=\"-ml-38/16\">\n        Upon termination of the Services or upon a written request by the\n        Customer, AirMason shall return or delete Customer Personal Data in its\n        possession. AirMason undertakes the following steps to ensure the secure\n        handling of the Customer's Personal Data:\n      </p>\n      <ol>\n        <li>\n          Deletion After Termination: Following the termination of the\n          Customer's contract, AirMason retains Customer Personal Data for a\n          period of 90 days. During this period, the Customer can request a data\n          export by email. After the lapse of this 90-day period, the Personal\n          Data is automatically deleted.\n        </li>\n        <li>\n          Deletion Upon Request: Customers can request the deletion of their\n          Personal Data at any time by sending an email to AirMason. We aim to\n          comply with such deletion requests within 7 days.\n        </li>\n        <li>\n          Anonymization of Data: In cases where there is a soft delete (via the\n          dashboard, under regular operations), AirMason may anonymize or\n          de-identify Customer Personal Data rather than deleting it entirely.\n          This is done to maintain the integrity of the data while ensuring that\n          no personal identifiable information remains.\n        </li>\n        <li>\n          Data Deletion Procedures: AirMason uses a multi-step process to ensure\n          the complete deletion of data. This includes the deletion of data from\n          our live servers, followed by the deletion from our backup servers.\n          Once deletion is completed, the Customer will receive an email\n          notification confirming the deletion.\n        </li>\n        <li>\n          Exceptions: There are no exceptions to the data return or deletion\n          policy except as required by applicable laws. In such cases, only the\n          minimum necessary information is retained.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <p>\n      This Return or Deletion of Data policy ensures AirMason's commitment to\n      respect the privacy and confidentiality of the Customer's Personal Data.\n    </p>\n    <br />\n    <div id=\"liability\" className=\"data-process-content\">\n      <h2>LIABILITY</h2>\n      <ol>\n        <li>\n          The aggregate liability of each party and all of its Affiliates\n          arising out of or related to this Data Processing Addendum (including\n          the Standard Contractual Clauses, where applicable) shall be subject\n          to the exclusions and limitations of liability set forth in each\n          Service Level Agreement governing the relationship between the\n          Customer and AirMason.\n        </li>\n        <li>\n          Any claims made against AirMason under or in connection with this Data\n          Processing Addendum (including, where applicable, the Standard\n          Contractual Clauses) shall be brought solely by the Customer entity\n          that is a party to the Agreement.\n        </li>\n        <li>\n          This limitation of liability reflects the allocation of risk between\n          the Parties and is an essential element of the bargain between the\n          Parties.\n        </li>\n      </ol>\n    </div>\n    <br />\n    <div id=\"term-and-termination\" className=\"data-process-content\">\n      <h2>TERM AND TERMINATION</h2>\n      <ol>\n        <li>\n          Term: This DPA shall commence on the Effective Date and shall continue\n          in effect until termination of the Agreement or until AirMason ceases\n          to process Customer Data on behalf of the Customer, whichever is\n          later.\n        </li>\n        <li>\n          Termination: This DPA shall terminate automatically upon termination\n          or expiration of the Agreement in accordance with its terms. Any\n          obligation imposed on AirMason under this DPA regarding the handling\n          and protection of Customer Data shall survive termination or\n          expiration of this DPA to the extent AirMason continues to possess or\n          control such Customer Data.\n        </li>\n        <li>\n          Breach: In the event of a breach of the terms of this DPA by AirMason,\n          the Customer may, without prejudice to any other rights or remedies\n          and on giving at least fifteen (15) days written notice to AirMason,\n          terminate this DPA and the Agreement if AirMason fails to cure such\n          breach within the notice period.\n        </li>\n        <li>\n          Right to Terminate: AirMason reserves the right to terminate this DPA\n          and the Agreement upon thirty (30) days written notice if the Customer\n          is in breach of any term of this DPA and fails to cure such breach\n          within the notice period.\n        </li>\n        <li>\n          Data After Termination: Upon termination or expiration of this DPA,\n          AirMason will cease all processing of Customer Data and will, at the\n          request of the Customer, return or delete Customer Data in its\n          possession, in accordance with Section 10 of this DPA.\n        </li>\n      </ol>\n    </div>\n  </div>\n)\n\nconst Privacy = ({}) => {\n  return (\n    <React.Fragment>\n      <Header />\n      <WidthWrapper>\n        <DataProcessingDoc />\n      </WidthWrapper>\n      <Footer />\n    </React.Fragment>\n  )\n}\n\nexport default Privacy\n","export default function _objectDestructuringEmpty(obj) {\n  if (obj == null) throw new TypeError(\"Cannot destructure undefined\");\n}"],"sourceRoot":""}