Secure Messaging

Learning Center

Back to top

Search Results




Support services for the Product will be provided to End Users in accordance with the terms set forth in this Policy. For greater clarity, in certain circumstances DeliverySlip Inc. (“DeliverySlip”) may be the Service Provider, in which case any reference to anything provided through the Service Provider will be deemed collapsed to the direct provision of same from DeliverySlip.

These Support and Service Levels Policy (“Policy”) is incorporated into and forms part of the End User License Agreement (“EULA”), and applies to your use of the Services described therein.


End User support and maintenance services are described herein to help ensure that the Product functions in accordance with the End User Licence Agreement, Product specifications and Documentation. DeliverySlip will provide (through Service Provider) to End Users Product Updates for any and all errors in the performance of the Product discovered by DeliverySlip (or through Service Provider). DeliverySlip will provide Product Updates (through Service Provider) in the same time period as it provides such Product Updates to its other Service Providers and/or End Users.


There are three (3) levels of support services. Support will be made available via e-mail and any other support contact tools employed by DeliverySlip as set forth in Table 1 below.

2.1 “Level 1 Support” will be defined to include the following: (1) initial error determination, (2) End User software/hardware issues, (3) installation/set-up, (4) How-To questions, (4) basic error resolution, and (5) escalation to Level 2 Support if the error remains unresolved.
2.2 “Level 2 Support” will be defined to include error isolation and re-creation as well as collection of all failure information and error logs associated with the reported error from the End User installation and from internal error re-creation and related tests.
2.3 “Level 3 Support” will be defined as engineering level support to remedy the reported error.


3.1 Level 1 Support – Service Provider
3.2 Level 2 Support – Service Provider
3.3 Level 3 Support – DeliverySlip through Service Provider


Service Provider will classify, or reclassify, as applicable, all errors as Severity 1, Severity 2, Severity 3 or Severity 4 in accordance with Table 1 below. In order to classify or reclassify an error as Severity 1 or Severity 2, a verifiable and reproducible test case must be provided. DeliverySlip will use reasonable efforts to correct such errors in accordance with the procedures, and to achieve resolution of such errors within the target time frames, all as set forth in this Section and Table 1.

For all inquiries regarding system status, upgrades, and Level 1 Support, Level 2 Support and Level 3 Support incidents, Service Provider or Customer must email, or for emergencies call 1.877.404.9964 ext 7007 and ask for “Emergency Support”.


The following table shall define severity levels (in addition to those definitions that may be agreed upon in writing by the parties from time to time), the service objective, and the resolution time for defects and errors. DeliverySlip will, after initially responding to any reported defect, periodically update Service Provider on the status of the defect.

Severity Definition Service Objective Resolution Time
1 Product or hosted product is not operational and all data inaccessible. Data flow is completely stopped resulting in critical impact to the End User’s data.  No workaround is available. End User will require continuous availability of DeliverySlip contact until resolution of the error. For emergencies only outside of DeliverySlip normal business hours, emergency platform (such as the application appears to be down for other reasons than poor internet connectivity, etc.), Service Provider sends an email to or via phone to 1.877.404.9964 ext 7007 for emergencies. This email address and phone number are monitored 24 hours a day/7 days a week. Resources will be applied continuously until a solution or an acceptable workaround or fix is developed. Hosted product: Response time: 20 mins.

Resolution time for non-scheduled maintenance:

Immediate continuous efforts until resolution of the error.



Response time: 20 mins.

Recovery Time Objective (RTO): 8 hrs of DeliverySlip successfully reproducing the error using the supplied test case.

Recover Point Objective (RPO): 1 hr of DeliverySlip successfully reproducing the error using the supplied test case.

2 Product is operational, but code changes are required in order to have a complete solution.  End User still has access to secure messages through Web Application however may have some limited functionality through other applications. No workaround is available in the affected applications.


DeliverySlip resources applied continuously, during normal business hours, until a workaround or fix is developed. Response time: 1 hr.


