Descript Review 2026: Privacy, AI Training, and Where the Documents Disagree

Last updated: August 15, 2026

Descript is a cloud audio and video editor. It transcribes uploaded media, lets an editor cut video by deleting transcript words, and runs generative features through models the user can select. This review covers one question: what Descript’s published documents establish about the handling of uploaded material. Editing quality, performance, and pricing are outside its scope.

Descript publishes a dedicated subprocessor page, a security page, a privacy policy, contract terms, help articles, and model documentation. Those sources contain a great deal of detail. They do not reconcile into one account of who handles what.

The verdict in one line: Descript discloses more than most buyers realize, across documents that contradict each other on vendors, human access, and deletion.

The document set

A buyer searching for Descript’s data handling usually lands on the security page. That page is written as an explanation. It walks through account data, media files, usage analytics, and voice cloning, naming a vendor for each.

Five other documents cover the same ground from different angles, and each carries information the others omit.

Compiled from the six named Descript document types, read 15 August 2026.

The subprocessors page is the fullest vendor inventory and the hardest to reach. At descript.com/subprocessors Descript maintains a table of roughly 48 rows, each with a vendor name, the internal team using it, a link to that vendor’s privacy policy, and a data region. It does not appear in the site footer navigation on any page read for this briefing, including its own. Its copyright line reads 2024 and its footer markup differs from the current site.

Every row on that table states a data region of US, apart from a single row reading New York. The privacy policy states the same thing in prose: Descript is based in the United States and processes and stores information there. Two independent documents agree, so a buyer needing European processing has a clear answer.

Sources: Descript, accessed 15 August 2026 · Descript, accessed 15 August 2026 · Descript Privacy Policy, 14 April 2025

A model name is not a processor

Descript shows model names in two places. The Underlord co-editor has a selector carrying Claude, GPT, and Gemini names. Generative media has a separate reference listing models attributed to Google DeepMind, Black Forest Labs, OpenAI, PixVerse, Kling, and others.

Those labels state which model family Descript says powers a feature. They do not state how Descript serves it.

Descript’s own documentation supplies the counterexample. The security page describes Whisper as an open-source transcription model hosted inside Descript’s infrastructure. OpenAI released Whisper. Naming OpenAI as the processor for a Whisper transcription would be wrong.

The subprocessors page makes the distinction concrete in the other direction. It lists OpenRouter, a routing service that sits between an application and multiple model providers. It lists Baseten and Huggingface, which host models on behalf of customers. It lists Andromeda with a region of New York, and Braintrust, an evaluation and observability platform for language model output.

Those entries describe intermediary layers. Their presence means a request originating from a model name in the picker may reach the named model company directly, may pass through a router, may run on a third-party host, or may run on infrastructure Descript controls. The published documents do not say which, for any specific feature.

The privacy policy adds a third pattern. It states that the software generating voiceprints runs on web hosting infrastructure provided by one of Descript’s vendors, without naming that vendor. So a processing step can be disclosed as existing while the party performing it stays unnamed.

The defensible conclusion is narrower than a count of companies. Descript publishes a vendor inventory and it publishes model names. It does not publish the join between them.

Sources: Descript, accessed 15 August 2026 · Descript, accessed 15 August 2026 · Descript Privacy Policy, 14 April 2025 · Descript Help, accessed 15 August 2026

Where the documents disagree

Six disagreements are visible from published text alone. None of them proves misconduct. Each of them means a reviewer cannot rely on a single document.

Vendors. Neither vendor document contains the other.

Compiled by comparing Descript’s security page and subprocessors page, both read 15 August 2026.

The transcription row carries the most weight. The security page names Rev, which is absent from the subprocessors page. The changelog states that ElevenLabs Scribe v2 became the default transcription model across supported languages, and ElevenLabs is on the subprocessors page. Two documents describe the transcription vendor differently and neither has been updated to match.

Avatars, described three ways. The security page names Hedra. The changelog states Hedra Character 2 was turned off for all users because Hedra discontinued it, with Kling becoming the default. The privacy policy describes unnamed vendors collecting facial geometry. Neither Hedra nor Kling appears on the subprocessors page.

Human access to Projects. The Terms set out four exceptions to the rule that automatic processing does not involve human access: the user grants permission, the user requests White Glove Service, access is otherwise authorized under the Terms including the generative tools section, or the law requires it. The privacy policy sets out two: the user consents, or the law requires it. The two missing exceptions are the ones a reviewer would most want to see.

Account deletion. The security page states that deleting an account results in <a href=”https://www.descript.com/security” target=”_blank” rel=”noopener”>”all data associated with your account is permanently deleted”</a>. The privacy policy states that some information may be retained where required by law or for legitimate business purposes, and that cached or archived copies may be kept for a period.

Selling and sharing. The security page states that project information is not sold, marketed, or used for advertising. The privacy policy states that advertising activities may result in selling or sharing identifiers, network activity information, and inferences with advertising partners. Those statements cover different data classes and are not contradictory, but a reader of the security page alone would form the wrong impression of the whole.

Privacy contact. The security page directs data subject requests to a data protection officer address. The privacy policy directs the same requests to the general support address.

Sources: Descript, accessed 15 August 2026 · Descript Privacy Policy, 14 April 2025 · Descript Terms of Service, 25 February 2025 · Descript, accessed 15 August 2026 · Descript Changelog, accessed 15 August 2026

Open conflict on AI training

Five documents address whether uploaded material may train a model. They do not describe the same rule.

Compiled from Descript’s Terms of Service, privacy policy, Account data and privacy help article, and pricing page, read 15 August 2026.

Three things are settled. A self-serve control exists and its location is published. Enterprise drives have data sharing switched off with no toggle, which is the opposite of what a pricing-page reader would conclude. And Descript demonstrates that source-specific carve-outs are possible: the privacy policy states that data obtained through the Google Workspace integration is not used to develop, improve, or train its AI models.

One question stays open, and it is now narrow enough to put in a single sentence. The Projects opt-out is described as covering use to improve the Descript Service. The general purposes list separately names training artificial intelligence models. Whether the first phrase covers the second is the whole question, and no published document answers it.

The help article gives the strongest assurance on record, stating that Descript has no plans to use the data of anyone who opted out at any stage of research, development, or production. That is a statement of intent in a help article rather than a term of the contract. A reviewer who needs the assurance to be binding will want it in the agreement.

Sources: Descript Terms of Service, 25 February 2025 · Descript Privacy Policy, 14 April 2025 · Descript Help, accessed 15 August 2026 · Descript, accessed 15 August 2026

Voiceprints, faces, and three years

Two Descript features generate data the privacy policy identifies as sensitive, and both carry retention periods the other documents do not mention.

Voiceprints come first. When a user creates an AI Speaker, Descript generates a voiceprint from the consent statement and from the audio recording being edited, and uses it to authenticate the speaker and prevent fraud. The privacy policy notes that voiceprints may be considered biometric data in some jurisdictions. Retention runs until the purpose is satisfied or up to three years after the account was last accessed, whichever comes first. The software that generates them runs on web hosting infrastructure provided by one of Descript’s vendors, which the policy does not name.

Two details matter for consent design. The voiceprint is derived partly from the working recording, not only from the consent script. And the retention clock runs from last account access rather than from deletion of the clone, so an abandoned account extends the period.

Avatars work differently. When a user creates a Descript avatar, vendors collect facial geometry data from uploaded photos. The privacy policy states that Descript itself does not have access to that data, and that the vendors retain it until the purpose is satisfied or up to three years after last account access. Those vendors are not named in the privacy policy. The security page names Hedra for avatars, and the changelog says Hedra was turned off with Kling replacing it.

The privacy policy acknowledges that voice models and facial geometry are sensitive under applicable US state laws, and states that Descript does not use or disclose sensitive personal information to infer characteristics about a person.

For a buyer, the operational consequence is narrow. Any organization that has a biometric consent or retention policy needs to apply it to these two features specifically, because they are the only parts of Descript that generate biometric data, and they are the only parts with a published retention period.

Sources: Descript Privacy Policy, 14 April 2025 · Descript, accessed 15 August 2026 · Descript Changelog, accessed 15 August 2026

What the standard Terms prohibit

The eligibility question comes before the privacy question, and it is answered in a place most buyers do not look.

Descript’s Terms list categories of content a user may not upload. Three matter to organizational buyers. Content directed to children under 16. Content containing protected health information. Content containing nonpublic personal information from a financial institution.

The restriction follows the content, not the buyer’s industry. A hospital marketing team recording a facility tour is uploading ordinary marketing footage. The same team recording a consultation is uploading a category the standard Terms exclude. The line sits at the data, so the test applies recording by recording rather than once at procurement.

Two further contract terms bear on the same decision. The Terms state that information may be processed, transferred, and stored in the United States and other countries, which matches the privacy policy and the subprocessors table. And the Terms cap aggregate liability at the greater of ten dollars or the amount paid for the service giving rise to the claim, subject to stated exceptions for gross negligence, fraud, intentional misconduct, and matters that cannot be limited by law.

Those provisions do not indicate that Descript is unsafe. They describe where responsibility sits after an incident.

Sources: Descript Terms of Service, 25 February 2025 · Descript Privacy Policy, 14 April 2025

Who may hear a cloned voice

Voice cloning creates a human access path the rest of the product does not.

Descript requires a consent statement. The Terms define a consenting speaker as a person, including the account holder, who has given both the user and Descript permission to train and synthesize their voice. The security page states that speakers must read a Descript-designated script affirming identity and consent. A third-party voice is therefore permitted where that person has authorized both parties, which is wider than a self-cloning-only reading.

