Local Markdown and AI writing workspace / Last updated 2026-08-21

WitNote Privacy Policy

Local-first No ads or tracking listed macOS / Native Swift / Local MLX AI / Ollama / Bring-your-own API

Overview

WitNote 2.0.3 is a native macOS Markdown writing and knowledge workspace rebuilt in Swift, with local folders, format conversion, bilingual reading, local MLX, Ollama, and user-configured API models.

This privacy policy applies to WitNote. Product delivery happens through the Apple App Store and the linked Hooosberg product website. The website and the app are first-party product surfaces; a GitHub repository is provided as a public source and notice reference.

Data Handling

User-selected folders, Markdown documents, and exports stay local by default. Local MLX and local Ollama do not upload documents by default. Text is sent directly to a user-configured cloud endpoint only when the user sends a request, and attached document content requires a separate per-endpoint permission.

Personal data collected by this productSee product-specific disclosure

Local-first storageYes

Advertising or third-party analyticsNot listed for this product

WitNote Data Flow

WitNote is a local-first macOS Markdown writing and knowledge workspace. The folders, Markdown documents, notes, imported files, exports, and app settings selected by the user are handled on the Mac. WitNote does not require a Hooosberg account, run advertising, or maintain a server-side writing profile.

Local files and foldersWitNote accesses the folder and files that the user chooses through macOS file access. The user remains responsible for backups, permissions, and the contents of imported or exported files.

Local AI inferenceWhen a local MLX model is selected, prompts and responses are processed on the Mac. The app does not default to sending those documents to a hosted AI service.

OllamaWitNote can connect to an Ollama service running on the same Mac. The app restricts that connection to localhost addresses and reads only the models available in that local service; it does not upload Ollama models to Hooosberg.

App settings and model selectionStored locally so the app can remember the selected workspace, interface preferences, model source, and available local or Ollama models.

User-Configured Cloud APIs

WitNote can connect directly to an OpenAI-compatible API endpoint chosen and configured by the user. WitNote is not an AI API provider and does not proxy cloud requests through a Hooosberg server. The user chooses the endpoint URL, model ID, and API key; the API key is stored in macOS Keychain on that Mac, not in a WitNote account or Hooosberg database.

When the user sends a cloud-AI request, the request text and the model response are transmitted directly between the app and the configured endpoint. Sending attached current-document content is off by default and requires the user to enable a separate permission for that individual endpoint. The user is responsible for choosing a provider, reviewing its privacy policy, and avoiding content they are not permitted to send.

WitNote does not retain cloud request bodies or API keys on a Hooosberg server. The configured provider may process, retain, or use data according to its own terms and settings; its retention and deletion practices are outside WitNote's control. Remove an endpoint in WitNote settings to delete its locally stored API key, and disable the document-content permission at any time.

Local AI and Model Downloads

WitNote 2.0.3 uses a native Swift macOS interface and supports a local MLX inference route. A small Qwen3 0.6B 4-bit model is bundled so a new user can start without a first model download. Optional model downloads are performed only when the user selects a model or retries a download; the downloaded files are saved in the app's local model directory and are not uploaded by WitNote.

MLX and Qwen are third-party open-source or model projects with their own notices and license terms. The app package includes third-party notices and the bundled model's license files. User-downloaded models remain subject to the model source's license, acceptable-use rules, and any attribution requirements. See MLX and the Qwen3 model page for source information.

In-App Purchases

The optional Lifetime purchase for format-conversion features is handled by Apple App Store and StoreKit. WitNote uses StoreKit to verify the purchase and restore it on a user's Apple account. Hooosberg does not receive the user's Apple ID, payment method, billing address, or App Store credentials. Refunds, billing questions, and account-level purchase records are handled by Apple.

Third-Party Notices

The installed app includes a ThirdPartyNotices.txt file and bundled Qwen3 LICENSE and NOTICE files where applicable. MLX, Qwen, and any subsequently downloaded model are credited separately from WitNote's own application code. Users should review the relevant source notice before redistributing model files or generated packages.

Network and External Links

WitNote may use the network for user-initiated model downloads, Apple StoreKit purchase or restore flows, pages the user explicitly opens, a local Ollama service, and a cloud endpoint configured by the user. The core Markdown workspace and local inference path are designed to work without a Hooosberg cloud account. External services process data under their own terms when the user chooses to access them.

Platform Services

When you download, purchase, update, or review WitNote through Apple App Store, Apple may process account, payment, device, crash, or store activity data under Apple's own privacy policy. WitNote may access the network for user-initiated model downloads, Apple StoreKit purchase or restore, pages the user explicitly opens, a local Ollama service, or a cloud API endpoint that the user configures. WitNote does not require a Hooosberg account, run advertising, or maintain a hosted user profile.

Support

For privacy questions or product support, contact [email protected] or Telegram @hooosberg.

Changes

This page will be updated when the product changes its data handling, store distribution, account model, analytics, payment flow, or support process.