Service Specific Terms

Posted: August 7, 2019

Effective as of: of: September 24, 2019

Unless otherwise defined in this Service Schedule, capitalized terms will have the meaning given to them in the Terms (currently available at https://www.hellosign.com/terms) and Privacy Policy (current available at https://www.hellosign.com/privacy).

HELLOSIGN (END USER AND WEBAPP)

  1. 1.   Service Description. HelloSign is an electronic signature service which allows Customers to display, deliver, acknowledge, store, and electronically sign documents.
  2. 2.   Authentication. A person signing a document via HelloSign must either have a HelloSign account or have received a request for signature in their email account.
  3. 3.   Audit Trails. Documents completed in HelloSign include an audit trail that contains information that helps track your document through its lifecycle. This information includes, but is not limited to, unique document ID generated by HelloSign, email addresses of the sender and recipient(s), IP addresses of the sender and recipient(s), and track events (such as date, time, and located when the following events occur - document uploaded, document viewed, document removed, document sent, document signed, decline to sign, signer email address updated, signer access code authenticated, signature request cancelled).

HelloSign API

  1. 1.   Service Description. HelloSign Application Programming Interface (“HelloSign API”) allows Customers to easily integrate or embed the HelloSign electronic signature solution into its application or workflow, creating a clean, branded, and seamless online experience allowing users to complete legally-binding agreements or transaction with your company and/or their customers.
  2. 2.   Authentication. To the extent that Customer elect to use the HelloSign API to enable embedded features on Customer Properties, Customer is required to authenticate the identity of each signer/end user through email confirmation or such other means that HelloSign may approval in its sole discretion. Customer is solely responsible and liable for such authentication and will indemnify, defend and hold HelloSign harmless against any claim related to such authentication.
  3. 3.   Signature Requests. A “Signature Request” is the transaction that takes place when Customer initiates a new signature process and make a corresponding call to the HelloSign APIs. For example, if you call “signature_request/send” to send out documents for signature, this will constitute one (1) Signature Request. Note that a single Signature Request can be used to gather signatures from multiple signers in cases where they are all involved in the same contract.
  4. 4.   API Keys. In order to use the HelloSign APIs, Customer must obtain its unique API credentials (an “API Key”) via the registration process. Customer is solely responsible for all activity associated with its API Key, regardless of whether it has knowledge of such activity. Customer must not share its API Key with any third party, shall keep such API Key secure, and shall use it as Customer’s sole means of accessing the HelloSign API.
  5. 5.   Transactions.
  6.      a.   Limits. Customer can make up to 2000 requests per hour for standard API requests, and 500 requests per hour for higher tier API requests. In test mode, Customer can do 50 requests per hour. Collectively the above are “Transaction Limits.” Please contact our sales department if you wish to increase your Transaction Limits.
  7.      b.   Rate Limits. HelloSign may be required to limit or suspend your use of the HelloSign APIs when such suspension or limited are necessary to prevent harm or liability to other customers/individuals, or to preserve the security, stability, araciality or integrity of the HelloSign Services.
  8. 6.   Properties. Only those Customer Properties that have been approved by HelloSign may access and use the Service. HelloSign reserves the right to reject any Customer Property, for any reason, in its sole discretion, including but not limited to ensure that you comply with the Terms and the Accept Use Policy. Furthermore, you will ensure that the Customer Properties contain terms of service and privacy policies that are consistent with the terms of this Agreement.
  9. 7.   API Restrictions. You agree that you will not (and will not permit any third party to) directly or indirectly: (a) create an API client that functions substantially the same as the HelloSign APIs; (b) make any use of the HelloSign APIs for any purpose independent of the Customer Properties; (c) misrepresent the source or ownership of the HelloSign APIs or remove, obscure, or alter any copyright, trademark or other proprietary rights notices, falsify or delete any author attributions, legal notices or other labels of the origin or source of the HelloSign APIs; or (d) interfere with or disrupt the HelloSign APIs or the servers or networks providing the HelloSign APIs or Service.
  10. 8.   Customer Applications. Customer may use the HelloSign APIs to develop applications and/or embedded signing experiences for use by Customer or Customer’s clients and their respective end users (collectively “Customer Applications”). Customer shall be solely responsible for the Customer Applications and shall ensure it has: a) provided its customers, clients, and end users with the applicable terms (including privacy terms) that authorize HelloSign to provide the Services hereunder, and b) the proper authority and/or authorization to share user or signer information (including personally identifiable information) with HelloSign.

