---
title: "Pace privacy"
description: "How Pace keeps voice, screen, meeting, and journal data local, plus the explicit exceptions that can use the network."
canonical: https://heypace.app/privacy/
last-updated: 2026-08-27
---
# Pace privacy

How Pace keeps voice, screen, meeting, and journal data local, plus the explicit exceptions that can use the network.

## Default

Pace processes voice, screen, meeting audio, and local journals on the Mac. The native app does not require an account and does not include analytics or telemetry SDKs.

## Public website analytics

Pages on heypace.app use Microsoft Clarity for visits, session interaction, and heatmaps; Watchtower measures aggregate routes and performance; and App Health records page visits and the website's explicitly named button events. App Health uses a first-party persistent anonymous browser ID for up to 90 days, records cleaned page paths, the referring site hostname, bounded campaign tags, and coarse country, device, and browser categories. It does not receive button text, form contents, or app data. The website has no Pace account or in-app voice, screen, meeting, or journal data. The native app loads none of these website analytics services and sends no telemetry.

## Explicit network use

- Sparkle checks a GitHub-hosted appcast for updates.
- Optional cloud or CLI planner tiers contact the provider selected by the user and visibly tint the app's status surface.
- The download tool fetches only a URL the user asks it to fetch.

Meeting audio is stored as local files under Pace's Application Support directory and can be deleted by the user.