Your data stays yours.

1. Who we are

FeynmanLM ("the app", "we", "our") is an independent app developed by Maarten de Vries. Contact: support@feynmanlm.app.

2. Data we do not collect

FeynmanLM servers do not store your source library or study history. This means:

• We do not store your sources, Schedule plans, chats, or review sessions.
• We do not collect your study history, review outcomes, or learning progress.
• We do not store the content of sources you add (articles, papers, PDFs, podcast transcripts).
• We do not collect your AI provider API keys (stored in the macOS Keychain on your device).
• We do not collect voice recordings or transcriptions.
• We do not run advertising, behavioral tracking, or cross-app analytics.

3. Where your data is stored

All app data is stored in your private iCloud container (iCloud.com.feynmanlm). In the current app implementation this means a SQLite database plus source files rooted inside the app container. This includes:

• Knowledge-base sources and extracted source text
• Source queue, Studio state, and Schedule plans
• Podcast transcripts, book files, paper PDFs, and other imported source files
• Feynman session history and generated artifacts

iCloud storage is governed by Apple's Privacy Policy at apple.com/legal/privacy. Data is encrypted in transit and at rest by Apple.

Your API keys (Anthropic, OpenAI, Groq, Gemini) are stored in the macOS Keychain and never leave your device except when used to authenticate requests directly to those providers.

4. Third-party AI providers

FeynmanLM sends content to third-party AI providers directly from your device — not through our servers. You configure which provider to use in Settings. The content sent includes:

• Source text excerpts when you review or chat about a source
• Your typed or transcribed answer text
• Review prompts, summaries, and follow-up questions
• Text sent to cloud text-to-speech providers when you use Read Aloud with a cloud provider

Each provider has its own privacy policy and data retention practices:

You are not required to use all of these providers. You choose which provider handles each task in Settings. If you do not configure a provider's API key, the app does not send data to that provider.

5. Hosted MCP relay

If you connect an external assistant through MCP, your assistant's requests and the app's responses pass through FeynmanLM-operated Cloudflare infrastructure before reaching your Mac. The hosted relay does not log or store MCP request or response bodies, but it is a trusted relay and is not end-to-end private from FeynmanLM infrastructure.

The hosted relay stores relay metadata such as tunnel records, tokens, OAuth credentials, and last-seen timestamps.

6. Google connectors (Drive and YouTube)

FeynmanLM offers optional Google connectors. They run only when you explicitly connect them and grant access; FeynmanLM never accesses your Google account on its own.

YouTube. FeynmanLM uses YouTube API Services to import the videos you have liked on YouTube. Connecting YouTube grants FeynmanLM read-only access (the youtube.readonly scope) to your liked-videos feed. FeynmanLM reads the title, video ID, position, and uploading channel of each liked video and stores them in your own knowledge base on your Mac and in your private iCloud container. FeynmanLM does not read, modify, or upload anything else in your YouTube account.

Google Drive. The Google Drive connector imports Drive files you point it at (read-only) as meeting or document sources. It reads a folder or document only when you explicitly start an import.

If you later open or review an imported video or document, its transcript or text is fetched at that point and stored with the source. As described in Section 4 and Section 5, source content you choose to review may be sent to the AI provider you have configured, or to an AI assistant you have connected over MCP. FeynmanLM does not otherwise share your Google data with third parties.

By using the YouTube connector you agree to the YouTube Terms of Service. Google's handling of any data it receives is governed by the Google Privacy Policy. You can revoke FeynmanLM's access to your Google account at any time from the Google security settings page.

7. Microphone and voice input

FeynmanLM requests microphone access to support voice answers in Review Chat. When you use voice input:

• If you use Apple's on-device speech recognition (the default option), audio is processed entirely on your device and never transmitted.
• If you configure a cloud speech-to-text provider (OpenAI Whisper, Groq, Deepgram, or others), your audio is sent to that provider's servers for transcription. Audio is not stored by the provider beyond the time needed to return a transcript (per each provider's policy).

We do not store, transmit, or have access to your audio recordings or voice transcriptions at any point.

8. Sign in with Apple

FeynmanLM uses Sign in with Apple for authentication. When you sign in:

• We receive an anonymous, app-specific user identifier from Apple.
• We do not receive your name or email address unless you explicitly choose to share them during sign-in.
• If you choose to share your email, Apple may provide a relay address that forwards to your real email.
• This identifier is used only to associate your in-app purchase and subscription status with your account.

Sign in with Apple authentication is governed by Apple's Privacy Policy.

9. In-App Purchases and Subscriptions

Purchases and subscriptions are handled entirely by Apple's App Store. We do not collect or process payment information. Apple does not share your payment details with us.

We may receive from Apple: your Apple-assigned user identifier, country/region, and subscription status. We use this only to unlock app features and do not share it with third parties.

10. Analytics and crash reporting

FeynmanLM does not integrate any third-party analytics SDK (such as Firebase, Mixpanel, or Amplitude).

If you have opted in to sharing analytics with app developers in macOS settings, Apple may provide us with aggregated, anonymized crash reports and basic usage metrics. This data does not include personally identifiable information. You can opt out in System Settings → Privacy & Security → Analytics & Improvements.

11. Safari Reading List and local file access

On macOS, FeynmanLM can read your Safari Reading List bookmarks to automatically surface recently saved articles. This data is:

• Read locally from ~/Library/Safari/Bookmarks.plist
• Never transmitted to us or to any server
• Used only to populate the Studio source queue on your device

This feature requires you to grant Full Disk Access in macOS System Settings. You can revoke this permission at any time.

12. Children's privacy

FeynmanLM is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided information through the app, please contact us at support@feynmanlm.app.

13. Data retention and deletion

Your source library and study data exists in:

• Your iCloud account — delete via Finder/iCloud Drive or remove the app's data in macOS System Settings → Apple ID → iCloud → Manage.
• Your device Keychain — API keys are removed when you delete the app.
• Third-party AI providers — follow each provider's data deletion process per their privacy policies linked in Section 4.
• Hosted MCP relay metadata — only if you connect an external assistant through MCP.

14. Changes to this policy

If we make material changes to this privacy policy, we will update the effective date at the top of this page and, where appropriate, notify users within the app. Continued use of the app after any changes constitutes acceptance of the updated policy.

15. Contact

Questions or concerns about this privacy policy?

Email: support@feynmanlm.app
Website: feynmanlm.com