Customer attestation
Customer Attestation for External Recordings
This page states what Fred expects a customer to confirm before uploading external recordings, importing participant material, or requesting sensitive AI-assisted analysis outside Fred's native notice and acceptance flow.
- Last updated
- Effective date
- Version
- customer-attestation-2026-06-19
- Applies to
- Customers, workspace owners, administrators, researchers, and any user uploading external research material into Fred.
Scope: External recordings, imported transcripts, participant-provided material, behavioral analysis requests, and other uploads collected outside Fred's native consent flow.
When this matters
Whenever recordings or similar materials are collected outside Fred's native notice and acceptance path.
What must be true
The customer must be able to attest that collection, upload, and requested analysis are lawful and properly disclosed.
Fred's position
Fred may refuse, suspend, or remove a workflow when those conditions are missing or unreliable.
1. When attestation is required
This attestation model matters when a customer uploads, imports, or links recordings, transcripts, participant files, or similar material that was collected outside Fred's own native participant notice and acceptance flow.
It also matters when the customer asks Fred to run AI-assisted or behavioral-analysis workflows on such material, especially where the workflow involves recordings, participant-sensitive context, or derived signals.
2. What the customer must be able to attest
Before uploading or requesting analysis, the customer should be able to attest that the material was lawfully collected, that any required participant notice or consent was provided, and that the requested analysis is compatible with the stated research purpose and applicable law.
- The customer had authority to collect and upload the material.
- The people represented in the material received the required notice and, where required, gave valid consent.
- The requested analysis stays within the disclosed research purpose and does not introduce a new incompatible purpose without the required legal basis.
- The material does not contain prohibited or clearly unnecessary sensitive content for the requested workflow.
3. Material Fred may reject
Fred may reject uploads or analysis requests involving unlawful, exploitative, discriminatory, manipulative, infringing, or otherwise prohibited material. Fred may also reject material that appears incompatible with participant rights, confidentiality duties, or the product's supported use boundary.
Even where a customer believes a workflow is lawful, Fred may still require clarification, supporting context, or a more limited implementation if the request creates disproportionate privacy, rights, or platform risk.
4. Withdrawal, deletion, and suppression handling
If a customer later learns that notice, consent, or another legal precondition was missing, withdrawn, or materially defective, the customer should stop the workflow and request removal or suppression of the affected material without undue delay.
Fred may assist with deletion, export, or suppression handling according to product capability, customer agreements, backup integrity constraints, security needs, and applicable law.
5. Records and enforcement
Customers should keep their own records showing how external material was collected, what notice or consent path was used, and why the requested analysis is lawful and proportionate. Fred may ask for additional context or assurances before enabling a sensitive workflow.
Fred may pause, refuse, suspend, or remove a workflow if the required attestation cannot be supported or if the intended use becomes incompatible with Fred's legal, privacy, or product boundary.
Contact
Questions about this document can be sent to [email protected].