1888 Poshard Drive - Suite A

Columbus, IN 47203
V: 812 378 4100
F: 812 378 4502
E: success@tls.net
SINCE 1986
W: www.tls.net
CLOUD SERVICES  MANAGED SERVICES  DISASTER RECOVERY PLANNING  HOSTED PBX  SIP TRUNKING  DATA CENTER SERVICES

TLS.NET, Inc. Statement of CPNI Compliance

Purpose:
TLS.NET, Inc. records only such Customer information is necessary to adequately, clearly, and
correctly invoice clients for services which have been duly authorized and provided, and to monitor and
ensure that packet transmission standards meet telephony quality requirements of the client end-users.

Policy:
In serving clients within the fields of medicine, banking & finance, and education as well as those
within the SMB commercial market, the processes and standards of TLS.NET, Inc. have been reviewed
by clients within industries whose concerns for network privacy, security, and reliability are more
stringent than most. With the advent of each client’s due diligence audit, TLS.NET, Inc. has the
opportunity to measure itself in those critical areas.
In the process of providing client-requested products and services,TLS.NET collects and uses
information about the services being delivered. During that process we may collect non-public
information from clients resulting from their completion of applications, contracts, or the use of the
service itself. We prohibit the disclosure of any non-public information to anyone other than the client
or the client’s designated agent or authorized employee.
We restrict access to non-public information to TLS.NET employees whose job requires the access in
order to provide the services which have been requested. We maintain physical, electronic, and
procedural safeguards to ensure the integrity of all data within our control.

Procedures:
Packet transmission data is captured for quality review and purged upon completion of the test sampling.
Traffic detail for billing purposes is converted to electronically deliverable Portable Document Format
(PDF) files for delivery to the client to and/or retrieval by the end-user client.
The delivery of data in PDF file ensures that only employees of TLS.NET with appropriate login
credentials have access to digital network data from which the PDF is drawn.
Traffic data on the TLS.NET network is protected within Cisco routing devices (QoS enabled) located
behind tandem Cisco firewalls.
Stored Data is accessible only within 168-bit triple DES encryption.
Data is purged as it reaches the age of 90 days unless a prior written request has been received from an
agency of law enforcement or an entity possessing the legal authority to make such a request.

Let TLS.NET take care of it

Sign up to vote on this title
UsefulNot useful