privacy data use · Privacy Policy

BaseFrame policy finding

“ The BaseFrame desktop app reads on-device data to find the workflows worth automating. The exact sources depend on which operating system you run. macOS. We read passively from sources Apple already maintains: app-focus events from the Biome stream (Library/Biome), historical app usage from Screen Time (knowledgeC.db), Apple Mail / Calendar / Reminders / Contacts, browser history (Safari, Chrome, Arc, Brave, Edge, Firefox), and per-app SQLite caches (Slack, Notion, Microsoft Office, Linear, etc.). We never read message bodies. macOS Full Disk Access is required for these reads. Windows. Windows has no equivalent passive app-focus stream, so we run a small background process that records the foreground window’s application name and title once per second. Window titles are scrubbed for emails, phone numbers, file paths, and other PII patterns before they are stored locally. You can disable title capture in Settings. We additionally read browser history (Edge, Chrome, Firefox), Outlook mail headers (subject, sender, recipients) and calendar entries via MAPI, and Microsoft Teams channel activity. We never read message bodies. All raw local data stays on your device. To generate workflow recommendations, the Desktop Application constructs prompts from scrubbed activity metadata (app names, timestamps, and PII-scrubbed window titles) and sends them to BaseFrame's servers, which forward them to an AI provider for processing. No message bodies, file contents, email text, or unredacted personal data are included in these prompts. Activity data that has already been summarized into a workflow fingerprint is cached locally and is not re-sent.”

Document

Privacy Policy

Captured

2026-07-19

Location

Privacy Policy › “Local Data Sources Read by the Desktop App”

Snapshot SHA-256

789e8a899c2b6d5b28bf7ca8472c96d3f976d7ec37656b6d8a3bbeb34a3a2051

Informational only, not legal advice. Terms change; verify the source and capture date.