Security and compliance for Soft Phone workspaces

Unlike a purely web-based product, Soft Phone workspaces touch phone networks, call recordings, transcripts, messages, and often regulated sectors such as healthcare or financial services. Rules like GDPR and CCPA govern personal data; TCPA, state telemarketing laws, and carrier rules shape how you may call or text; industry frameworks (for example SOC 2 or ISO 27001) may be table stakes for your procurement team. DialQueue is built so you can implement strong operational practices: minimize data you retain, document consent, and keep an auditable trail of what the platform processed on your behalf.

DialQueue operates the Soft Phone platform and follows our published policies, but you decide how your team uses the workspace: who has number access, which lines record, how messaging is used, and which CRM or webhook integrations you connect. You remain responsible for lawful use, adequate agreements with your end users where required, and configuration that reflects your industry's rules. We are responsible for securing the service we provide.

We process account data, usage signals, and call- and message-related content as described in our Privacy Policy. Depending on features you enable, audio, transcripts, and messages may be handled by our infrastructure and by Providers you connect (including telephony partners such as Telnyx). Where we offer region or retention controls, use them to align with your data map and retention schedule. Enterprise customers may request a Data Processing Addendum (DPA) or similar schedules where appropriate for their jurisdiction.

Many teams ask whether they can use Soft Phone when Protected Health Information (PHI), payment card data, or other special categories are in scope. Supporting regulated workloads typically requires the right product configuration, approved subprocessors, and signed agreements (such as a Business Associate Agreement under HIPAA in the U.S. when PHI is involved). If you need a formal compliance package, contact us with your use case. We will work through feasibility, documentation, and any technical prerequisites with your security and legal teams.

Nothing on this page, and no default dashboard toggle, should be read as a blanket certification for your deployment; compliance is always system-wide and fact specific.

You must comply with applicable laws for recording calls, autodialed or prerecorded messages, SMS, quiet hours, and do-not-call registries. DialQueue helps you run shared numbers with clear history and controls; you are responsible for obtaining and documenting consent where the law requires it, including evidence retention intervals your counsel recommends.

Soft Phone stacks combine dialer, messaging, storage, and telephony. Each component may introduce its own terms, data handling, and regional availability. Review your providers' documentation with the same rigor you would apply to any enterprise phone system, and ensure your DialQueue configuration only routes data to services that meet your requirements. When you bring your own integrations, your relationship with that vendor supplements ours.

We support security and procurement reviews for qualified opportunities. If you need responses to vendor questionnaires, details on our control environment, or a roadmap conversation for certifications or geography-specific hosting, reach out with your timeline and scope.

Contact: support@dialqueue.com
Documentation: dialqueue.com