:Harvey:Support

What Usage Data Does Harvey Collect?

Learn about usage data, from what it is to why and how we use it.

Last updated: Apr 15, 2026

Overview

Usage data captures how users interact with Harvey across your organization and is displayed in Harvey’s Analytics dashboard. It reflects activity across product surfaces such as Assistant, Vault, Workflow agents, Playbooks, Word, and Outlook.

Usage data helps:

  • Admins and Knowledge Managers understand adoption and engagement
  • Organizations demonstrate ROI internally and support renewals
  • Harvey improve product performance and feature development

What Usage Data Does Harvey Collect?

Harvey limits data collection to what is necessary to provide insights and improve the platform.

Core Usage Metadata

Harvey collects event-level metadata such as:

  • User information
    • User email
  • Time and access
    • UTC timestamp
    • Access point (e.g., web, mobile, api)
  • Activity details
    • Product surface area (e.g., Assistant, Vault, Workflow agents, Playbook, Word, Outlook)
    • Subsurface (e.g., new thread vs. follow-up)
    • Action (e.g., create vs. run)
    • Client Matter ID (if provided)
    • Source (e.g., uploaded files, Vault, external databases)
    • Number of uploaded documents

Resource Identifiers (Where Applicable)

For certain product areas, Harvey logs resource names to support deeper analysis:

  • Workflow agent name
  • Playbook name
  • Vault name
  • Review table name

This helps Admins identify which resources are most used by their organization.

What Is Not Included in Usage Data

The Usage History API and Analytics dashboard do not include:

  • Query text
  • AI-generated responses

Sensitive content (queries and responses) is only available via the Query History API and requires appropriate authorization.

This separation ensures:

  • Sensitive content is not exposed in Analytics
  • Admins can analyze usage without accessing user inputs or outputs
  • Data access aligns with enterprise privacy expectations

How Harvey Uses Usage Data

Harvey uses usage data to support both customer visibility and platform performance.

Specifically, usage data enables:

  • Transparency to customers via Analytics
  • Support for enterprise reporting and renewal discussions
  • Product performance and reliability improvements via engagement patterns and feature adoption

Usage data is not used to train foundation models on customer content. Harvey analyzes high-level trends and engagement patterns.

Privacy and Security Notes

  • Usage data is scoped at the workspace level.
  • Resource names returned via API are not gated by client-matter or ethical walls.
  • API tokens should be managed securely.
  • Retention policies apply based on workspace configuration.

FAQs

Manage Vault Data Retention Settings

Learn how to configure and manage vault data retention settings in Vault, including triggers and deletion timelines.

View Analytics and Reporting

Understand how to access, interpret, and export usage analytics in Harvey, and when to use the dashboard versus APIs for reporting.

Client Matters for Admins

Learn how admins can manage client matter numbers in Harvey, including viewing, editing, uploading in bulk, and setting user permissions.

Release Overview

Understand how Harvey manages product releases, rollout methods, and admin controls.

Managing Prompts and Examples in Library (For Admins)

Discover how to manage, customize, and organize Library to fit your team’s needs.