Alpha privacy notice
Alpha notice · 4 November 2026
VoiceAssist LLC runs this free, invite-only alpha. Contact support@voiceassist.live about your data or account.
What your assistant stores
Your account has its own virtual machine. Conversations, transcripts, artifacts, settings, connected-service credentials and model keys are stored there. We do not automatically save raw audio from live voice calls. Audio files you choose to send are stored as conversation artifacts. Transcripts and voice context can persist according to the assistant’s retention settings.
Who can access it
Hosting operators can technically access your VM and its data. OVHcloud hosts the physical machine. VM isolation and encryption do not mean operators cannot access data while your assistant is running.
Your browser and phone establish TLS with your assigned assistant VM. The shared entry service routes that encrypted connection and handles account authorization. It does not terminate the assistant connection’s TLS.
The private SSH pilot uses a trusted browser proxy that can inspect assistant traffic. Public encrypted assistant access is a separate mode.
AI providers and connected services
The model you select receives the request and relevant conversation or tool context needed to answer. Voice providers process live audio. Provider retention and training terms depend on the provider account and feature; this alpha does not promise zero retention. Before enabling a funded provider on your account, the operator identifies that provider and its applicable terms. Connected services receive the actions and data needed for the tools you choose.
Accounts and operational records
The shared account service stores your username, password verifier, immutable account identifier, assigned VM, invitations and session authorization. Operational records include service health, usage/cost totals, backup dates, durations and verification results. Backup records exclude conversation contents, filenames and credentials. We use no advertising trackers, analytics or third-party fonts on this site.
Backups and recovery
Each user VM has independently encrypted backups on rsync.net and its own recovery key. Backups run every six hours and are downloaded and checked after creation. Normal retention keeps all recovery points for seven days, then daily, weekly and monthly recovery points for up to roughly three months. Current evidence is available to your assistant through its backup-status tools. A successful backup does not guarantee zero data loss or uninterrupted service.
Export, deletion and support
These operations are assisted by the operator during alpha. Contact support from your signed-in account or complete the operator’s identity check. We prepare an encrypted export through a private delivery channel. For deletion, we verify ownership, revoke account access, stop scheduled work and remove the live VM. Independently encrypted backups and their recovery material are retained until a scheduled purge three calendar months after deletion. We confirm live-data removal and the backup expiry date, then confirm the backup purge separately. Deleted accounts are not reactivated from older backups. Minimal security/audit records may remain after review.
Do not send passwords, private keys, recovery keys or sensitive conversations in ordinary feedback email. Describe the problem and approximate time; the operator can arrange a private way to investigate.