HelloWorks

  1. 1.   Service Description. HelloWorks is an intelligent workflow automation service that simplifies document completion through advanced data validation, conditional logic, integrated e-signatures, and mobile-first design.
  2. 2.   Authentication. A person signing a document via an electronic signature feature offered within HelloWorks must either have a HelloSign account or have received a request for signature in their email account.
  3. 3.   Transactions. A HelloWorks “Transaction” occurs when customer or user launches a Workflow from the HelloWorks visual interface (currently named the” HelloWorks Builder”).
  4. 4.   Workflow. A “Workflow” is the combination of multiple tasks or processes being utilized. With the HelloWorks visual interface allows users to create combinations of multiple forms and documents that are required to be completed by an end user. Workflows are the basis of what becomes a transaction. After a workflow is launched, it becomes a transaction.
  5. 5.   End User / Participant. In HelloWorks, an end users / participant is an individual who receives the launched workflow and is required to complete the forms and documents online.

HelloWorks API

  1. 1.   Service Description. The HelloWorks API allows customers to easily integrate and embed our workflow automation and e-signature solutions into any application or workflow, creating a clean, branded, and seamless online experience allowing your users to simplify complex workflows, and complete legally-binding agreements and transactions.
  2. 2.   Authentication. To the extent that Customer elect to use the HelloWorks API to enable embedded features on Customer Properties, Customer is required to authenticate the identity of each participant/signer/end user through an email confirmation or such other means that HelloSign may approval in its sole discretion. Customer is solely responsible and liable for such authentication and will indemnify, defend and hold HelloSign harmless against any claim related to such authentication.
  3. 3.   API Keys. In order to use the HelloWorks APIs, Customer must obtain its unique API credentials (an “API Key”) via the registration process. Customer is solely responsible for all activity associated with your API Key, regardless of whether you have knowledge of such activity. Customer must not share your API Key with any third party, shall keep such API Key secure, and shall use it as Customer’s sole means of accessing the HelloSign APIs.
  4. 4.   Transactions.
         a.   Definition. A HelloWorks API Transaction is the use of the API to initiate either: 1) the collection and/or dissemination of information, or 2) a signature request.
         b.   Limits. Customer can make up to 500 requests per hour. In test mode, Customer can do 50 requests per hour. Collectively the above are “Transaction Limits.” Please contact our sales department if you wish to increase your Transaction Limits.
         c.   Rate Limits. HelloSign may be required to limit or suspend your use of the HelloWorks APIs when such suspension or limited are necessary to prevent harm or liability to other customers/individuals, or to preserve the security, stability, araciality or integrity of the HelloSign Services.
  5. 5.   Properties. Only those Customer Properties that have been approved by HelloSign may access and use the Service. HelloSign reserves the right to reject any Customer Property, for any reason, in its sole discretion, including but not limited to ensure that you comply with this Agreement or the Accept Use Policy. Furthermore, you will ensure that the Customer Properties contain terms of service or use that are consistent with the terms of this Agreement.
  6. 6.   API Restrictions. You agree that you will not (and will not permit any third party to) directly or indirectly: (a) create an API client that functions substantially the same as the HelloWorks APIs; (b) make any use of the HelloWorks APIs for any purpose independent of the Customer Properties; (c) misrepresent the source or ownership of the HelloWorks APIs or remove, obscure, or alter any copyright, trademark or other proprietary rights notices, falsify or delete any author attributions, legal notices or other labels of the origin or source of the HelloWorks APIs; or (d) interfere with or disrupt the HelloWorks APIs or the servers or networks providing the HelloSign APIs or Service.
  7. 7.   Customer Applications. Customer may use the HelloWorks APIs to develop applications and/or embedded signing experiences for use by Customer or Customer’s clients and their respective end users (collectively “Customer Applications”). Customer shall be solely responsible for the Customer Applications and shall ensure it has: a) provided its customers and end users with the applicable terms (including privacy terms) that allow HelloSign to provide the Services hereunder, and b) the proper authority and/or authorization to share end user information with HelloSign.

HelloSign for Salesforce

  1. 1.   Service Description. HelloSign for Salesforce is an integration that lets you quickly prepare documents for electronic signature, minimize the back-and-forth follow-up, and simplify the signing process for your clients by using data from your Salesforce fields.
  2. 2.   Eligibility. Customer must be on a HelloSign enterprise plan (or higher tier) to access this integration. Customer (or its administrator) can add users to its Salesforce integration within the limits of Customer’s subscription plan. HelloSign for Salesforce works with both Salesforce Classic and Salesforce Lightning Experience.
  3. 3.   Documents. All signed documents are stored within your Salesforce instance. You may then download or transfer the signed documents into your databases / document repositories.
  4. 4.   Third Party Content and Products. Customer understands that the HelloSign for Salesforce integration will provide Customer with access to Third Party Content and to Third Party Products that may access Customer’s instance of the HelloSign Services and export, delete or otherwise alter Customer Data (including Customer’s Confidential Information).
  5. 5.   Disclaimer. HelloSign does not warrant or support Third Party Content or Third Party Products (whether or not these items are designated by HelloSign as “powered”, “verified” or otherwise) and disclaims all responsibility and liability for these items and their access to the HelloSign Services, including their modification, deletion, disclosure or collection of Customer Data.

