CoreRecord
Legal

Privacy Policy

Privacy Policy – CoreRecord for macOS

Last updated: September 16, 2026

1. Our Privacy Commitment

Your privacy is the core architectural principle of CoreRecord. Engineered exclusively for macOS as a local-first utility, CoreRecord records and transcribes audio directly on your Mac. For users who choose to subscribe to CoreRecord AI, the app can also generate executive meeting summaries powered by Apple Intelligence. We do not require user accounts. The developer operates no custom servers and does not receive, store, or access your recordings or transcripts; optional summaries are processed on-device or via Apple's Private Cloud Compute as detailed in Section 3.

2. Content Processing & Storage (Local Handling)

By default, audio recording and live speech transcription are processed and stored locally on your Mac using system storage.

  • Audio Files (.caf): Recorded audio (microphone and system audio) is written directly to app-accessible local storage on your Mac. Raw audio files are never uploaded or transmitted by CoreRecord.
  • Transcripts & Metadata: Timestamped text segments, session titles, dates, and durations are persisted locally on your Mac using Apple's SwiftData framework. Generated summary text is saved locally on your Mac with the session unless you delete the session.
  • User Exports: When you export or copy content, files are written only to locations you explicitly choose on your Mac.

Data Deletion & Trash Safety: You retain full control over your content. When you delete a session inside CoreRecord, the local SwiftData transcript records are deleted, and the associated `.caf` audio file is safely moved to your Mac's system Trash (allowing manual recovery via Finder if deleted by mistake). Uninstalling CoreRecord removes the local app container data.

3. macOS APIs & Apple Intelligence

CoreRecord leverages native macOS APIs to provide high-performance audio capture, speech recognition, and optional text summarization.

  • System Audio Capture (ScreenCaptureKit): CoreRecord uses Apple's ScreenCaptureKit API to capture system audio (e.g., meeting audio from web browsers or video calls). Although macOS displays a "Screen Recording" permission prompt, CoreRecord utilizes an audio-only pipeline. Video frames are discarded immediately, and no screen or video data is ever recorded, stored, or transmitted.
  • Speech Recognition (Transcription): CoreRecord uses Apple's native `SFSpeechRecognizer` framework with `requiresOnDeviceRecognition` strictly enforced. Speech transcription is performed locally on your Mac using Apple's on-device speech recognition engine. If on-device speech recognition is unavailable on your Mac, live transcription may not be offered; CoreRecord does not send audio to the developer or to third-party speech APIs for transcription.
  • AI Summaries (CoreRecord AI Tier Only): Meeting summarization is available exclusively with an active CoreRecord AI subscription (Pro Lifetime does not include AI summaries). When an AI subscriber explicitly clicks to generate a summary, CoreRecord uses Apple's Foundation Models framework:
    • Private Cloud Compute (PCC): For complex or long meeting transcripts, CoreRecord routes the transcript text (never raw audio) to Apple's Private Cloud Compute. This processing is governed by Apple's Apple Intelligence Privacy Terms. According to Apple's Apple Intelligence and PCC documentation, PCC processes data solely to fulfill your request, does not make data accessible to Apple, and does not retain data after returning results. As documented in Apple's privacy terms, Apple may collect limited, non-content request telemetry (such as approximate request size and processing duration) to maintain service quality, which is not linked to your Apple Account or meeting content.
    • On-Device Fallback: If PCC is unavailable or quota limits apply, CoreRecord attempts to summarize the transcript locally on your Mac using Apple's on-device `SystemLanguageModel`.

4. Data Collection & Network Policy

Specifically:

  • We do not run analytics, advertising, tracking, or telemetry on your recordings or transcripts (see Section 5 for purchase-related data).
  • We do not sell or share your content with third parties.
  • We do not integrate with third-party AI APIs or LLM providers.

Network communication in CoreRecord is strictly limited to:

  1. Receipt & Entitlement Validation: Communicating with RevenueCat and Apple App Store services to process purchases, check subscription status, and restore purchases (see Section 5).
  2. Apple Intelligence Summaries: Stateless transcript summarization requests sent securely from your Mac to Apple's Private Cloud Compute through native Apple Intelligence system services when an active CoreRecord AI subscriber explicitly triggers summary generation.

5. Purchases & Financial Data

CoreRecord is free to download for microphone recording and on-device speech transcription. We offer two optional paid upgrade paths:

  • CoreRecord Pro (Lifetime): A one-time In-App Purchase that unlocks System Audio capture (ScreenCaptureKit). Pro Lifetime does not include AI meeting summaries.
  • CoreRecord AI (Monthly Subscription): An auto-renewing monthly subscription that unlocks Apple Intelligence meeting summaries and automatically includes all CoreRecord Pro system audio capture features (no separate Pro purchase required).

Transaction Data (Apple App Store): Apple processes all payments, transactions, and auto-renewable subscriptions. The developer does not receive or store your credit card details, financial information, or billing address. For details, see Apple's Privacy Policy.

Purchase & Entitlement Validation (RevenueCat): To manage product entitlements, verify active subscriptions, and support purchase restoration across devices, CoreRecord uses RevenueCat. RevenueCat processes limited non-content metadata, including:

  • An anonymous app user identifier generated for entitlement mapping
  • Purchase and entitlement status (e.g., whether `corerecord_pro` or `corerecord_ai` is active)
  • Basic device and app version details required for receipt validation

RevenueCat never receives your audio files, transcripts, session titles, or meeting content. We use it solely for purchase management—not for advertising, profiling, or cross-app tracking. For details, see RevenueCat's Privacy Policy.

6. System Permissions & Requirements

To provide its features, CoreRecord requires specific system permissions and hardware capabilities governed by macOS:

  • Microphone: Requested to capture your spoken voice during recording sessions.
  • Speech Recognition: Requested to convert spoken audio into timestamped text locally on your Mac (`SFSpeechRecognizer`).
  • Screen & System Audio Recording: Requested by ScreenCaptureKit solely to capture system audio output from remote calls and browser applications.
  • Apple Intelligence Requirement: AI summaries require a compatible Mac running a supported version of macOS with Apple Intelligence enabled and an active CoreRecord AI subscription.

7. Recording Consent

You are solely responsible for complying with all applicable local, national, and international laws regarding audio recording and obtaining any required notice or consent from meeting participants before recording.

8. Contact & Support

For questions regarding this Privacy Policy or CoreRecord's architecture, please contact support at: