DaySpire Logo DaySpire

Trust by architecture,
not just by policy.

Most productivity and cloud-based tools ask you to trust a written privacy policy document. DaySpire is engineered so that work content stays in the Mac app's local storage boundary and off DaySpire servers.

1. What Stays Local

DaySpire keeps work content inside your macOS user directories under a locally encrypted database by default. Runtime AI does not upload these content types to DaySpire servers:

  • Audio Recordings & Transcripts: Meeting voice recordings and their corresponding on-device text transcripts.
  • Intelligent Local Index: Search mapping that organizes notes, transcript segments, and files securely on-device.
  • Visual Text Captures: Screen captures added explicitly by you as billing evidence are indexed purely on-device.
  • Project memory: Links between calendar tasks, notes, documents, and client timelines.

2. What May Contact the Internet

DaySpire is a local-first application, but it requires standard, transparent external hooks for maintenance, asset delivery, and optional billing logs:

  • Model Downloads during Setup: About 12 GB of speech-to-text and language models are fetched one time into local assets from verified repositories. The download runs in the background and can be paused, resumed, or cancelled in Settings; the models never send work content anywhere.
  • App Update Checks: Querying public release manifests to ensure your local macOS binaries stay secure.
  • Product license Activation: The app checks your generated license keys against our isolated dashboard endpoint to verify legitimacy.
  • Optional advertising measurement: When a Google ad brought you to the website, DaySpire asks before remembering the ad click identifier. If you allow it and Stripe later confirms a paid invoice, the licensing service sends Google the click identifier, transaction identifier, paid amount, currency, time, and a granted measurement-consent signal. It sends no DaySpire work content, does not use the data for ad personalization, and stores nothing for this purpose if you decline.
  • Opt-In Diagnostics: Crash metadata or core process limits can be shared purely under an opt-in basis, containing no transcripts or file content.

3. macOS System Permissions

DaySpire is a native, notarized Mac app that relies on macOS's per-permission consent system (TCC): each capability below triggers a standard system prompt the first time the feature that needs it is used, and the app keeps working in a reduced mode if you decline. To observe app and window activity, DaySpire runs outside the macOS App Sandbox — which is exactly why every one of these permissions stays individually visible and revocable in System Settings > Privacy & Security.

🪟 Accessibility

Reads permitted app names and window titles when you enable work-context capture so DaySpire can help group your day, and when you enable meeting detection so it can recognize supported live calls. DaySpire never reads raw keystrokes or clipboard contents — input monitoring retains aggregate activity counts only.

🎙️ Microphone Access

Used solely for audio you explicitly initiate: meeting or room recordings you start yourself, recordings of detected meetings you approve — it asks first, every time, and the microphone does not start until you say yes — and short voice-search commands you trigger. Recording state is always visible in the app and menu bar.

🖥️ Screen Recording

Used only for features you enable or deliberately invoke: optional screen-text summaries, screenshot evidence you capture, visible-attendee extraction, and system audio during a recording you started or approved. If permission is already granted, DaySpire can also use it as a meeting-detection fallback when Accessibility is unavailable. Screen-content sampling remains off by default, and projects you mark as highly sensitive keep screenshots disabled by default.

📅 Calendar Integration (EventKit)

Optional. Reads local calendar events to link meetings to projects and resolve timeline gaps.

📂 Watched Folders

Reads files only in folders you explicitly add (via the standard macOS folder prompts) and files you drag in as project evidence. Content is indexed locally only.

4. Data Portability

Your work is yours. DaySpire stores work records locally and lets you export reviewed timecards and audit logs as standard CSV, XLSX, or JSON files. You can also clean up application data and downloaded model files from local settings.