Privacy Policy

Last updated: May 25, 2026

This draft policy is provided for product launch preparation and should be reviewed by qualified legal counsel before public release.

Information We Collect

Voice Invoice Pro may process business account information, tenant branding settings, technician activity, customer names, customer email addresses, phone numbers, service addresses, invoice line items, tax amounts, signatures, delivery method, sync status, and payment status.

Voice and Audio Processing

When voice invoicing is used, audio may be sent to a transcription or AI processing provider to convert spoken job details into invoice data. Audio is used to provide the requested feature and improve invoice accuracy. Do not dictate sensitive information that is not needed for the invoice.

Offline Device Storage

The mobile app stores draft and completed invoices locally so it can continue working in weak signal areas. Queued sync and email requests are sent to the backend when connectivity returns.

Payments

If payment links are enabled, payment processing is handled by a payment provider. Voice Invoice Pro should not store full card numbers. We may store invoice payment status, provider references, and payment-link metadata.

How We Use Information

• To create, sign, email, print, save, and sync invoices.
• To operate tenant accounts and white-label branding.
• To provide support, troubleshoot errors, and prevent abuse.
• To generate business reports, exports, and operational summaries.

Service Providers

Voice Invoice Pro may rely on hosting providers, database infrastructure, SMTP/email providers, transcription or AI providers, analytics providers if configured, and payment processors if enabled.

Retention and Deletion

Invoice and account data is retained while needed to provide the service, meet business obligations, resolve disputes, and comply with legal or accounting requirements. Businesses may request deletion or export of their data, subject to lawful retention requirements.

Security

We use tenant API authentication, server-side secrets, database access controls, and admin session controls. No internet-connected system can be guaranteed perfectly secure, but production deployments should use HTTPS, restricted CORS, strong passwords, backups, and monitoring.

Contact

Questions about privacy can be sent through the contact page.