Data Handling Principles

Hepi is designed to be a transparent bridge between your local environment and advanced AI models. We follow a strict “Explicit Intent” model: data is only processed or sent online when you actively trigger a feature.

1. Local Storage

Most of your configuration and session data stays on your machine in encrypted or secured local storage.

Settings: Your preferences, custom shortcuts, and feature toggles are stored locally.
Identity: Authentication tokens and your user profile are cached locally to keep you signed in.
Entitlement: Your Pro+ status is verified via a local signed receipt.

2. Online AI Processing

When you ask a question or use a live assistant mode, Hepi securely transmits the necessary context to AI providers (such as Google Gemini).

Feature Type	What is Sent	Processing Method
Assistant Chat	Text, captured screen regions, or uploaded images.	On-demand (only when you click send).
Meeting Assistant	System audio or microphone input.	Real-time streaming (while the mode is active).
Live Assistant	Continuous audio and visual context (if enabled).	Live-streaming API.

3. Crash Diagnostics

When Hepi crashes or exits unexpectedly, it may send a bounded technical report to help diagnose reliability issues. Crash diagnostics can include app version, platform, crash type, error message, stack trace, startup timing, and recent app milestones.

Crash diagnostics does not include screenshots, screen recordings, microphone or system audio, transcripts, chat prompts, model responses, auth tokens, entitlement receipts, API keys, raw settings, or full process lists. Reports are redacted, truncated, grouped by issue, and retained for a limited period.

Distinguishing Local and Online Tasks

It is important to understand the boundary between what stays on your PC and what goes to the cloud.

Local Tasks: Window management, desktop switching, ghost mode, and settings changes happen entirely on your computer. No data is sent online for these operations.
Online Tasks: AI responses, speech synthesis, and live transcriptions require secure cloud processing to function.

Info

Hepi does not "train" its models on your private data. Your captures and conversations are used solely to provide the immediate response you requested.

Best Practices for Privacy

Control Your Context: Only capture the specific screen regions or audio sources needed for your task.
End Sessions Promptly: Always stop Meeting or Live Assistant modes as soon as they are no longer needed to terminate the data stream.
Review Settings: Use the Privacy section in Hepi settings to control which apps are monitored and how capture notifications are handled.

Visual Indicators

Hepi provides clear visual indicators (such as glowing borders or status text) whenever a live capture or microphone session is active, so you are always aware of when data is being processed.

Last updated: 2026-06-19

Was this page helpful?