Your voice is sensitive. We treat it that way.

VoicePort may process writing samples, uploaded documents, customer-submitted URLs, public social captions, transcript exports, phone conversation transcripts, SMS consent replies, call scheduling requests, phone numbers, and the generated voice.md artifact.

We treat that material as customer-owned source data. The product should collect only what it needs, send only the context required for generation or voice transport, and avoid retaining raw material longer than the customer-facing retention promise allows.

If VoicePort or an approved VoicePort assistant uses text messages or phone calls to coordinate with you, we may process your phone number, message content, opt-in and opt-out replies, preferred call times, call status, call recordings, transcripts, and support metadata needed to deliver the service.

We use this mobile information to send requested service messages, coordinate calls, respond to support requests, comply with opt-out obligations, troubleshoot delivery, and maintain abuse-prevention records.

We do not sell, rent, or share mobile opt-in data or SMS consent information with third parties or affiliates for their marketing or promotional purposes. We may share phone and messaging data with service providers, such as communications carriers, hosting providers, customer support tools, and security vendors, only as needed to operate VoicePort and comply with law.

You can opt out of SMS messages by replying STOP. You can request help by replying HELP or contacting hello@voiceport.co.

The Starter product can be short-retention: create the voice.md file, deliver it, support the order, then delete or redact raw source material on the published schedule.

The goal is not to ask you to believe VoicePort is impossible to compromise. The goal is to avoid keeping more sensitive raw material than the product needs.

Some future upgrades, such as refreshes, team files, agent-ready exports, and quarterly updates, work better if VoicePort keeps a saved history. That retention should be a visible customer choice, not a hidden default. You should be able to use fresh material instead.

VoicePort uses specialized providers for storage, AI generation, calls, payments, email, and analytics. Those providers should receive the minimum data needed for their job. Payment tools do not need your writing. Analytics tools do not need your voice.md. Call transport does not need unrelated account history.

Before broad customer testing, provider accounts must be VoicePort-owned, isolated from unrelated businesses, and reviewed for model-training, retention, logging, deletion, access-control, and encryption behavior.