> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Retention & Deletion

> How long Voxworks keeps different kinds of account data, how to export it before it ages out, and how to raise a privacy complaint.

## Overview

Voxworks keeps personal information only for as long as it's needed for the purpose it was collected for, or as required by law — consistent with the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth). In practice this means two different patterns:

* **Automated retention windows** — some operational data (automation execution logs, in-app notifications) is deleted automatically by a scheduled cleanup job once it passes a fixed age.
* **Retained until you act** — most of your working data (calls, contacts, scripts, custom variables, batches) is kept for as long as your account is active and you haven't deleted it yourself. Deleting it, or deleting your account, is what starts its removal.

This page covers what's automatically purged and when, how to export data before it's gone, the paths available for deleting data yourself, what Voxworks commits to in the Terms of Use and Privacy Policy, and how to escalate a privacy complaint to the regulator.

***

## Retention windows by data type

| Data type                                                            | Retention window    | What happens after                                                                                                                                                                                                       |
| -------------------------------------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Automation execution log entries                                     | 90 days             | Hard-deleted by a scheduled cleanup job. The execution's trigger payload and per-step results can contain customer data pulled from CRM or webhook payloads, so this window limits how long that data sits in your logs. |
| Notifications — informational and success<sup>†</sup>                | 30 days             | Automatically deleted once expired.                                                                                                                                                                                      |
| Notifications — warning<sup>†</sup>                                  | 90 days             | Automatically deleted once expired.                                                                                                                                                                                      |
| Notifications — critical<sup>†</sup>                                 | 90 days             | Automatically deleted once expired *and* acknowledged. An unacknowledged critical notification is kept regardless of its expiry date — an unread emergency alert is never silently aged out.                             |
| Calls, recordings and transcripts                                    | Not yet finalised   | Retained for as long as your account is active and the data is needed to provide the platform to you. Voxworks does not yet apply a fixed automatic deletion window to call recordings.                                  |
| Contacts, custom variables, scripts, batches, and other working data | No automatic expiry | Kept until you delete the individual record yourself, or until your account or team is deleted.                                                                                                                          |

<sup>†</sup> Notifications (the bell, Activity feed, and Notification Created automations) are currently in **beta, available to selected invites only**. Reach out to the Voxworks team if your team is interested in joining.

A few things worth knowing about the automated windows:

* Automation execution logs have no export option in the app. If you need a step's result data beyond 90 days, capture it yourself — for example by writing it to a custom variable, or sending it to your own system through a **Destination** step — before it ages out. See [Execution Log](/automations/execution-log) for what the log shows while it's live.
* API keys, tokens, and other credentials referenced by your tools and integrations are stored encrypted rather than time-limited — see [Integrations Overview](/integrations/overview) for how connections and their stored credentials work.

***

## Exporting data before it's deleted

Several table pages in the app let you download your own data as a file, and downloads respect whatever filters or row selection you currently have applied — so you can narrow to exactly what you want before exporting:

| Page                             | Formats   | Notes                                                                                                                                |
| -------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Calls                            | CSV, JSON | Download icon in the table toolbar; exports the selected rows if any are checked, otherwise every row matching your current filters. |
| Contacts                         | CSV       | Same toolbar pattern; pair with **Upload CSV** if you're re-importing elsewhere.                                                     |
| Custom Variables                 | CSV       | Available from the Custom Variables table toolbar.                                                                                   |
| Usage History (Settings → Usage) | CSV       | Exports your wallet or minute usage ledger for the selected billing period.                                                          |

There's no export option for automation execution logs or in-app notifications — export what you need from those before their retention window closes, using the approaches described above.

Deleting your account or a team is permanent and cannot be undone, so export anything you want to keep first. See [Deleting an Account or Team](/account/deletion) for exactly what's removed and the confirmation steps involved.

***

## Deletion paths

You can remove data yourself through the app in a few places:

* **Individual records** — contacts, custom variables, scripts, batches, and lists each have a delete action on their own row or detail view, usually behind a confirmation dialog that reads "This cannot be undone."
* **Bulk selection** — table pages with row checkboxes (Contacts, Custom Variables) offer a "Delete selected" action for removing many records at once.
* **Account or team deletion** — the account-level "Danger Zone" lets an owner delete their account and any teams they own outright. This immediately cancels active subscriptions and cannot be undone. Full mechanics — confirmation requirements, what happens to numbers and any remaining wallet balance — are covered in [Deleting an Account or Team](/account/deletion).

Deleting a contact, batch, or list hides the record straight away — it disappears from your view and from anywhere else the product reads on your behalf, rather than sitting around waiting to be purged. Scripts work differently: if a script's call flow is still in use elsewhere, deleting it is blocked until you remove those references, so nothing gets deleted out from under another script.

***

## What Voxworks commits to

The Terms of Use and Privacy Policy set out Voxworks' data-handling commitments alongside the retention behaviour above:

* **Purpose-based retention.** The Privacy Policy commits to storing personal information "for as long as it is needed for the purpose for which it was collected or as required by law."
* **You keep ownership of your data.** The Terms of Use confirm you retain all rights in the data you input and in call recordings and transcripts generated on your behalf; Voxworks holds a licence to use that data to provide, maintain, improve, and secure the platform.
* **Security measures.** Voxworks maintains industry-standard technical and organisational measures to protect your data against unauthorised access, alteration, disclosure, or destruction — see [Security & Compliance Overview](/security/overview) for the detail.
* **Breach notification.** If Voxworks becomes aware of an eligible data breach affecting personal information held in connection with the platform, it will comply with the Notifiable Data Breaches (NDB) scheme under the Privacy Act.
* **Access and correction.** You can ask Voxworks to access or correct personal information it holds about you by contacting **[admin@voxworks.ai](mailto:admin@voxworks.ai)**.

***

## Raising a privacy complaint

If you're concerned about how Voxworks is handling your personal information — including a possible breach of the Australian Privacy Principles — the Privacy Policy sets out a two-step path:

1. **Contact Voxworks directly.** Lodge your complaint in writing to **[admin@voxworks.ai](mailto:admin@voxworks.ai)**. Voxworks will investigate within a reasonable time and keep you informed of progress.
2. **Escalate to the OAIC.** If you haven't had a response within a reasonable time, or you're not satisfied with the outcome, you're entitled to lodge a complaint with the **Office of the Australian Information Commissioner (OAIC)** directly, at [www.oaic.gov.au](https://www.oaic.gov.au).

***

## Next Steps

* [Security & Compliance Overview](/security/overview) — data residency, encryption, and access-control commitments this page's retention rules sit alongside.
* [Deleting an Account or Team](/account/deletion) — the full account-deletion flow, confirmation steps, and what happens to numbers and wallet balance.
* [Execution Log](/automations/execution-log) — what the 90-day automation execution log shows while it's still live.