Last updated: March 2020
PLEASE READ THIS DATA PRIVACY AND SECURITY ADDENDUM (“ADDENDUM”) CAREFULLY BEFORE USING THE WEBSITE, SOFTWARE OR SERVICES OFFERED BY PIPE17, INC. (“PIPE17” OR “PROCESSOR”). THIS ADDENDUM SHALL APPLY TO THE EXTENT PIPE17 ACCESSES OR COLLECTS PERSONAL DATA (DEFINED BELOW) IN ITS CAPACITY AS A SERVICE PROVIDER OR IS A PROCESSOR OF PERSONAL DATA THAT IS SUBJECT TO CERTAIN DATA PROTECTION LAWS (DEFINED BELOW). YOU OR THE ENTITY YOU REPRESENT (“CUSTOMER” OR “CONTROLLER”) AGREE THAT YOU HAVE READ AND ACCEPT THE TERMS IN THIS ADDENDUM, WHICH SUPPLEMENT PIPE17’S TERMS OF SERVICE AVAILABLE AT https://pipe17.com/terms-of-service (“TERMS OF SERVICE”). IF YOU ARE ACCESSING THE SERVICES ON BEHALF OF YOUR EMPLOYER, YOU REPRESENT AND WARRANT THAT YOU HAVE THE AUTHORITY TO AGREE TO THESE TERMS ON ITS BEHALF AND THE RIGHT TO BIND YOUR EMPLOYER THERETO. IF EITHER YOU OR YOUR EMPLOYER DO NOT UNCONDITIONALLY AGREE TO ALL THE TERMS AND CONDITIONS OF THIS ADDENDUM, YOU HAVE NO RIGHT TO USE PIPE17’S SERVICES AND MUST NAVIGATE AWAY FROM THIS PAGE.
This Addendum supplements the Terms of Service whenever any user of Pipe17’s Services provides Pipe17 with personal data that is or will be subject to Data Protection Laws. Any terms not defined in this Addendum shall have the meaning set forth in the Terms of Service. In the event of a conflict between the terms and conditions of this Addendum and the Terms of Service, the terms and conditions of this Addendum shall supersede and control.
1.1. “Anonymous Data” means Personal Data that has been processed in such a manner that it can no longer be attributed to an identified or identifiable natural person.
1.2. “Authorized Employee” means an employee of Processor who has a need to know or otherwise access Personal Data to enable Processor to perform their obligations under this Addendum or the Terms of Service.
1.3. “Authorized Individual” means an Authorized Employee or Authorized Subcontractor.
1.4. “Authorized Subcontractor” means a third-party subcontractor, agent, reseller, or auditor who has a need to know or otherwise access Personal Data to enable Processor to perform its obligations under this Addendum or the Terms of Service, and who is either (1) listed as a subprocessor on Pipe17’s List (as defined in Section 4.2 below) or (2) authorized by Controller to do so under Section 4.2 of this Addendum.
1.5. “Data Subject” means an identified or identifiable person to whom Personal Data relates.
1.6. “Instruction” means a direction, either in writing, in textual form (e.g. by e-mail) or by using a software or online tool, issued by Controller to Processor and directing Processor to Process Personal Data.
1.7. “Personal Data” means any information relating to Data Subject which Processor Processes on behalf of Controller other than Anonymous Data, and includes Sensitive Personal Information.
1.8. “Personal Data Breach” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, personal data transmitted, stored, or otherwise processed.
1.9. “Process” or “Processing” means any operation or set of operations which is performed upon the Personal Data, whether or not by automatic means, such as collection, recording, organization, storage, adaptation or alteration, retrieval, consultation, disclosure by transmission, dissemination or otherwise making available, alignment or combination, blocking, erasure, or destruction.
1.10. “Sensitive Personal Information” means a Data Subject’s (i) government-issued identification number (including social security number, driver’s license number or state-issued identification number); (ii) financial account number, credit card number, debit card number, credit report information, with or without any required security code, access code, personal identification number or password, that would permit access to an individual’s financial account; (iii) genetic and biometric data or data concerning health; or (iv) Personal Data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, sexual orientation or sexual activity, criminal convictions and offences (including commission of or proceedings for any offense committed or alleged to have been committed), or trade union membership.
1.11. “Services” shall have the meaning set forth in the Terms of Service.
1.12. “Standard Contractual Clauses” means the agreement executed by and between Controller and Processor and attached hereto as Exhibit B pursuant to the European Commission’s decision (C(2010)593) of February 5, 2010 on standard contractual clauses for the transfer of personal data to processors established in third countries which do not ensure an adequate level of protection.
1.13. “Supervisory Authority” means an independent public authority which is established by a member state of the European Union, Iceland, Liechtenstein, or Norway.
2.1. The rights and obligations of the Controller with respect to this Processing are described herein. Controller shall, in its use of the Services, at all times Process Personal Data, and provide instructions for the Processing of Personal Data, in compliance with all applicable federal, state, local, and foreign laws, regulations, and rules relating to data protection and privacy (the “Data Protection Laws”), including, without limitation, the General Data Protection Regulation (Regulation (EU) 2016/679) (the “GDPR”) and the California Consumer Privacy Act (the “CCPA”). Controller shall ensure that its instructions comply with all laws, rules and regulations applicable in relation to the Personal Data, and that the Processing of Personal Data in accordance with Controller’s instructions will not cause Processor to be in breach of the Data Protection Laws. Controller is solely responsible for the accuracy, quality, and legality of (i) the Personal Data provided to Processor by or on behalf of Controller, (ii) the means by which Controller acquired any such Personal Data, and (iii) the instructions it provides to Processor regarding the Processing of such Personal Data. Controller shall not provide or make available to Processor any Personal Data in violation of the Terms of Service or otherwise inappropriate for the nature of the Services, and shall indemnify Processor from all claims and losses in connection therewith. For the avoidance of doubt, Customer retains control of the Personal Information and remains responsible for Customer’s compliance obligations under the Data Protection Laws, including providing any required notices and obtaining any consents required for the lawful processing of the Personal Information.
2.2. Pipe17 shall Process Personal Data only (i) for the purposes set forth in the Terms of Service, (ii) in accordance with the terms and conditions set forth in this Addendum and any other documented instructions provided by Controller, and (iii) in compliance with the Data Protection Laws. Controller hereby instructs Pipe17 to Process Personal Data in accordance with the foregoing and as part of any Processing initiated by Controller in its use of the Services.
2.3. The subject matter, nature, purpose, and duration of this Processing, as well as the types of Personal Data collected and categories of Data Subjects, are described in Exhibit A to this Addendum.
2.4. Following completion of the Services, at Controller’s choice, Processor shall return or delete the Personal Data, except as required to be retained by law. If Controller and Processor have entered into Standard Contractual Clauses as described in Section 6 (Transfers of Personal Data), the parties agree that the certification of deletion of Personal Data that is described in Clause 12(1) of the Standard Contractual Clauses shall be provided by Processor to Controller only upon Controller’s request.
3.1. Processor shall take commercially reasonable steps to ensure the reliability and appropriate training of any Authorized Employee.
3.2. Processor shall ensure that all Authorized Employees are made aware of the confidential nature of Personal Data and have executed confidentiality agreements that prevent them from disclosing or otherwise Processing, both during and after their engagement with Processor, any Personal Data except in accordance with their obligations in connection with the Services.
3.3. Processor shall take commercially reasonable steps to limit access to Personal Data to only Authorized Individuals and shall take reasonable steps to limit their access to the part or parts of the Personal Information that those Authorized Individuals strictly require for the performance of their duties.
4.1. Controller acknowledges and agrees that Processor may (1) engage its affiliates and the Authorized Subcontractors listed in the “List” to this Addendum to access and Process Personal Data in connection with the Services and (2) from time to time engage additional third parties for the purpose of providing the Services, including without limitation the Processing of Personal Data.
4.2. A list of Processor’s current Authorized Subcontractors (the “List”) is available at https://pipe17.com/security/sub-processors (such URL may be updated by Processor from time to time). At least thirty (30) days before enabling any third party other than Authorized Subcontractors to access or participate in the Processing of Personal Data, Processor will add such third party to the List and notify Controller of that update via email. Controller may object to such an engagement in writing within ten (10) days of receipt of the aforementioned notice by Controller.
4.2.1. If Controller reasonably objects to an engagement in accordance with Section 4.2, Processor may provide Controller with a written description of commercially reasonable alternative(s), if any, to such engagement, including without limitation modification to the Services. If Processor, in its sole discretion, does not provide any such alternative(s), or if Controller does not agree to any such alternative(s) if provided, Processor may terminate this Addendum. Termination shall not relieve Controller of any fees owed to Processor under the Terms of Service.
4.2.2. If Controller does not object to the engagement of a third party in accordance with Section 4.2 within ten (10) days of notice by Processor, that third party will be deemed an Authorized Subcontractor for the purposes of this Addendum.
4.3. Processor shall ensure that all Authorized Subcontractors have executed confidentiality agreements that prevent them from disclosing or otherwise Processing, both during and after their engagement by Processor, any Personal Data.
4.4. Processor shall, by way of contract or other legal act under European Union or European Union member state law (including without limitation approved codes of conduct and standard contractual clauses), ensure that every Authorized Subcontractor is subject to obligations regarding the Processing of Personal Data that are no less protective than those to which the Processor is subject under this Addendum.
4.5. Processor shall be liable to Controller for the acts and omissions of Authorized Subcontractors to the same extent that Processor would itself be liable under this Addendum had it conducted such acts or omissions.
4.6. If Controller and Processor have entered into Standard Contractual Clauses as described in Section 6 (Transfers of Personal Data), (i) the above authorizations will constitute Controller’s prior written consent to the subcontracting by Processor of the processing of Personal Data if such consent is required under the Standard Contractual Clauses, and (ii) the parties agree that the copies of the agreements with Authorized Subcontractors that must be provided by Processor to Controller pursuant to Clause 5(j) of the Standard Contractual Clauses may have commercial information, or information unrelated to the Standard Contractual Clauses or their equivalent, removed by the Processor beforehand, and that such copies will be provided by the Processor only upon request by Controller.
5.1. 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, Pipe17 shall at all times implement appropriate technical and organizational measures designed to safeguard Personal Information against unauthorized or unlawful processing, access, copying, modification, storage, reproduction, display, or distribution, and against accidental loss, destruction, or damage including, but not limited to, the security measures set out in Appendix C. Pipe17 must document those measures in writing and periodically review them, at least annually, to ensure they remain current and complete.
5.2. Where appropriate, Pipe17 shall take reasonable precautions to preserve the integrity of any Personal Information it processes and to prevent any corruption or loss of the Personal Information, including but not limited to establishing effective back-up and data restoration procedures.
6.1. Any transfer of Personal Data made subject to this Addendum from member states of the European Union, Iceland, Liechtenstein, Norway, Switzerland or the United Kingdom to any countries which do not ensure an adequate level of data protection within the meaning of the laws and regulations of these countries shall, to the extent such transfer is subject to such laws and regulations, be undertaken by Processor through the Standard Contractual Clauses set forth in Exhibit B to this Addendum.
6.2. Customer hereby grants its prior written consent to the transfer of the Personal Information by Pipe17 to the United States or such other countries set forth in an Order Form executed by Customer if such consent is required under the Standard Contractual Clauses or otherwise. Any transfer of Personal Information to any other country will only be done with Customer’s prior written consent.
7.1. Processor shall, to the extent permitted by law, promptly notify Controller upon receipt of a request by a Data Subject to exercise the Data Subject’s right of: access, rectification, restriction of Processing, erasure, data portability, restriction or cessation of Processing, withdrawal of consent to Processing, and/or objection to being subject to Processing that constitutes automated decision-making (such requests individually and collectively “Data Subject Request(s)”). If Processor receives a Data Subject Request in relation to Controller’s data, Processor will advise the Data Subject to submit their request to Controller and Controller will be responsible for responding to such request, including, where necessary, by using the functionality of the Services.
7.2. Processor shall, at the request of the Controller, and taking into account the nature of the Processing applicable to any Data Subject Request, apply appropriate technical and organizational measures to assist Controller in complying with Controller’s obligation to respond to such Data Subject Request and/or in demonstrating such compliance, where possible, provided that (i) Controller is itself unable to respond without Processor’s assistance and (ii) Processor is able to do so in accordance with all applicable laws, rules, and regulations. Controller shall be responsible to the extent legally permitted for any costs and expenses arising from any such assistance by Processor.
8.1. Processor shall, taking into account the nature of the Processing and the information available to Processor, provide Controller with reasonable cooperation and assistance where necessary for Controller to comply with its obligations under the GDPR to conduct a data protection impact assessment and/or to demonstrate such compliance, provided that Controller does not otherwise have access to the relevant information. Controller shall be responsible to the extent legally permitted for any costs and expenses arising from any such assistance by Processor.
8.2. Processor shall, taking into account the nature of the Processing and the information available to Processor, provide Controller with reasonable cooperation and assistance with respect to Controller’s cooperation and/or prior consultation with any Supervisory Authority, where necessary and where required by the GDPR. Controller shall be responsible to the extent legally permitted for any costs and expenses arising from any such assistance by Processor.
8.3. Processor shall maintain records sufficient to demonstrate its compliance with its obligations under this Addendum, and retain such records for a period of three (3) years after the termination of the Terms of Service. Controller shall, with reasonable notice to Processor, have the right to review, audit and copy such records at Processor’s offices during regular business hours.
8.4. Upon Controller’s request, Processor shall, no more than once per calendar year, make available for Controller’s review copies of certifications or reports demonstrating Processor’s compliance with prevailing data security standards applicable to the Processing of Controller’s Personal Data. If Controller and Processor have entered into Standard Contractual Clauses as described in Section 6 (Transfers of Personal Data), the parties agree that the audits described in Clause 5(f) and Clause 12(2) of the Standard Contractual Clauses shall be carried out in accordance with this Section 8.4.
8.5. In the event of a Personal Data Breach, Processor shall, without undue delay, inform Controller of the Personal Data Breach and take such steps as Processor in its sole discretion deems necessary and reasonable to remediate such violation (to the extent that remediation is within Processor’s reasonable control).
8.6. In the event of a Personal Data Breach, Processor shall, taking into account the nature of the Processing and the information available to Processor, provide Controller with reasonable cooperation and assistance necessary for Controller to comply with its obligations under the GDPR with respect to notifying (i) the relevant Supervisory Authority and (ii) Data Subjects affected by such Personal Data Breach without undue delay.
8.7. The obligations described in Sections 8.5 and 8.6 shall not apply in the event that a Personal Data Breach results from the actions or omissions of Controller. Processor’s obligation to report or respond to a Personal Data Breach under Sections 8.5 and 8.6 will not be construed as an acknowledgement by Processor of any fault or liability with respect to the Personal Data Breach.
9.1. The total liability of each of Controller and Processor (and their respective employees, directors, officers, affiliates, successors, and assigns), arising out of or related to this Addendum, whether in contract, tort, or other theory of liability, shall not, when taken together in the aggregate, exceed the limitation of liability set forth in the Terms of Service.
Details of Processing
Nature and Purpose of Processing: Processor will Process Personal Data as necessary to perform the Services pursuant to the Terms of Service, and as further instructed by Controller in its use of the Services.
Duration of Processing:180 days
Categories of Data Subjects: Controller customers
Type of Personal Data:
Standard Contractual Clauses
For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection.
CONTROLLER (referred to herein as the “Data Exporter”)
And PIPE17 (referred to herein as the “Data Importer”)
each a “party”; together “the parties”,
HAVE AGREED on the following Contractual Clauses (the “Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1.
The Clauses become effective at the same time as the Addendum. If you are accessing the Services on behalf of your employer, you represent and warrant that you have the authority to agree to these terms on its behalf and the right to bind your employer thereto. If either you or your employer do not unconditionally agree to the Clauses, you have no right to use Pipe17’s Services and must navigate away from all Pipe17 webpages and applications.
For the purposes of the Clauses:
(a) ‘personal data’, ‘special categories of data’, ‘process/processing’, ‘controller’, ‘processor’, ‘data subject’ and ‘supervisory authority’ shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
(b) ‘the data exporter’ means the controller who transfers the personal data;
(c) ‘the data importer’ means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country’s system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
(d) ‘the subprocessor’ means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
(e) ‘the applicable data protection law’ means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
(f) ‘technical and organisational security measures’ means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
Details of the transfer
The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 which forms an integral part of the Clauses.
Third-party beneficiary clause
Obligations of the data exporter
The data exporter agrees and warrants:
(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter’s behalf and in accordance with the applicable data protection law and the Clauses;
(c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 to this contract;
(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
(e) that it will ensure compliance with the security measures;
(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
(h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
(j) that it will ensure compliance with Clause 4(a) to (i).
Obligations of the data importer
The data importer agrees and warrants:
(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
(c) that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
(d) that it will promptly notify the data exporter about:
(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
(ii) any accidental or unauthorised access, and
(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred;
(f) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
(g) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
(h) that the processing services by the subprocessor will be carried out in accordance with Clause 11;
(i) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
Mediation and jurisdiction
(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority;
(b) to refer the dispute to the courts in the Member State in which the data exporter is established.
Cooperation with supervisory authorities
The Clauses shall be governed by the law of the Member State in which the data exporter is established.
Variation of the contract
The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause.
Obligation after the termination of personal data processing services
This Appendix forms part of the Clauses.
The Member States may complete or specify, according to their national procedures, any additional necessary information to be contained in this Appendix.
The data exporter is the Controller.
The data importer is Pipe17.
The personal data transferred concern the following categories of data subjects (please specify):
Categories of data
The personal data transferred concern the following categories of data (please specify):
The personal data transferred will be subject to the following basic processing activities:
Transmitting, collecting, storing and analyzing data to enable Controller to fulfill orders.
This Appendix forms part of the Clauses.
Description of the technical and organisational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c) (or document/legislation attached):
Pipe17 is committed to providing a highly secure and reliable integration and business automation service. This includes maintaining the confidentiality of its customers’ information and ensuring that customers’ information will be available when it is needed. To achieve this we use proven, tested, best-in-class security tools, technologies, practices and procedures.
Pipe17 is hosted on public cloud infrastructure from Amazon Web Services (AWS) which maintains high standards of security for their data centers. You can read further about AWS security here: aws.amazon.com/security/
The Pipe17 website is only accessible over HTTPS. Traffic over HTTPS is encrypted and is protected from interception by unauthorized third parties. Pipe17 follows current best practices for security, including the use of strong encryption algorithms with a key length of at least 128 bits.
Pipe17 also uses secure protocols for communication with third-party systems: usually HTTPS, but other protocols such as SFTP and FTPS are also supported. For on-premise systems, access requires the installation of an on premises agent behind the firewall, which communicates outbound to Pipe17 over an encrypted link, using TLS 1.2.
Pipe17 uses a multi-tier architecture that segregates internal application systems from the public Internet. Public traffic to the website passes through a Web Application Firewall (WAF) and then is routed to interior systems running on private subnets. Interior as well as exterior network traffic uses secure, encrypted protocols. All network access, both within the datacenter and between the datacenter and outside services, is restricted by firewall and routing rules. Network access is recorded into a centralized secure logging system.
Clients login to Pipe17 using a password which is known only to them. Password length, complexity and expiration standards are enforced. Passwords are not stored; instead, as is standard practice, only a secure hash of the password is stored in the database. Because the hash is relatively expensive to compute, and because a “salting” method is used, brute-force guessing attempts are relatively ineffective, and password reverse-engineering is difficult even if the hash value were to be obtained by a malicious party.
Pipe17 users can optionally configure their accounts to use Two-Factor Authentication, by means of an authenticator app such as Google Authenticator, Microsoft Authenticator, or Authy.
Pipe17 supports integration with 3rd party SAML compliant SSO systems. This allows an enterprise to manage access to Pipe17 as well as other enterprise applications and apply custom authentication schemes and policies.
Pipe17 also supports Single Sign-On using 3rd-party credentials including Google and Microsoft Office 365.
Pipe17 supports automatic session logout after a period of time. Enterprises can set the appropriate timeout period according to their security needs.
When Pipe17 recipes connect to remote systems using user-supplied credentials, where possible this is done using OAuth2, and in those cases, no credentials need to be stored in the Pipe17 system. However, if a remote system requires credentials to be stored, they are encrypted using a 256-bit key.
Pipe17 has a comprehensive software development lifecycle process that incorporates security and privacy considerations. Design and code reviews, as well as unit and integration testing, are part of the process.
Development staff receive regular training on Secure Coding Practices, including avoidance of the OWASP Top Ten Web application vulnerabilities.
Pipe17 undergoes an annual penetration test of the website by a qualified third party. In addition, regular internal vulnerability scans are conducted.
All data stored in the Pipe17 system is encrypted at rest.
Pipe17 stores transaction related data for a limited period of time, in order to provide visibility into system activity, facilitate testing and debugging, allow re-running failed transactions, and to support long running transactions. All transaction data is always encrypted in transit and when stored in Pipe17’s platform.
Customers have control over the retention period of the transaction data. In addition, Pipe17 provides the ability to mask out sensitive data in the transaction logs for additional security.
Pipe17 has implemented a Business Continuity and Disaster Recovery program. This program includes not just measures to insure the high availability of Pipe17’s IT assets, but also contingency planning for natural disasters and other possible disruptions. IT measures used to insure high availability include running Pipe17 services in multiple redundant cloud Availability Zones and replication of the application database to a standby system.
Pipe17 has deployed a variety of security and monitoring tools for its production systems. There is 24×7 monitoring of the security status of its systems and automated alerts are configured for security and performance issues.
While we don’t anticipate there ever being a breach of our systems, Pipe17 has put in place a Security Incident Response Plan, which details roles, responsibilities and procedures in case of an actual or suspected security incident.
All employees are subject to background checks that cover education, employment and criminal history. Employment at Pipe17 requires written acknowledgement by employees of their roles and responsibilities with respect to protecting user data and privacy.
Pipe17 maintains an information security training program that is mandatory for all employees.
Knowledgeable full-time security personnel are on staff.