AI transparency
AI Transparency and Participant Notice
This page explains how Fred presents AI-assisted research analysis on the public website, what kinds of AI-supported workflows Fred may enable, what notice expectations apply, and which uses are outside the intended or supported boundary.
- Last updated
- Effective date
- Version
- ai-transparency-2026-06-19
- Applies to
- Customers, procurement teams, workspace users, and people who may be exposed to AI-assisted research analysis performed through Fred.
Scope: AI-assisted summaries, theming, evidence linking, behavioral analysis, recordings, attention or gaze-related indicators, and related participant-facing notice expectations.
Purpose
Fred uses AI to support research review, evidence organization, and decision-making workflows, not to replace human judgment.
Notice
People exposed to AI-assisted analysis should receive clear notice when the workflow depends on recordings, behavioral signals, or other sensitive processing.
Boundary
Fred does not position these features as definitive tools for employment, education, health, policing, or legal-status decisions.
1. What Fred means by AI-assisted research analysis
Fred may use AI-assisted components to help customers organize, summarize, cluster, or review research evidence. Depending on the workflow, that can include summaries, thematic groupings, evidence links, tags, behavioral-signal overlays, or other research-support outputs.
These features are intended to help a human team move faster and inspect evidence more coherently. They are not intended to displace human review or to produce definitive judgments about a person's inner state or legal status.
2. Inputs that may be involved
AI-assisted workflows may rely on customer-provided prompts, transcripts, survey answers, comments, recordings, interaction events, or other research material that the customer has chosen to process through Fred.
Some workflows may also rely on behavioral or attention-related signals derived from recordings or interaction data where that feature is actually enabled for the relevant product path.
3. Participant notice expectations
Where a person is recorded, analyzed, or otherwise exposed to a workflow that uses AI-assisted research analysis, the customer should provide clear notice that the session or material may be reviewed with AI-assisted tools and that related outputs may be linked into reports or evidence repositories.
Where Fred provides native notice or acceptance steps inside the product, customers should use them. Where the collection or upload occurs outside Fred's native flow, the customer remains responsible for the participant-facing notice and any required consent or other lawful basis.
- Explain that the material may be reviewed with AI-assisted analysis.
- Explain whether recordings, transcripts, or behavioral signals are involved.
- Explain who will review the outputs and for what decision-making purpose.
4. Human review and interpretive boundaries
Fred expects customers to keep a human reviewer in the loop when using AI-assisted research outputs. Customers should inspect source evidence, check material context, and avoid presenting AI-assisted output as a substitute for contextual judgment.
Fred's AI-assisted outputs should not be represented as definitive statements about emotion, honesty, mental state, diagnosis, identity, or protected characteristics.
5. Unsupported or prohibited uses
Fred does not support using AI-assisted or behavioral-analysis outputs as the sole basis for high-impact decisions about employment, education, insurance, credit, housing, policing, or similar access decisions.
Customers must not configure or request workflows that would be unlawful, manipulative, discriminatory, exploitative, or incompatible with participant rights or applicable AI and privacy law.
- No use as a stand-alone employment or education decision system.
- No claim that a Fred signal proves what a person truly feels, intends, or believes.
- No request to process material that was collected without the required notice, permission, or lawful basis.
6. Escalation and contact
If a customer is unsure whether a workflow fits the supported boundary, the customer should pause the rollout and request a legal or operational review before proceeding. Fred may also pause or reject a workflow if the notice, attestation, or intended use appears unreliable or incompatible with the product boundary.
Questions about this page or a particular workflow can be sent to the contact address below.
Contact
Questions about this document can be sent to [email protected].