Privacy notice

This draft describes the intended LineSquire product and the current provider topology. It is not an effective privacy notice. Launch geography, operator identity, required rights language, and contact details beyond the support channel must be completed with counsel.

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.

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, Creem 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. Final legal bases and jurisdiction-specific disclosures require counsel review.

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.

Deleting data from LineSquire does not by itself prove deletion from every provider. Hume currently retains provider-side voice-session content under its configured retention setting, with provider training use disabled. Provider-held data follows the provider's settings and supported processes; the final notice must state applicable retention periods and request handling before launch.

Some minimal records may need to remain for security, fraud prevention, legal process, billing, taxes, disputes, or proof that a deletion or suppression request was honored. Final categories and periods require counsel approval.

Subscribers are intended to be able to 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.

Questions or requests can begin at support@linesquire.com. Identity verification may be required before LineSquire discloses or changes account data. Final response deadlines, appeal rights, and regional rights must be added for the launch jurisdiction.