“Not used for training” is the start of the conversation.
A privacy promise becomes useful when you understand its scope, exceptions and the task you want to perform.
What is established.
DuckDuckGo states that Duck.ai conversations are not used to train models and describes agreements that limit provider retention. Its documentation also identifies exceptions, optional features and separate handling for uploads. These are the provider’s published commitments. PrivacyAF has not audited their implementation.
Where we stand.
Our interpretation: privacy-conscious product design deserves attention and precise reading. Training use, retention, access and permission are different questions. A service’s protection does not decide whether your organization permits a particular client document or personal record to be sent to it.
Ask the next question.
- Does this commitment cover the exact product, feature and account you plan to use?
- Which retention exceptions, subprocessors and upload rules apply?
- What information can you remove while still accomplishing the task?
- Who has authority to approve disclosure of the material?
Educational commentary. Sources and services can change. This brief does not establish legal compliance, product safety or misconduct. No affiliation or endorsement. Suggest a correction.