Document status
Launch draft — not yet effective. This document describes intended product and operating boundaries. Qualified counsel must review and approve it before launch, and it does not create current service terms.
How to read this list
This is an operational service-provider list, not a final legal classification. Counsel must determine which providers are processors, subprocessors, independent controllers, or other service providers for each launch jurisdiction and contract.
Provider locations, transfer mechanisms, contract terms, retention periods, and advance-change notice must be completed before this page becomes effective.
DIDForSale
DIDForSale supplies local phone-number inventory and SIP carrier routing for LineSquire calls.
- Data involved
- Telephone numbers, signaling and routing metadata, carrier events, and call media in transit.
- Current boundary
- LineSquire uses separately tagged number assignments and a dedicated SIP target. Carrier records remain subject to DIDForSale's systems and terms.
Hume
Hume supplies the realtime speech and voice session used by the LineSquire assistant.
- Data involved
- Call audio, voice-session instructions, session metadata, transcripts or model events, and tool-call context limited to the active call.
- Current boundary
- Provider-side content retention is enabled and provider training use is disabled. Local deletion does not by itself establish deletion of provider-held content.
Creem
Creem supplies hosted checkout, subscription management, and billing webhooks if paid enrollment is enabled.
- Data involved
- Billing contact details, hosted-checkout information, product and subscription identifiers, payment status, invoice data, and provider event metadata.
- Current boundary
- Payment credentials are entered on Creem-hosted surfaces. Paid enrollment is not enabled in the current subscriber release.
SMTP2GO
SMTP2GO supplies delivery of sign-in codes and transactional service email.
- Data involved
- Recipient email address, message content, delivery metadata, and bounce or delivery status.
- Current boundary
- Email content is limited to authentication and service notifications; call transcripts are not intended to be placed in routine email notices.
Changes and questions
The effective notice must explain how provider changes are announced. Questions about this draft can begin at support@linesquire.com.
Questions about this draft
Contact support@linesquire.com. Do not send passwords, payment credentials, security codes, or unnecessary call content by email.