Skip to content

docs: explain artifact retrieval with zero data retention - #1334

Open
dhruva-vapi wants to merge 4 commits into
mainfrom
dr/zdr-artifact-retrieval
Open

dhruva-vapi wants to merge 4 commits into
mainfrom
dr/zdr-artifact-retrieval

Conversation

@dhruva-vapi

@dhruva-vapi dhruva-vapi commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Description

Problem: Customers using ZDR need a short guide to find call data when recordings and transcripts are empty in Vapi.

Customers can use the existing ZDR page to understand what Vapi retains, where to retrieve their own recordings, transcripts, and logs, and what to check when data is missing.

  • Update fern/security-and-privacy/zero-data-retention.mdx with a compact retention table, storage prerequisites, retrieval locations, and four troubleshooting checks.
  • Keep one short note linking to the existing end-of-call report reference. Remove the detailed event comparison, payload inventory, generated filename table, and command example.
  • Link to the guide from fern/assistants/call-recording.mdx and use bucket-relative paths in its storage examples.
  • Explain explicitly why later API and Dashboard call records can have blank recording or artifact URLs even after delivery to customer storage. Point to storage lookup and saved live end-of-call reports, while separating blank URLs from disabled recording or upload failure.
  • Reuse the existing page and navigation entry. No navigation changes.

Since the first push, the guide remains 61% shorter (1,719 to 671 whitespace-delimited words, including frontmatter). It focuses on what ZDR retains, where to retrieve call data, and what to check when data is missing. The latest edit makes the missing-URL explanation explicit without restoring the detailed event comparison.

Behavior was checked against VapiAI/vapi at 1bf98e9ecd896437e174ab54a8f90a33884bff5d and the docs API schema. Examples use generic placeholders.

Testing Steps

  • Run pinned Fern 5.151.1 validation. Zero errors and 14 existing warnings (SDK route conflicts, site contrast, and the redirect check skipped without local Fern authentication).
  • Strictly validate all 10 JSON blocks across the changed pages.
  • Verify all 14 internal links, including heading anchors.
  • Run git diff --check and inspect the full PR diff.
  • Review the shorter copy for storage and ZDR accuracy and customer privacy.
  • Confirm GitHub Fern Check, Preview Docs, and Go/Python/TypeScript SDK previews and compilation pass for 7c8717b.
  • Inspect the missing-URL callout and surrounding storage guidance in the current-head preview. It renders clearly without restoring the detailed event comparison.

Human review remains required. Optional Lightsage evals require a custom eval selected for GitHub PRs. This PR changes documentation only.

@lightsage-app

lightsage-app Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

Lightsage docs evals

Lightsage could not queue docs evals for this PR.

Docs URL: https://vapi-preview-01a14596-777c-700a-9a4d-1e47b2ddaea6.docs.buildwithfern.com
Commit: 3141802
Reason: No custom evals are selected for GitHub PR evals. Open Lightsage > Custom Evals and enable the GitHub checkbox for at least one custom eval.

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

## Storage Configuration

<Note>
With Zero Data Retention (ZDR), Vapi does not retain call content or artifact URLs in the call record. Configure your own storage before the call to keep a copy. See [Find recordings, transcripts, logs, and metadata with ZDR](/security-and-privacy/zero-data-retention#find-recordings-transcripts-logs-and-metadata) for retrieval steps and troubleshooting.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Edit update: tightened the callout to two sentences and matched the link text to the destination heading.

Suggested change
With Zero Data Retention (ZDR), Vapi does not retain call content or artifact URLs in the call record. Configure your own storage before the call to keep a copy. See [Find recordings, transcripts, logs, and metadata with ZDR](/security-and-privacy/zero-data-retention#find-recordings-transcripts-logs-and-metadata) for retrieval steps and troubleshooting.
With Zero Data Retention (ZDR), Vapi does not retain call content or artifact URLs in the call record, so configure your own storage before the call to keep a copy. To retrieve files or troubleshoot missing data, see [Find recordings, transcripts, logs, and metadata](/security-and-privacy/zero-data-retention#find-recordings-transcripts-logs-and-metadata).

@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants