---
title: "What optional text refinement changes about the data flow"
description: "Optional refinement introduces a service-processing step for text."
slug: "text-refinement-data"
category: "privacy-data"
language: en
editorial_status: published
capability_status: development
reviewed_at: 2026-10-13
keywords: ["CueSpec cloud text processing","refinement privacy","server data flow"]
---

# What optional text refinement changes about the data flow

Optional refinement introduces a service-processing step for text. Local audio transcription does not mean that a refined prompt has never left the Mac.

## Know which mode you use
The raw route creates a draft locally. The optional refinement route requires a configured CueSpec Server and login. Complete real-service acceptance and public policy details remain incomplete in the reviewed snapshot.

Before using refinement for sensitive material, establish the intended provider route, what text is submitted and the applicable handling terms. A generic health response does not answer retention or access-control questions.

## Avoid unsupported promises
This library does not claim zero retention, universal end-to-end encryption, an independent security audit or a specific compliance certification. Those claims require evidence from the actual service and contractual arrangement.

Manual editing of the local raw draft is an available alternative when you do not need a remote cleanup stage. Sending the final prompt to Codex still has its own data flow and terms. Decide separately whether local capture, optional refinement and task delivery are each appropriate for your material.

## Related reading

- [Data-processing facts in the current workflow](/privacy-facts-summary/)
- [Optional text refinement is unavailable](/refinement-unavailable/)
- [Where recorded audio goes](/audio-data-flow/)
- [CueSpec product facts at a glance](/product-facts/)