Resolution time: Within five (5) business days of DeliverySlip successfully reproducing the error using the supplied test case.

3 Product is operational with functional limitations or restrictions that are not critical to the overall End User operations. DeliverySlip resources applied on an as available basis until a work-around or fix is developed. Response time: 1 hr.


Resolution time: Next update or upgrade released by DeliverySlip within 90 days.

4 Low or no impact errors with Product usage, implementation, performance or any other inquiries. Answer generic questions or provide path to answers within reasonable time frames.   Update or upgrade requests will be reviewed and implemented in the next update or upgrade release, where feasible, or to meet specific commitments made. Response time: 24 hrs.


Resolution time: Within fifteen (15) business days for generic questions.  Update or upgrade requests are processed on a case-by-case basis.


Service level guarantees for the Product will be provided by DeliverySlip to Service Providers or direct contracting clients only, and are not extended directly to End Users in accordance with the terms set forth in this Policy.


DeliverySlip shall provide 99.9% network uptime for the DeliverySlip operated Product over each contract year. Should access to the DeliverySlip operated Product through the Internet become unavailable for a sustained period of one hour or more, Service Provider shall receive a refund equivalent to one day of every affected Service Provider Pro User’s pro-rated charges for that month for every full hour of downtime to the extent that such downtime falls below such 99.9% guarantee. All refund calculations shall be based on unavailability in one-hour increments. This SLA does not cover outages caused by equipment and/or events not under the direct control of DeliverySlip, including any third party hosting service, or caused by individuals not directly employed by DeliverySlip. This provision does not cover outages due to scheduled or emergency network and/or facility maintenance, which shall be broadcast to all Service Provider at least 7 days in advance for planned maintenance and as soon as practicable (using commercially reasonable efforts to provide 24 hours’ notice) for emergency maintenance, including maintenances deemed non-disruptive. This provision does not cover outages or downtime where the Internet from the Pro User to the DeliverySlip operated Product is unavailable or where the cause is due to a loss of connection from the Pro User or the Pro User’s service provider.

Any and all refunds to Service Provider, whether under this or any other guarantees described in this Policy, shall not exceed 50% of each impacted Pro User’s total monthly charges for that month. No refund is available for latency or interrupted services where the circumstances are beyond DeliverySlip’ control or for acts of God, earthquake, fire, flood, denial of service attack, etc.


  • Accessibility of the DeliverySlip services. During Schedule Maintenance, DeliverySlip servers and services may be available, but User access may not be available
    • Normal scheduled maintenance (“Normal Maintenance Window”) occurs at least one evening per week.
    • The Normal Maintenance Window may occur on Thursday evenings between the hours of 7:00 PM – 9:00 PM PST. This is subject to change at DeliverySlip’s sole discretion, and the new Normal Maintenance Window will become effective upon an update to this SLA.
    • Quarterly scheduled maintenance (“Quarterly Maintenance Window”) occurs once per calendar quarter on the second weekend of the last month in the quarter.
    • The Quarterly Maintenance Window may occur on the second weekend of the last month in the quarter between the hours of 10:00 AM – 6:00 PM PST on both Saturday and Sunday.
  • Infrastructure Maintenance includes all DeliverySlip components, including server(s). During Infrastructure Maintenance, the DeliverySlip server and other Services may not be available and is not included in the calculation of uptime guarantees.
  • Scheduled maintenance does not count as downtime and is not included in the calculation of the uptime guarantees.
  • If DeliverySlip intends to perform scheduled maintenance outside of the Normal Maintenance Window or Quarterly Maintenance Window, DeliverySlip will post notice to DeliverySlips’ web site twenty-four (24) hours before initiating.


  • DeliverySlip has the right to perform emergency maintenance if there is an immediate, material threat to DeliverySlip Servers or to DeliverySlip services.
  • DeliverySlip will attempt to update web site prior to emergency maintenance, but notice depends upon the severity and critical nature of the emergency maintenance.
  • Emergency maintenance does not count as downtime and is not included in the uptime guarantee calculations.