The Terms then set out who may listen. Descript employees, vendors, and contractors, naming Amazon Mechanical Turk workers, may listen to samples of training audio and synthesized audio to test quality and monitor for misuse. The same clause permits those workers to use the AI voice to create a series of non-defamatory utterances for internal quality assurance. The security page describes the Mechanical Turk step independently.

The privacy policy covers the same ground with different scope. It refers to employees and contractors listening to samples, and to Descript employees generating the quality assurance utterances. It does not mention vendors, and it does not name Mechanical Turk. Both documents describe human listening; they describe a different set of listeners.

Both also address research use. Training audio may be added to Descript’s research datasets, with the data disassociated from the account before it is added.

On watermarking, the pages read for this briefing are silent. Descript’s ethics page describes verbal consent verification and membership of the Content Authenticity Initiative. Neither that page, nor the Terms, nor the privacy policy, nor the security page, nor the voice cloning product page contains a provision stating that generated audio carries a watermark or provenance signal. Third-party writeups assert one exists. Five pages is a narrow search, so this is recorded as unresolved rather than absent.

Sources: Descript Terms of Service, 25 February 2025 · Descript Privacy Policy, 14 April 2025 · Descript, accessed 15 August 2026 · Descript, accessed 15 August 2026 · Descript, accessed 15 August 2026

What to request in writing

The published documents answer more than most buyers expect. These six cannot be closed from public text.

Alongside those, a reviewer will want the standard artifacts. The security page links a trust portal where requirements can be searched and further detail requested, which is the route to the SOC 2 Type II report. The privacy policy contains a European Economic Area section setting out legal bases for processing, data subject rights, and the route to a supervisory authority complaint, though it names no specific transfer mechanism. The Terms specify a written notice address for the arbitration opt-out, which has a 30-day window; that address should be taken from the Terms rather than the site footer, because the two differ.

Sources: Descript, accessed 15 August 2026 · Descript Privacy Policy, 14 April 2025 · Descript Terms of Service, 25 February 2025

FAQ

Methodology and source ledger

This is a Tier C briefing. Future Stack Reviews did not create an account, upload a file, run a feature, or inspect a setting. No claim here describes measured behavior or an observed data route.

Eleven Descript-published documents were read on 15 August 2026.

1. Data Subprocessors, descript.com/subprocessors
2. Security and privacy, descript.com/security
3. Privacy Policy, descript.com/privacy, last updated 14 April 2025
4. Terms of Service, descript.com/terms, last updated 25 February 2025
5. Account data and privacy, help center article 10255866490125
6. Ethics statement, descript.com/ethics
7. AI voice cloning, descript.com/tools/voice-cloning
8. Pricing, descript.com/pricing
9. Underlord co-editor, help center article 36803785502221
10. Generative image and video models, help center article 39869916772621
11. Changelog, feedback.descript.com/changelog

Four limits bound every statement above.

Page state cannot be asserted for a specific moment. Retrieval tools return cached versions in practice. The claim is that this content existed at these URLs as read, not that any page displayed the same on another date.

Account-gated material was not inspected. The Share data with Descript setting, the usage screen, checkout, and billing sit behind a login. The default position of that toggle for a new self-serve account is not established here.

Absence is recorded as unresolved. Where a provision was not located, that reflects a search across the eleven named documents. It does not establish that Descript has not published it elsewhere. The SecurityPal trust portal, any data processing addendum, and any Enterprise order form were not opened.

Provider attributions in the model reference were not verified against each model vendor’s own sources. That work is separate and is not reported here.

Sources rechecked: 15 August 2026. Contract versions checked: Terms 25 February 2025, Privacy Policy 14 April 2025. Product pages and the changelog change without notice and require a fresh check before any revision.

Verdict

Do not approve Descript by reading one privacy page.

Descript discloses a great deal. It publishes a subprocessor inventory with region labels, names biometric data as biometric, gives a retention period for it, states that Mechanical Turk workers may hear voice clone samples, and provides a self-serve control for data sharing with a published path. Most vendors of its size disclose less than this.

The problem is that no two of those documents agree on the same thing. The security page and the subprocessors page name different vendors for transcription, avatars, and human voice review. The Terms allow four exceptions to no-human-access; the privacy policy allows two. The security page says account deletion is permanent; the privacy policy says some information may be retained. Five documents describe the training rule in five ways.

The decision therefore turns on the recording rather than on the tool. Owned material containing no restricted data class, on a self-serve plan, is a decision the published documents can support once the sharing setting has been checked. Anything involving a third party’s voice or face brings biometric data and a three-year clock into scope. Client footage, confidential interviews, or anything touching a prohibited class should wait for written answers to the six questions above.

The finding is not that Descript hides its processors. The finding is that its disclosures were written at different times for different purposes, and reading any single one of them will give a buyer a picture the others contradict.