Third Party Integrations / Connectors

  1. 1.   Service Description. Third Party Integrations help connect HelloSign with the services you already use to power your business. Some examples of such integrations are Google (Gmail, Google Docs, Google Drive, and G Suite), Evernote, Hubspot CRM, Microsoft OneDrive, Oracle, and Slack.
  2. 2.   Eligibility. To use a HelloSign integration you must be a customer of HelloSign and a customer of the service you want to use the integration with. Some integrations may require that you approve the use of such service and/or consent to the transfer of your information/data between HelloSign and the third-party service.
  3. 3.   Third Party Content and Products. You are solely responsible for the use of such integration, third party service, and ensuring that you have the proper rights and permissions to share data between HelloSign and the third-party services. You understand that the Third-Party Integrations may provide Customer with access to Third Party Content and to Third Party Products that may access Customer’s instance of the HelloSign Services and export, delete or otherwise alter Customer Data (including Customer’s Confidential Information).
  4. 4.   Disclaimer. HelloSign does not warrant or directly support third party integrations, Third Party Content, Third Party Products (whether or not these items are designated by HelloSign as “powered”, “verified” or otherwise) and disclaims all responsibility and liability for these items and their access to the HelloSign Services, including their modification, deletion, disclosure or collection of Customer Data.

HelloFax

  1. 1.   Service Description. HelloFax is an electronic fax service that allows Customers to upload and manage documents online, send and receive faxes online, and electronically sign faxes. HelloFax has international coverage and currently covers over 70 countries worldwide.
  2. 2.   Account Information. Customers of HelloFax must provide HelloSign with accurate and up-to-date information including, but not limited to: name, billing address, physical address, payment information (including credit card number), and national ID number (where applicable). HelloSign may be required to obtain copies of Customers or its users national IDs where required by legal proceedings, investigations, or by our subcontractors/service providers. Customer will immediately provide any and all related account information upon request by HelloSign and Customer expressly authorizes HelloSign to share any and all account information, usage data, location data, and IP addresses with its subcontractors/service providers. HelloSign reserves the right to suspend or terminate Customer’s account and/or its use of HelloFax if such account information is out-of-date or not provided immediately upon request.
  3. 3.   Unsolicited Faxes and Spam. The transmission of unsolicited fax advertisements is illegal in the United States under the Federal Telephone Consumer Protection Act of 1991 (TCPA), and in the European Union under the Privacy and Electronic Communications Regulations 2003, and is also illegal under the laws of a number of other countries, states and provinces. We reserve the right to immediately suspend or terminate your use of HelloFax if send unsolicited fax advertisements and / or spam. We also reserve the right to monitor your use of HelloFax and HelloSign, in its sole discretion, may decide to not deliver any messages it considers unsolicited fax advertisements or spam.
  4. 4.   Reporting unsolicited faxes and spam. If you believe that you received an unsolicited fax advertisement, we recommend you contact the sender to inform them you would like to stop receiving such faxes. Please also contact HelloSign customer support so that we may investigate accordingly.
  5. 5.   Numbers and Porting. Customer may obtain new numbers from HelloSign for use with HelloFax. Such numbers are subject to availability and HelloSign does not guarantee that any particular number can be assigned to a Customer. HelloSign also supports number porting (for US, UK and Canada) as per the terms below:
         a.   Number Port-In Request Procedures.
              i.   Customer must keep the its existing service active in order to port a phone number to HelloSign.
              ii.   Please fill out and submit the Porting Request Form.
              iii.   Once we receive your request, we'll verify whether or not we can port your number and respond to your request as soon as possible. If we are able to port your number, we'll then ask you to fill out a Letter of Authorization form which we will forward to you. We'll also need the most recent copy of your invoice from your current provider to serve as proof that you own the number.
              iv.   Once both of the documents are submitted, we'll start the port request. After the request has been started, we'll ask you to sign up for a paid subscription (visit our pricing page) and you'll be assigned a temporary number by our system. You can choose to keep the number you're assigned for an extra monthly fee (currently $4.99) or we can swap it out with the number you are porting once it's accepted.
              v.   After the porting process is complete, we'll add the ported number to your account and assess a porting fee (currently $60) at that time.
              vi.   All fees are subject to HelloFax and HelloSign then current pricing, which may be updated from time-to-time.
         b.   The Number Port-Out Process. In order to request the porting out to another service provider of a fax number currently assigned to an account, you must follow the instructions specified by that service provider and must provide all information and cooperation requested by the relevant other services providers, HelloSign, or any other relevant third party. The porting of phone numbers into or out of an account requires Customer’s provision of specific and detailed information to HelloSign and/or other service providers, and procedures imposed by other service providers or HelloSign in order to comply with law and industry standards. Therefore, the completion of any number port request may depend on factors outside of HelloSign’s control, including delays caused by Customer and/or other service providers.
         c.   Unauthorized Port Outs. HelloSign is required by law to comply with any valid porting request. Phone numbers may be ported out from an account due to acts or omissions of third parties, and it may be difficult or impossible for HelloSign to: (i) prevent such port-outs: (ii) retrieve numbers ported out of an Account; or (iii) port such numbers back into an account. HelloSign has no responsibility or liability due to such port-outs.
         d.   Accurate Porting Information. Customer represents and warrants that all information provided in connection with any request to port in or port out numbers to or from the HelloFax Services (including without limitation any information or representations in any Letter of Agency) by Customer or any party acting on its behalf or direction will be true, accurate, and up-to-date.
         e.   Customer Compliance with Porting Laws. The porting of numbers is subject to telecommunications and other laws and may be subject to third-party terms and conditions. Customer, and/or any party acting on Customer’s behalf, shall not: (i) violate any applicable law or engage in any fraudulent or deceptive conduct in its porting-related requests or activities; (ii) engage in or facilitate “slamming” or the porting out of any fax number or change or attempt to change any party’s telephony service provider without first obtaining the proper, requisite consents and authorizations; or (iii) violate contractual or other obligations to service providers or other third parties.
         f.   Release of Numbers. In the event of account termination or cancellation, all numbers associated with the account which have not previously been ported to another provider may be released. The cancellation of individual lines may result in the release of the associated numbers if those numbers have not previously been ported to another provider. Customer is solely responsible for working with its new third-party provider to port out any numbers prior to termination or cancellation of HelloFax or other HelloSign Services, or any individual line.

