Document status
Effective August 8, 2026. Provider and privacy details updated October 8, 2026. LineSquire is a service of Upmarketers LLC. These terms and policies apply to the service, including trial and paid enrollment made available through Stripe.
How to read this list
This list identifies external providers that receive information to operate LineSquire. A provider can act as a processor, independent controller, or other service provider depending on the data and applicable law.
Upmarketers LLC reviews provider access and limits shared data to the service being supplied. Material provider changes will be reflected on this page and communicated when required by law.
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.
Inworld
Inworld supplies realtime speech recognition and speech synthesis for the LineSquire assistant, including the optional public browser demo and fixed-phrase voice previews. Its language-model routing service connects assistant responses and separate task-safety review to the selected model service described below.
- Data involved
- Call audio, voice-session instructions, session metadata, transcripts or model events, and tool-call context limited to the active call.
- Current boundary
- Local deletion and LineSquire retention controls do not by themselves delete Inworld-held content or change Inworld's retention or training settings. Information is handled under the applicable Inworld service terms and settings; no content-retention or training exclusion is promised here.
Language-model services through Inworld
The selected GPT models are supplied by OpenAI through Inworld. These models produce assistant responses and perform a separate task-safety review. Model services receive the request content routed to them; they are not merely phone carriers.
- Data involved
- Assistant instructions, conversation text, approved call context and tool interactions needed for a response. The separate task-safety review receives sanitized task text, not subscriber identifiers or protected fact values.
- Current boundary
- Local deletion does not establish deletion by Inworld or OpenAI. Their applicable service terms and settings govern provider-held content, retention and training use. A retention setting for an Inworld-hosted model does not establish the same handling by a third-party model service.
Hume (historical sessions)
Hume is not selected for new voice sessions in this release. Voice sessions previously processed by Hume used content retention enabled and provider training use disabled. These historical settings do not describe Inworld or the selected language-model services.
- Historical data boundary
- Prior call audio, session instructions, transcripts, model events and tool-call context may remain subject to Hume's applicable retention settings and obligations. Local deletion does not by itself establish deletion of historical provider-held content.
Didit
Didit supplies hosted identity verification when a subscriber requests access to outbound calling.
- Data involved
- Identity documents, verification images or video, liveness and matching results, session metadata, and decision status supplied through Didit's hosted flow.
- Current boundary
- LineSquire sends a pseudonymous account reference and retains only encrypted session identifiers, minimal decision status, warning codes, and audit history after webhook processing. It does not retain provider document images or extracted identity fields in subscriber records. Account deletion invokes the provider deletion workflow and verifies session absence before local tombstoning.
Stripe
Stripe 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 Stripe-hosted surfaces. LineSquire receives billing identifiers and payment status, not full card credentials.
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
Questions about a provider or this notice can be sent to support@linesquire.com. The current list is updated when a provider is added, replaced, or removed.
Questions about this policy
Contact support@linesquire.com. Do not send passwords, payment credentials, security codes, or unnecessary call content by email.