Data and network use
On-device processing and service connections
Section titled “On-device processing and service connections”Your meeting content is processed on this device by default. Before the first connection, review the privacy policy. After acceptance, first-time setup makes a country-only request to choose regional usage-data controls, respecting saved network restrictions. It sends no meeting content or installation identifier. The following service review controls content-free licensing and app updates. Basic usage reporting has its own visible switch: on by default outside the EEA/UK, prior opt-in inside the EEA/UK, and no reporting under an unknown or unconfigured policy.
Work offline in Settings → AI providers keeps cloud processing off. AI processing stays on this device. Separately enabled service connections can still run. Licensing, update checks, and enabled usage reporting work independently of where your meeting content is processed. These service requests contain no meeting content; their identifiers and connection data are described below.
External AI tasks are off by default. Choose each task’s provider and approve its disclosed data before any sharing. Only approved ordinary text can be shared. Recordings, voiceprints, acoustic information and voice-derived interpretations always stay on this device. Turn Share basic usage data off in Settings → Privacy & storage without changing your AI or licensing choices.
Usage consists of numeric action counts, including app openings, completed update checks, and updates found. It includes a random installation identifier; the service derives country and a coarse network prefix, not a retained raw IP. See Privacy for exact fields, retention, and deletion controls. There is no desktop analytics SDK or website pixel.
Optional AI component downloads are started by you. App update checks and downloads are automatic when enabled; turn them off in Settings → General. You confirm installation and restart.
User-directed local exports
Section titled “User-directed local exports”A new export menu on every meeting note lets you save content to your device with no upload. Available actions: Save as Markdown, Email draft, Save audio clip, and Local Git handoff. Transcript timestamp links let you jump to the spoken segment in local audio playback — no content leaves your device.
Audio clips may be saved locally; the current network-export actions accept only their disclosed text content. Recordings, voiceprints and acoustic information are never sent through Markdrip-controlled AI routes. Markdrip does not host audio clips or create hosted links to your content.
See Export and share meeting notes for details.
User-directed network exports (coming soon)
Section titled “User-directed network exports (coming soon)”When available, you will be able to send selected content from a meeting note — summary, manual notes, or action items — directly to a workspace you own. This will not be a background channel: a network request will happen only when you explicitly choose a destination, preview what will be sent, and confirm the action. Each export will be a fresh, one-shot action with no retry or background sync.
Read Privacy & Local-First Guarantees for the complete promise.
Private insights and processing status
Section titled “Private insights and processing status”The navigation shows Processing: On this device, selected cloud tasks, or an unavailable status when the processing location cannot be confirmed. Open it to review providers and task choices. Licensing, updates, enabled usage reporting, calendar connections, file exports, and connected agents have separate scopes.
Meeting-history insights start only after you choose to enable them. Sending selected evidence to an AI provider additionally requires the Insights task permission and cloud insights choice. Including your private context is a further choice. Personal reflections stay local. An exclusion prevents future use; it cannot recall text already sent to a provider.
Sharing private insights with an agent requires separate permission. Connected agents may forward received text under their own data-handling settings. The status describes Markdrip’s processing, not all software on the device. See Insights and My coach.