How Hollow handles data.

Privacy should feel as deliberate as the assistant itself. This page covers the current Hollow Zero early-access posture.

Last updated March 31, 2026.

What Hollow collects

Hollow may collect account details, waitlist submissions, conversation content, connector install settings, granted scopes, and limited diagnostic information needed to keep the service working.

How it is used

This information is used to authenticate users, deliver assistant responses, support cross-surface continuity, manage connector installs, improve reliability, and communicate about early access.

Connected accounts and connectors

Hollow is moving toward user-owned account connections. When a connector supports OAuth or another account-linking flow, the goal is for each user to connect their own account instead of relying on a developer-funded shared API key. Connector listings should make their auth model and scope requirements visible before install.

Retention and access

Data may be retained for product operation, debugging, and early access support. Access is limited to what is needed to run and improve Hollow. As the platform expands, privacy and connector controls will continue to tighten.

Questions

For privacy questions, contact luka@gethollow.com.