Flunkey

Legal · Privacy

Privacy Policy

Last updated on 4th of October, 2026 · Version 1.0.0 · Holder: Flunkey

Flunkey is a local-first Windows desktop app with no first-party AI proxy, accounts, analytics, advertising, or tracking. Cloud providers are optional: speech transcription can run with on-device Whisper, and AI tasks can use your configured Ollama server. This policy explains what stays on your device, what leaves it, and how to delete it.

1. Summary

  • We operate no server for the app. There is no account, registration, or login. Cloud requests go directly from your device to the provider assigned to that task. Requests using Ollama go to the server you configured, normally localhost.
  • We never receive your content. Your audio, transcripts, chats, selections, dictionary, and API keys never reach us.
  • Cloud requests use the key you entered for that provider. Local Whisper and Ollama are keyless local options; an Ollama request is sent to its configured server.
  • On-device Whisper uses temporary WAV and text files, deletes them after success or failure, and cleans up crash leftovers on a later launch. F9 screenshots are captured only when you select them, sent with that F9 request, and saved locally as JPEG attachments with chat history.

2. Data stored on your device

DataLocationNotes
Settings and collections (transcripts, chats, transforms, dictionary, analytics/history)%LOCALAPPDATA%\com.flunkey.desktop\ (separate plaintext JSON files)Settings and collections are stored separately; no encryption at rest and no API keys in these files.
F9 screenshot attachmentsLocal chat history under app dataUser-selected screen or app-window captures are stored as JPEGs with the local chat.
OpenRouter model catalogLocal app-data cachePublic catalog data and timestamp; no chat content or keys.
On-device Whisper model downloadsLocal model storageDownloaded locally by the user; removed by Wipe all data.
API keysWindows Credential Manager, service Flunkey: groq_api_key, openai_api_key, gemini_api_key, openrouter_api_keyDPAPI-backed, per-user. Fail closed: if the keyring is unavailable, keys stay memory-only and are never written to disk. Legacy plaintext keys are auto-migrated then blanked.
On-device Whisper temporary audio and textTemporary local WAV and text filesDeleted after success or failure; leftovers from a crash are cleaned up on a later launch.
ClipboardOS clipboardF8/F10 use clipboard-based paste; the current clipboard may be cleared by Wipe all data. Windows clipboard history and cloud clipboard may persist outside Flunkey.

3. Data sent to third parties

When a task uses a network service, its request goes to the cloud provider assigned to that task, the user-configured Ollama server, or the relevant model catalog service:

ProviderEndpointPrivacy info
Groqhttps://api.groq.comgroq.com/privacy-policy
OpenAIhttps://api.openai.comopenai.com/policies/privacy-policy
Google Geminihttps://generativelanguage.googleapis.compolicies.google.com/privacy
OpenRouterhttps://openrouter.aiopenrouter.ai/privacy
Ollama (optional)User-configured server, normally localhostRequests go to the server address configured by the user, not to a Flunkey cloud service.
Model catalogsOpenRouter public catalog; Groq model listing uses the saved Groq keyCatalog requests contain no chat content and are separate from F9 conversations.

Cloud audio and text are sent to the cloud provider assigned to that task. Provider processing regions, retention, and training-use policies are governed by the provider, not by Flunkey. If you select Ollama, requests go to the user-configured Ollama server (normally localhost) rather than a cloud AI provider.

F9 screenshots are captured only after you choose a screen or app window in the F9 panel. The image is sent with the F9 request to its assigned provider and saved locally as a JPEG with that chat. Image analysis requires a vision-capable model. F8 and F10 do not capture screenshots.

The OpenRouter model catalog is public. Groq model discovery uses the saved Groq key; that listing request contains no chat content. Neither catalog request is an F9 conversation request. When you report an AI response, Flunkey opens an editable email draft and does not send it unless you choose to send it.

4. What we never collect

No analytics, crash reporting, advertising identifiers, or remote logging. No prompts, completions, audio, screenshots, keys, IP addresses, or user agents are sent to Flunkey. There is no first-party AI proxy. When local Ollama is selected, requests go to the server address you configured.

5. Retention and your choices

Data stays in local app storage until you wipe it. Settings → Wipe all data clears settings and collection files, screenshots attached to saved chats, downloaded Whisper models, saved provider keys, and the current clipboard, then resets app preferences, including startup settings. Windows clipboard history (including Win+V) and cloud clipboard may persist outside Flunkey. You can also remove individual transcripts, chats, transforms, and dictionary words in-app at any time.

6. Children

Flunkey is not directed at children under 13. Do not use it to process a child's personal information.

7. Changes and contact

We may update this policy as the app evolves; the date at the top will change and material changes will be surfaced in-app. Questions: flunkeymanager@gmail.com · https://www.flunkey.space