Privacy & your discovery data

Scout stores the project information your team provides, including stakeholder names and contact details, questionnaire answers, transcripts, generated documents, and review activity. Workspace members can access their team’s discovery data. Questionnaire responses are attributed to the respondent.

Account authentication is handled by Clerk. Application data and uploaded files are stored in Convex. When your team generates documents, selected discovery evidence is sent to the configured AI provider. Audio transcription, when enabled, sends the recording to Deepgram. When your team sends a reminder, the recipient address and reviewed email content are sent to Resend if email delivery is configured. Your discovery lead should confirm that this use is appropriate before uploading sensitive material.

Individual questionnaire links act as access keys. Shared questionnaire links use a private browser token to separate each respondent’s draft. Draft answers may also be stored locally on that device so work can recover after a connection interruption. Local drafts are removed after submission.

Client handoff links expose only the selected document versions, not internal review comments. Anyone holding a handoff link can view it until it expires or is revoked. Your team can archive an engagement to close public access, or delete its engagement data in the application backend.

Scout records operational events such as generation status and token usage. Optional hosting analytics and error monitoring depend on the deployment configuration. Do not put passwords or other secrets in discovery answers. Contact your discovery lead for access, correction, or deletion requests; the team operating the workspace is responsible for responding.

These are the application’s current data practices. This page does not claim regulatory certification or a specific contractual retention period.