Security Policy | Snapcom

Security Policy

This policy describes how Snapcom protects the data our customers and partners trust us with, including call records, recordings, transcripts, messages, and the information we exchange with connected business systems.

Effective September 28, 2026. This policy applies to Snapcom LLC and should be read together with our Privacy Policy.

Scope and definitions

This policy applies to the systems, services, employees, and contractors that Snapcom uses to deliver its cloud business phone (UCaaS), business texting, call analytics, and related services, including integrations that sync call information to customers' business applications.

Customer Data means information that Snapcom processes on behalf of a customer in providing our services. It includes account and contact information, call detail records, voicemails, call recordings, transcripts, AI-generated call summaries, text message content, and data that we send to or receive from third-party platforms that a customer has connected to our services, such as a CRM.

Personal Data means any Customer Data that identifies or could reasonably be linked to an individual person.

Security program

Snapcom maintains a written information security program with administrative, technical, and physical safeguards designed to:

  • protect the security, confidentiality, and integrity of Customer Data and Snapcom systems;
  • protect against reasonably anticipated threats or hazards to that data and those systems;
  • prevent unauthorized access to or use of Customer Data; and
  • dispose of Customer Data securely when it is no longer needed.

A designated member of Snapcom management is responsible for the program. We review the program and this policy at least once a year, and whenever a significant change to our services, systems, or risk environment calls for it.

Access control

We limit access to Customer Data to the people and systems that need it to deliver, support, or secure our services.

  • Access is granted on a least-privilege basis and tied to each person's job responsibilities.
  • Each person uses a unique account. Shared administrative logins are not permitted where the system supports individual accounts.
  • Multi-factor authentication is required for administrative access to production systems, cloud management consoles, and internal tools that expose Customer Data.
  • Access is removed promptly when a person changes roles or leaves Snapcom, and access rights are reviewed periodically.
  • API keys, tokens, and other credentials, including those issued to us by integration partners, are stored in restricted locations, are not shared with unauthorized parties, and are rotated or revoked if we suspect they have been exposed.

Personnel

Employees and contractors with access to Customer Data are bound by written confidentiality obligations. They receive security and privacy training when they join, with refreshers at least once a year, covering topics such as phishing, password and device hygiene, handling of Customer Data, and how to report a suspected incident.

Encryption and data protection

  • In transit. Web portals, APIs, and integrations use TLS 1.2 or higher. Voice signaling and media are encrypted with TLS and SRTP where the phone, app, or customer network supports it.
  • At rest. Call recordings, voicemails, transcripts, backups, and other stored Customer Data are kept in storage that is encrypted at rest.
  • Minimization. We collect and share only the data needed for the service a customer has enabled. For integrations, we send only the fields required for that integration to work.
  • Non-production use. We do not use production Customer Data in development or test environments unless it is necessary to resolve a specific issue, and then only with access limited to the people working on it.

Infrastructure and network

Snapcom services run in secured data center facilities and with established cloud infrastructure providers that maintain physical access controls, environmental protections, and redundant power and connectivity.

  • Production systems are protected by firewalls and network segmentation, with management interfaces restricted to authorized networks and users.
  • Systems are configured from hardened baselines, and unnecessary services are disabled.
  • Security patches are evaluated and applied based on risk, with critical vulnerabilities prioritized.
  • We monitor our voice and messaging platforms for toll fraud, account takeover, and other abuse, and may restrict affected accounts or traffic to protect customers.

Applications and integrations

Software that Snapcom builds, including customer-facing apps and integrations with third-party platforms, follows secure development practices. Changes are reviewed before release, secrets are kept out of source code, and production and development environments are kept separate.

When we integrate with a partner's platform, we access it only with the credentials and permissions that the partner issues to us, we use those credentials only for the integration the customer has enabled, and we follow the partner's published security and usage requirements.

Monitoring and logging

We log administrative actions, authentication events, and access to key systems, and we monitor for activity that may indicate unauthorized access, misuse, or fraud. Logs are protected from unauthorized changes and kept for a period appropriate to their purpose.

Vendors and subprocessors

Snapcom uses carefully selected vendors to help deliver its services. These fall into the following categories:

  • cloud hosting, storage, and infrastructure providers;
  • telecommunications carriers and messaging providers;
  • speech-to-text and AI processing providers used for transcription and call summaries; and
  • customer support, ticketing, and business operations tools.

Before engaging a vendor that will process Customer Data, we evaluate its security practices. We require vendors by written agreement to protect Customer Data with safeguards at least as protective as those in this policy, and to use it only to provide services to Snapcom. A current list of subprocessors is available to customers and partners on request.

Backup and continuity

We back up critical systems and Customer Data on a regular schedule, store backups separately from the primary systems they protect, and periodically test that we can restore them. Our platform is designed with redundancy so that the failure of a single component does not interrupt service.

Incident response

Snapcom maintains a documented incident response plan. When we become aware of a suspected security incident, we act to contain it, investigate its cause and scope, and remediate it.

If we confirm unauthorized access to, or acquisition, use, or disclosure of, Personal Data in our care (a "Data Breach"), we will notify affected customers and partners promptly and in accordance with applicable law and our agreements with them. Our notice will include the information reasonably available to us about what happened and what we are doing about it, and we will cooperate with their efforts to meet their own notification obligations.

Retention and disposal

We keep Customer Data only as long as needed to provide our services, as configured by the customer (for example, call recording retention settings), as required by our agreements, or as required by law.

When a customer agreement ends, we delete or return Customer Data as that agreement requires. Copies in backup systems are removed through our normal backup rotation. When we retire storage media or equipment, we securely erase or destroy the data on it, or rely on our infrastructure providers' certified disposal processes.

Customer responsibilities

Security is shared between Snapcom and each customer. Customers are responsible for:

  • managing which of their users have access to our services and removing access when those users leave;
  • protecting their passwords, devices, and network equipment;
  • giving any notices and obtaining any consents required by law before recording calls, transcribing calls, or sending text messages; and
  • deciding which third-party systems, such as a CRM, to connect to our services, and managing access within those systems.

Legal and regulatory compliance

Snapcom complies with the data protection and privacy laws that apply to its services. As an interconnected VoIP provider, we also protect Customer Proprietary Network Information (CPNI) as required by Federal Communications Commission rules. Where we process Personal Data on behalf of a customer, we do so as that customer's service provider and follow the customer's documented instructions and our written agreements.

Changes to this policy

We may update this policy as our services, technology, and legal requirements change. When we do, we will post the updated version on this page and change the effective date at the top.

Contact us

To ask a question about this policy, request our subprocessor list, or report a suspected security issue or vulnerability, email security@snapcom.com.

Snapcom LLC
12444 Powerscourt Dr, Suite 270
St. Louis, MO 63131