Data retention and deletion

Back to Security Retention periods depend on the type of data. Deleting a meeting, deleting an account and cancelling a plan have different effects. Use the tables below to find the action you need. An item may disappear from the app before its stored files are erased. Cleanup runs in the background and may need retries or support review. This delay does not provide an in-app recovery period. Export anything you need before deleting it or its retention period ends.

​

Automatic retention periods

These periods determine when data is eligible for automatic cleanup. They do not guarantee availability for the full period or immediate deletion at its end. Earlier deletion, plan settings and contract terms may apply. Month-based periods follow the calendar, rather than a fixed number of days. Editing or opening a transcript does not restart its retention period. Audio can expire while the text remains; video expiry does not delete a separate audio file or transcript. Message expiry can leave related usage or speech-analysis records. The Privacy Policy sets a maximum of 3 months for conversation-history audio, depending on plan and settings. The backup guidance below does not extend that commitment.

​

Delete a meeting, bot session or upload

Use the delete control for the relevant item. Available actions depend on ownership and workspace permissions. The 30-day delay applies to manual deletion of ordinary transcripts and recordings. Automatic expiry does not add another 30-day wait. Deleting a saved transcript does not remove all original uploads, subtitles or dubbed media; delete the upload or job separately. See Meeting Logs, Web Meeting Bot and File Transcribe for the controls.

​

Accounts, workspaces and shared data

You cannot delete your account while you are a workspace manager. Change that role first. See Account Settings and Member Management. Deleting a persistent whiteboard, editor or other virtual-office object normally hides it first. Cleanup of its owned content and attachments becomes due after 30 days; files referenced elsewhere are preserved. Room or floor deletion can remove resources through a different process. Removing a custom object from the catalog does not necessarily remove copies already placed in floors, templates or editing history.

​

Dictionaries and voice registration

Deleting a Vocabulary Builder source or session does not delete terms already added to a dictionary. Remove those terms separately. Deleting a voice registration for speaker identification applies to the selected language. It requests recording removal and takes that registration out of active use. Other language registrations, existing meeting text and speaker labels can remain. This action does not confirm physical erasure of every related identity or historical record; request personal-data deletion for that broader scope.

​

Recordings and copies on your devices

Use Delete in offline history to remove a saved local transcript and its audio on each device. Cloud deletion, signing out, quitting the app, switching accounts or removing a speech model does not clear offline history. If deletion reports an error, check the result and retry. Recovery recordings from interrupted online capture can remain while an upload is pending or has failed. Deleting a local recovery recording does not delete a copy already uploaded to the cloud. Downloads, exports, operating-system backups and files shared with other people need separate deletion. If you enabled saved diagnostic logs, use their delete or clear control; older sessions can remain after sign-out.

​

Backups, logs and copies sent elsewhere

Processing files, translation caches, job history and operational logs have separate cleanup rules. Some contain content or identifiers. Temporary files from successful processing are cleaned up after results are handed back; unfinished or failed work may stay for recovery. Routine rules include 7 days, 30 days or one calendar month, with exceptions for active or referenced records. These are not deadlines for every copy. Backups and archives also have separate lifecycles. Losing playback access or deleting an entry does not confirm that every copy is gone. Include backups and archives in a privacy request if you need that confirmation. Support, billing, security-investigation and appeal records are handled for their own purposes under the Privacy Policy and applicable law. Account deletion does not automatically erase them. A hashed identifier is not necessarily anonymous. VoicePing cannot recall a downloaded transcript, delivered email summary or copy sent to an integration, API or MCP client. Disconnecting a service or revoking a key stops future access within that control’s scope; delete earlier copies through the receiving service.

​

Request deletion of personal data

Contact support and identify the account or workspace, affected feature and data you want deleted. Include retained copies if relevant. VoicePing may verify your identity and authority. Do not send passwords, verification codes or API keys. Under Privacy Policy Articles 10 and 10-2, personal data is deleted within 30 days of a valid deletion request, unless applicable law requires retention. The policy also covers deletion or irreversible anonymization of relevant identifiers in logs. Product cleanup schedules do not replace this commitment or your statutory rights; formal requests remain separate from ordinary account-deletion assistance. Ask for confirmation of what was deleted, what must be retained and why, and how retained copies are handled. This guide explains product behavior; the Privacy Policy, your service agreement and any applicable Data Processing Agreement continue to govern.