Privacy Policy

Scope

Twinevia provides a business messaging service to approved organizations. This policy applies to visitors, pilot applicants, account users, and the business information processed when customers use Twinevia. A customer organization may have its own privacy obligations and policies for recipients whose data it submits to the service.

Information we collect

Information you provide

We collect pilot-application details such as organization name, contact name, email, optional phone and website, messaging use case, expected volume, and provider-account status. Approved customers also provide account, organization, registration, policy-acceptance, billing, and support information.

Messaging information

When an organization uses Twinevia, the service may process recipient phone numbers and names, audience records, message content, schedules, consent or suppression records, delivery attempts, provider identifiers, replies, survey responses, and usage totals. The organization controls the purpose and recipients of its messages.

Technical and transaction information

We collect security and operational information such as IP-derived intake records, user agent, authentication events, timestamps, session and audit records, queue and delivery state, and error details. Stripe handles payment-card entry; Twinevia stores transaction and customer references needed to verify billing rather than full payment-card numbers.

How we use information

• Review pilot fit and communicate about onboarding.
• Create and administer approved organizations and user access.
• Provide messaging, inbox, registration, usage, billing, and support functions.
• Apply suppression, consent, entitlement, security, fraud, and abuse controls.
• Reconcile provider and payment events, investigate failures, and maintain audit records.
• Protect, troubleshoot, improve, back up, and recover the service.
• Meet legal, regulatory, carrier, and provider obligations.

How information is shared

We disclose information only as needed to operate the service, follow customer instructions, protect Twinevia and others, or comply with law. Operational recipients may include:

• Messaging providers and carriers, including Twilio and downstream networks, for number provisioning, registration, sending, receiving, and delivery status.
• Payment providers, including Stripe, for Checkout, subscriptions, invoices, payments, and the customer portal.
• Infrastructure and professional providers supporting hosting, storage, monitoring, security, backup, legal, and accounting functions.
• Authorities or affected parties when reasonably necessary to comply with law, enforce policies, or address fraud, abuse, security, or safety.

Twinevia does not sell personal information for money. We do not use recipient message content for third-party advertising.

Choices, access, and retention

Customers can manage many workspace records through the service and may request assistance through the Contact page. Message recipients should first contact the organization that sent the message and may use recognized opt-out keywords such as STOP. We retain information for as long as reasonably necessary to provide the service, maintain security and transaction records, meet legal or provider requirements, resolve disputes, and complete controlled backup retention. Deletion requests may be limited by those obligations.

Security

Twinevia uses administrative, technical, and operational safeguards intended to protect information, including tenant-aware access, role controls, session protections, encrypted storage for customer-managed provider credentials, request validation, provider webhook checks, audit records, backups, and recovery procedures. No internet service can guarantee absolute security.

Contact and changes

Twinevia is a service of IT Wingman LLC. Submit privacy questions through the Contact page. We may update this policy as the service, law, or provider requirements change. A revised effective date will identify the current public version, and approved customers may be required to accept a new version before continuing to use chargeable features.