HelloFax API

  1. 1.   The HelloFax API allows customers to easily integrate and integrate our electronic fax solutions into their applications or website.
  2. 2.   Authentication. To the extent that Customer elects to use the HelloFax API to enable integrated features on Customer Properties, Customer is required to authenticate the identity of each end user / sender through an email confirmation or such other means that HelloSign may approval. Customer is solely responsible and liable for such authentication and will indemnify, defend and hold HelloSign harmless against any claim related to such authentication.
  3. 3.   API Keys. In order to use the HelloFax APIs, Customer must obtain its unique API credentials (an “API Key”) via the registration process. Customer is solely responsible for all activity associated with your API Key, regardless of whether you have knowledge of such activity. Customer must not share your API Key with any third party, shall keep such API Key secure, and shall use it as Customer’s sole means of accessing the HelloFax APIs.
  4. 4.   Transactions.
         a.   Limits. Customer can make up to 200 pending fax requests per day. Please contact our sales department if you wish to increase your fax request limits.
         b.   Rate Limits. HelloSign may be required to limit or suspend your use of the HelloFax APIs when such suspension or limited are necessary to prevent harm or liability to other customers/individuals, or to preserve the security, stability, araciality or integrity of the HelloSign Services.
  5. 5.   Properties. Only those Customer Properties that have been approved by HelloSign may access and use the Service. HelloSign reserves the right to reject any Customer Property, for any reason, in its sole discretion, including but not limited to ensure that you comply with this Agreement or the Acceptable Use Policy. Furthermore, you will ensure that the Customer Properties contain terms of service or use that are consistent with the terms of this Agreement.
  6. 6.   API Restrictions. You agree that you will not (and will not permit any third party to) directly or indirectly: (a) create an API client that functions substantially the same as the HelloFax APIs; (b) make any use of the HelloFax APIs for any purpose independent of the Customer Properties; (c) misrepresent the source or ownership of the HelloFax APIs or remove, obscure, or alter any copyright, trademark or other proprietary rights notices, falsify or delete any author attributions, legal notices or other labels of the origin or source of the HelloFax APIs; or (d) interfere with or disrupt the HelloFax APIs or the servers or networks providing the HelloFax APIs or Service.
  7. 7.   Customer Applications. Customer may use the HelloFax APIs to develop applications for use by Customer or Customer’s clients and their respective end users (collectively “Customer Applications”). Customer shall be solely responsible for the Customer Applications and shall ensure it has: a) provided its customers and end users with the applicable terms (including privacy terms) that allow HelloSign to provide the Services hereunder, and b) the proper authority and/or authorization to share end user information with HelloSign.