DeliverySlip shall maintain its network in such a manner as to provide to Service Provider and Pro Users the best possible performance of the DeliverySlip operated Product. In order to achieve this DeliverySlip makes the following guarantees to Service Provider:

The internal DeliverySlip network shall have an average latency of not greater than 1ms over a period of greater than one hour
If the average latency, within the internal DeliverySlip network, is greater than 1ms for a sustained period of one hour or more, then Service Provider shall receive a refund equivalent to one day of every affected Pro User’s pro-rated charges for that month for every full hour of downtime. If the average latency, overall, is greater than 5ms for a sustained period of one hour or more, then Service Provider shall receive a refund equivalent to 10% of every Pro User’s pro-rated charges for that month for every hour of downtime.


The DeliverySlip network is monitored twenty-four hours a day, seven days per week from DeliverySlip Operations Centers. Service outages automatically trigger alarms that are processed and resolved by DeliverySlip technical staff. A problem ticket is opened in the trouble ticketing system for alarms that cannot be resolved immediately. Established escalation procedures based upon the severity of the problem are used to direct the issue through the operations and / or development organizations. DeliverySlip operations can be contacted directly by phone or through email. DeliverySlip data centers are located at facilities that provides 24-hour physical security, palm print and picture identification systems, redundant electrical generators, redundant data center air conditioners, and other backup equipment designed to keep servers continually up and running.

The network perimeter is protected by multiple firewalls and monitored by intrusion detection systems — all sourced from industry-leading security vendors. Regular monitoring of firewall logs proactively identifies security threats. Inside of the perimeter firewalls, the systems are safeguarded by network address translation and port redirection.

DeliverySlip enforces tight operating system-level security by using a minimal number of access points to all production servers. DeliverySlip protects all operating system accounts with strong passwords, and production servers do not share a master password database. All operating systems are maintained at each vendor’s recommended patch levels for security and are hardened by disabling and/or removing any unnecessary users, protocols, and processes.

Database access is controlled at the operating system and database connection level for additional security. Access to production databases is restricted to a limited number of points, and production databases do not share a master password database.

All Pro User data is stored on carrier-class disk storage using RAID disks and multiple data paths. All Pro User data is owned by the Pro User.

In addition to the above performance guarantees, DeliverySlip will take all possible measures to insure Pro User traffic reaches the DeliverySlip operated Products in a timely fashion comparable and within reason to any other SaaS product provider. These measures include the manipulation of routing tables so as to direct product access to using its best possible upstream link.

This SLA does not apply to situations where a Pro User is in violation of Service Provider’s EULA. Use of the Product constitutes acceptance of this SLA. This SLA may be updated at any time by DeliverySlip with the written consent of Service Provider. Such modifications may include, but are not limited to, upgrades to the network and network components.


The parties agree that it is DeliverySlip’ responsibility to monitor the guarantees given in this SLA, though it may act upon information received from Service Provider in that regard. Service Provider may not undertake any automated monitoring, probing, or testing of the DeliverySlip systems or services in order to determine compliance herewith or to detect outages without DeliverySlip’ prior written consent. The purpose of obtaining such consent is to ensure that the methods proposed by Service Provider to such testing do not unduly interfere with the operation of DeliverySlip’ systems and services. For greater certainty, any such unauthorized monitoring by Service Provider (or any Reseller, Pro User or End User licensed to use the Product directly or indirectly through Service Provider) of DeliverySlip’ systems or services will constitute a material breach of this Agreement.


DeliverySlip may make changes to the Policy from time to time, without notice to you. When such changes are made, DeliverySlip will make a new copy of the Policy available by publishing the updated Policy through the Services.

You understand and agree that you are responsible for regularly reviewing the Policy in order to obtain timely notice of any such updates, and that by continuing to use the Services after the date on which the Policy has changed, you will be deemed to have accepted any changes to the Policy.

Last Updated: 27 SEPT 2017