LineSquire
Current public policy

Privacy notice

Privacy notice

What LineSquire is designed to collect, why it is used, and where provider retention differs from local controls.

Effective policy

Applies to LineSquire

LineSquire is provided by Upmarketers LLC. This document describes the current terms or policy for the service.

Last updated August 8, 2026

Effective August 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.

LineSquire is provided by Upmarketers LLC in the United States. This notice explains how Upmarketers LLC handles personal information through the LineSquire website, accounts, calls, integrations, support, and billing.

Call data can concern both the subscriber and another participant. LineSquire is designed to use the minimum information needed to route a call, follow an approved task, produce a record, protect the service, and meet legal obligations.

The categories below depend on the features a subscriber uses. LineSquire should not request passwords, full payment-card numbers, bank credentials, Social Security numbers, or one-time security codes during calls.

  • Account data, including email address, authentication events, verification state, preferences, and support history.
  • Identity-verification data when outbound access is requested, including the hosted verification session, provider status, decision result, and limited warning or audit codes. Didit processes submitted identity documents and verification media on its hosted service; LineSquire does not retain copies of those documents or extracted identity fields in subscriber records.
  • Phone and call data, including assigned numbers, participant numbers, routing metadata, timestamps, call events, consent decisions, transcripts, summaries, outcomes, and usage.
  • Subscriber-provided contacts, rules, permitted facts, task plans, approvals, and integration settings.
  • Device, security, rate-limit, diagnostic, audit, and complaint information.
  • Browser-demo microphone audio, transcript events, and short-lived security data when a visitor chooses to try the call-screening demo. The demo does not require a phone number, account, or payment details.
  • Billing customer, subscription, checkout, invoice, and payment-status information when paid enrollment is enabled. Payment credentials remain on Stripe-hosted surfaces.

Information is used to authenticate the subscriber, provide call handling, enforce permissions, meter usage, deliver notices, investigate faults or abuse, respond to privacy requests, and maintain an auditable record of consequential actions.

LineSquire is designed not to sell call content or build advertising profiles from it. Analytics should use redacted or aggregated values rather than transcripts or raw audio.

DIDForSale supports phone-number and carrier routing, Hume supports realtime voice processing, Didit supports hosted identity verification for outbound access, Stripe supports hosted commerce when paid enrollment is enabled, and SMTP2GO delivers authentication and service email. The service-provider page describes the operational data boundary for each.

Information may also be disclosed when required by valid legal process, to protect people or the service, during a reviewed business transaction, or at the subscriber's direction. LineSquire does not sell call content or use it to build advertising profiles.

LineSquire local raw recording is off by default. Local transcript, summary, and recording settings are separate, and recording requires an explicit choice and retention period. Account controls are designed to support call deletion, export, retention changes, and account deletion workflows.

The public browser demo keeps its transcript only in the current page and does not write demo audio or transcript to LineSquire account storage. Hume still processes and may retain the voice session under the provider setting described below.

Deleting data from LineSquire does not by itself delete every provider-held copy. Hume retains provider-side voice-session content under its configured retention setting, with provider training use disabled. Account deletion requests also direct Didit to delete the associated verification sessions and provider user before LineSquire removes its encrypted identifiers. Stripe, DIDForSale, SMTP2GO, and other providers may retain records under their applicable settings, contracts, and legal obligations.

LineSquire retains account and call information according to the settings displayed in the account and removes or de-identifies it when it is no longer needed. Minimal records may remain for security, fraud prevention, legal process, billing, taxes, disputes, suppression, or proof that a deletion request was honored.

Subscribers can review call records, change local retention settings, export account data, delete individual calls, disconnect integrations, and request account deletion. Call recipients can report a call or request suppression through the public complaint form.

Privacy questions and requests can be sent to support@linesquire.com. Upmarketers LLC may verify identity before disclosing or changing account data and will respond within the period required by applicable law. Depending on location, a person may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information and to appeal a denied request.

Questions about this policy

Contact support@linesquire.com. Do not send passwords, payment credentials, security codes, or unnecessary call content by email.

Privacy notice | LineSquire