Skip to main content
Velor

Enterprise IT guides

What you get when you leave

How to take your data, what is and is not in the export, and what deletion removes and keeps.

For customers and their procurement reviewers. Every statement here is checked against the product by apps/web/scripts/leave-doc-matches-code.test.ts; the contractual terms are the Data Processing Agreement, section 11 (Return and Deletion). If this page and the DPA differ, the DPA controls.

1. Taking your data

Who can ask: the workspace owner, from Settings, Data, "Request full export". It works after your plan has ended or been cancelled; ending a subscription does not lock you out of your own export. (Owners only: the export contains every conversation in the workspace, so it is not available to admins or agents. A fresh sign-in is required.)

What you receive is an email with links to three files:

  1. The main export (JSON, machine-readable): conversations and their messages, visitor records and visitor memory, knowledge-base sources, action invocation audit records, and the audit log. Files attached to conversations and uploaded to the knowledge base are delivered as links.
  2. The same sections as plain text, laid out as CSV blocks, for people who would rather open it in a spreadsheet.
  3. Your organization content (JSON): everything you built or that is about your own conversations: - agents and their configuration - agent version snapshots - agent drafts - agent configuration versions - agent configuration revisions - prompt text - action definitions (signing secrets are never exported) - workflow definitions - procedure definitions - procedure run summaries about your conversations - routing rules - routing configuration - phone menus - voice style notes - phone numbers and style notes (provider keys are never exported) - calling-compliance settings - single sign-on attribute mapping - webhook destinations (secrets are never exported) - connector configuration (credentials are never exported) - knowledge text as indexed (vector embeddings are not exported) - knowledge source version history - help-center articles - reply templates - brand voice guides - brand voice examples - campaign copy - agent skills - customer records - CRM events received for your contacts - knowledge-base findings drafted from visitor feedback - quality scores for your conversations - billable-resolution records - proposals drafted for you - analytics proposals about your agent - sandbox test messages - sandbox replay results - invoices - the legal entity name, billing address, tax ID and PO number printed on your invoices

How long you have: we deliver an export within 15 business days of your request (an owner can also generate one at any time from Settings, Data), as JSON over a signed link that is valid for 7 days. The workspace's data is preserved for 30 days after termination so you can ask (DPA 11). If a table cannot be read, the export is refused, not delivered partially: you will never receive a file presented as complete that is missing a section.

2. What is not in the export, and why

  • Credentials and secrets, always. Any column that could hold a password, API key, signing secret, token or private key is dropped from every row of every table, by name, so a new secret-bearing column is dropped before anyone has to remember it. You will need to re-issue integration credentials wherever you move to.
  • Vector embeddings. They are derived from your text and are not portable; the text is exported.
  • Three internal records, which are Velor's or one user's, not your content:
  • platform marketing content written by Velor (case studies)
  • Velor staff's own record that an operator paused this workspace's agent (you are told by email when that happens)
  • one user's notification settings for their own browser (quiet hours, whether message text may show on the lock screen)
  • Data held by other companies. Call recordings are held by Twilio; email delivery logs by Resend; payment records by Stripe; model providers keep what their terms say. Our deletion asks Twilio to delete the recordings of your calls (see below); the rest is governed by those providers' terms and our sub-processor list (/subprocessors).

3. Deleting your data

Two ways:

  • You, any time: the owner uses Settings, Data, "Account deletion" and types the workspace's short name (its slug) to confirm. It is irreversible. Take your export first.
  • Us, on termination: on your written request we delete your data from primary storage within 15 business days and confirm it to you in writing; when an owner deletes the workspace, deletion starts immediately and the owner is emailed a confirmation. Velor does not delete automatically at the end of the 30-day window, so ask if you want it. Copies in routine backups are overwritten on the backup providers' retention cycles (DPA 11).

What deletion does. It removes your files from private storage (conversation attachments, knowledge-base uploads, workspace assets, evaluation datasets), asks Twilio to delete your call recordings, and then deletes the workspace. Every table that holds your data is keyed to the workspace and is removed with it, checked automatically against our database definitions on every change (see the next section for the exceptions).

What survives deletion, by design:

  • Payment-provider event records about your account (billing events), kept as billing evidence. They are detached from your workspace and contain no visitor data.
  • A platform write log used for security and operations; it carries a workspace identifier as a label only and holds no conversation content.
  • The record that the deletion happened (the request and its completion), as proof it ran.
  • Anything the law requires us to keep, and only for the narrow category and period so required (DPA 11).

4. What we cannot promise from the code alone

Fifteen internal tables were created in production before our migration tooling and are not defined in our repository, so whether each is removed with the workspace is confirmed against the live database, not by an automated check. We confirm the result in the written deletion confirmation. If you need a specific category confirmed (for example "customer records" or "agent drafts"), ask and we will state it.

In the product: /dashboard/settings/data (sign-in required).