Wisp Privacy Policy

Data Wisp handles

• Notes: title, body, original text or transcript, tags, state, timestamps, and AI-processing metadata.
• Unsubmitted drafts: local snapshots of new text, note edits, and recordings that have ended but have not yet been saved as notes, including references to their local files.
• Recordings and attachments: audio files, image files, documents, metadata that references those files, and SwiftData external-storage binary payloads used for restoration on synced devices.
• AI configuration: provider, model, feature routing, prompt choices, local model state, an optional profile, and user-saved memory items.
• API keys: stored in iOS Keychain, not in SwiftData or plain files.
• Purchase information: Apple transaction and receipt information, subscription or lifetime entitlement state, an anonymous RevenueCat App User ID, and app/device/store metadata needed for purchase verification and support.
• Feedback and diagnostics: when enabled, app version, iOS version, hardware model and language in the email body, plus a text attachment with redacted error metadata and an available anonymous purchase support ID. Diagnostics are enabled by default and can be turned off before sending, removing both automatic body metadata and the attachment.

Local-first behavior

By default, notes and recordings are stored on the device. Wisp remains usable without an account and without online AI configuration.

Unsubmitted text, note-edit snapshots, and recordings that have ended but have not yet been saved as notes remain local and do not enter CloudKit. Users can explicitly keep a draft and close, or discard it. The draft snapshot directory is excluded from device backups; this does not mean that attachment or audio files referenced by a draft are excluded from backup. Once saved as a note, content follows the normal note-storage and optional iCloud-sync rules.

Text changes are checkpointed after a 250 ms pause. Checkpointing reduces the risk of losing unsaved work but does not guarantee zero loss if the app stops before a write completes or storage fails. Recording recovery covers ended, finalized recordings only; it does not promise recovery of an unfinished M4A file.

Purchases and RevenueCat

Apple processes payments made through the App Store. Wisp uses RevenueCat to validate purchases, determine whether the configured entitlement is active, restore purchases, and provide subscription management and purchase support. Wisp does not create a user account; RevenueCat creates an anonymous App User ID. That anonymous identifier can be included in the feedback diagnostics attachment when support needs it; it is not displayed on the purchase page.

Wisp may contact RevenueCat when the app starts, restores purchases or refreshes entitlement status, even if you do not tap a purchase button during that session. These requests support purchase verification and access to existing purchases; they do not send note content.

RevenueCat may receive Apple purchase history and transaction data, the anonymous App User ID, and app/device/store metadata required for purchase verification, fraud prevention, entitlement delivery, support, and RevenueCat dashboard analytics. Wisp does not send notes, recordings, attachments, transcripts, prompts, API keys, or local-model content to RevenueCat. Wisp disables RevenueCat's automatic device-identifier collection for attribution and does not use purchase data for advertising or cross-app tracking. Apple and RevenueCat process this information under their respective privacy policies.

Microphone, Speech, and transcription

Wisp requests microphone permission when the user starts recording. Audio is saved locally first. Apple Speech is the default transcription path; depending on system settings and Apple terms, speech data may be processed by Apple.

Users may optionally download local Whisper models for on-device transcription. Wisp stores the raw transcript and can also create a more readable paragraph-form note body.

Online AI providers

If a user configures a provider API key and runs an AI action or enables the corresponding automatic AI processing (including explicitly consented long-term theme updates), Wisp sends only the content needed for that action to the selected provider. Supported provider families include OpenAI, Anthropic, Gemini, xAI, Mistral, Perplexity, Together AI, Fireworks AI, Cerebras, OpenRouter, Groq, DeepSeek, Doubao, Qwen, Moonshot, Zhipu, Baichuan, Tencent Hunyuan, Baidu Qianfan, MiniMax, SiliconFlow, Tencent TokenHub, Huawei ModelArts, OpenAI-compatible services, and Ollama-compatible endpoints. Provider processing is governed by the provider’s own terms and privacy policy.

Local AI models

Local Whisper and GGUF model files are not bundled in the app. They are downloaded only when the user chooses them, stored in Application Support, excluded from iCloud backup where appropriate, checked with SHA256 before installation, and removable by the user. Hy-MT2 Q4 is the only downloadable translation model and provides direct Chinese, English, and Japanese translation across all six directions.

On iOS 26 and later, Wisp can request Apple-hosted managed asset packs and copy verified model files into the same local model store. If an Apple-hosted pack is missing or unavailable, Wisp falls back to its existing background downloader. The downloader measures available official and verified-mirror endpoints, keeps the official source when performance is close, and automatically uses a verified mirror when it is materially faster. Every source is pinned to the same expected file checksum. iOS 18–25 use the existing downloader. Model download traffic goes only to the selected Apple-hosted or public model source; note text is not included in those download requests.

AI memory

An optional profile and saved memories are stored locally in app settings. Opening Related checks note contents and tags on device using keywords and tags to find up to four related notes, without a network request. It may suggest at most one original sentence from the current note about a preference, constraint, or decision. Candidates are not saved as lasting memories automatically; saving one requires your action. You can also add or edit memories, delete individual items, disable use without deleting them, or clear the collection. An overall memory switch and a separate personal-profile switch control their use; there is no per-request selection of individual memories or profile. They provide preferences and background, not unsupported facts for the current note.

Wisp can compare sentence meanings using an available Apple on-device language model, with keywords and tags as a fallback. You may also download and select one of two optional offline association models: EmbeddingGemma 300M (about 334 MB) or multilingual MiniLM INT8 (about 128 MB), including tokenizer files. After download and selection, these models compare notes only on this device; note text is not sent to the model host or an AI provider for association. Downloading model files requires a network connection. Model files stay local and are excluded from iCloud sync and backup.

System translation

When the user chooses Translate on a note, Wisp passes the currently selected note text to Apple's Translation framework. Translation uses Apple-managed on-device language models. If a required language is not installed, the system asks the user before downloading the shared language pack. Wisp does not send this translation text to a Wisp server, does not replace the original note, and does not store the system translation result automatically.

iCloud

iCloud sync is off by default. When enabled, notes, tags, attachments, transcription jobs, AI polish jobs, relationships, metadata, and SwiftData external-storage binary payloads sync through SwiftData and the user's private CloudKit database. Wisp developers cannot directly read a user’s private CloudKit database.

Recording, image, and document files still keep local relative paths for fast playback and preview. When a synced device is missing a local file, Wisp can backfill the local file from the SwiftData external-storage payload if that payload has synced. Downloaded local model files are never synced through iCloud and are excluded from iCloud backup where appropriate.

Wisp shows sync state from the user's iCloud account and CloudKit import/export events: disabled, not synced, syncing, synced, or the latest error. SwiftData does not expose per-file progress, so Wisp does not invent a sync percentage.

Feedback and diagnostics

Feedback prepares an editable email with prompts for the problem and reproduction steps. “Include diagnostics” is enabled by default and can be turned off before sending. When enabled, app version, iOS version, hardware model and language are added to the body, and a text attachment contains only timestamps, error severity, event categories, error codes and an available anonymous purchase support ID. It excludes note content, recordings, API keys, account credentials, record identifiers and free-form error messages. Turning diagnostics off removes both the automatic body summary and attachment. Wisp does not read the user-assigned device name or a device identifier. Wisp does not automatically upload or send this information: users review the draft and confirm sending in their mail app. If Apple Mail is not configured, users can share the draft and diagnostics file with a compatible mail app, or open an email draft without the attachment.

Search, shortcuts, and exports

Search runs locally. Lightweight semantic recall uses on-device representations and does not upload notes to a Wisp server. URL Scheme routes and Siri Shortcuts open Wisp actions such as capture, search, settings, import/export, or a specific note without adding extra tracking.

When users export Markdown, PDF, images, share cards, Notion entries, or Obsidian handoffs, the selected content is passed to the system share sheet or target app as requested by the user. Saving share images uses iOS Photos permission and system save behavior.

Live Activities and notifications

Recording and transcription can use Live Activities / Dynamic Island to show current state. Morning notes, evening review, and model-download completion reminders use local notifications that are off until the user enables or triggers them.

Tracking and training

Wisp does not sell personal data, does not use advertising identifiers, and does not use note content to train models. Network processing occurs for online AI, optional iCloud sync, feedback sent by the user, external links, Apple system services, model downloads and purchase verification through RevenueCat. No Wisp account does not mean there is no third-party data processing.

Deletion and control

Users can delete notes, tags, recordings, attachments, API keys, and downloaded local models inside the app, and revoke permissions in iOS Settings. Deleting the app removes local app data from the device. iCloud data is managed through iCloud settings and synced devices.

Deleting Wisp changes its anonymous RevenueCat App User ID after reinstall, but Apple purchase history and RevenueCat purchase records may remain where required to restore purchases, prevent fraud, provide support, or comply with law. Users can manage or cancel subscriptions through Apple's subscription settings and can contact Wisp with the support identifier for a RevenueCat data request. Apple controls App Store transaction and refund records.

European privacy rights

Where GDPR or similar laws apply, users can request access, correction, export, or deletion of personal data related to Wisp. Because Wisp has no account system, most data is stored on the user's device, in the user's iCloud account, with RevenueCat for purchase management, or with the third-party provider the user selected. Wisp can assist with RevenueCat purchase-support records and support or feedback records that the user sends to the developer.

The usual legal bases are providing app functionality requested by the user, honoring user-selected service configuration, complying with applicable law, and processing optional diagnostics when the user chooses to send feedback.

Children

Wisp is not directed to children and does not knowingly collect children’s personal information.

Contact

For privacy questions, contact support@mosodive.com.

Free and Pro data protection

Free and Pro use the same content-protection principles. Free manual AI uses default prompts and provider default endpoints, without retrieving or injecting saved Memory. Custom endpoints and Memory use require Pro. Existing settings and memories are retained when access ends; new paid processing stops. Wisp never silently redirects an old custom endpoint’s API key or notes to an official endpoint after a downgrade. Third-party AI usage charges are not included in Pro.

Public documentation website

Help, Privacy Policy and Terms are available both online and bundled for offline reading. Cloudflare hosts the public website and processes IP addresses, browser and request metadata needed to deliver and secure the pages. The website receives no notes, recordings or API keys and has no advertising or behavioral tracking scripts. Reading bundled documents does not require a website request; online links open in the browser.

Selected AI context and backups

Explicitly starting an AI action invokes the configured summary model. Connect ideas and Compare changes use the current note plus related notes, up to five in total; Recent review uses the five most recent notes from the last seven days. Each note contributes up to 3,000 characters. For an online provider, only the excerpts in that action’s scope and any enabled memory/profile context are sent to the configured provider; local models process them on device. Merely opening Related sends no note content to a provider. Results retain their source list and can be saved separately without automatically overwriting source notes. Memories and personal profile fields are included in explicit Wisp JSON and Wisp Markdown ZIP backups; those exported files may therefore contain sensitive information. They are not thereby added to automatic iCloud memory sync. Imports merge this information rather than overwriting existing nonempty profile fields. Keep exported files secure and check the destination before sharing.

Processing and weekly reviews

After starting an AI action, you can leave its page and find the result later in Memory. Processing may continue briefly when Wisp goes into the background, but iOS can interrupt it. Failed or interrupted requests are not automatically retried. If notifications are already allowed, Wisp may send a completion notice without note text.

Weekly reminders are off by default and require Pro. You can enable a local notification for Sunday at 20:00, or choose another weekday and time. With notification permission, iOS can remind you even when Wisp is closed; Focus and system notification settings may delay or silence it. A weekly reminder does not start AI processing; weekly reviews still require a tap. In review history, tap Start review to use the configured summary model on all available, nondeleted notes with text created or last edited during the preceding seven local calendar days. The range ends at your tap and uses the currently saved text, not historical versions. Full text is split into batches and combined, without a five-note or 3,000-character-per-note limit. An online model receives those batches, necessary intermediate summaries and enabled memory/profile context; multiple requests may incur usage charges. Local models process the content on device. Memory and profile switches still apply. Failed or interrupted requests are not retried automatically. Turning the reminder off removes future reminders and does not automatically cancel a review you explicitly started.

Long-term themes can be started manually. Automatic updates are off by default and require your explicit consent. Once enabled, Wisp incrementally updates themes from changed notes after edits settle, only while the app is in the foreground. There is no fixed schedule or guaranteed background run. The same failed input is not automatically retried; changing the provider or processing route requires consent again. They use the currently available text across your note library, rather than only the past week. Wisp caches summaries of individual notes locally to reuse unchanged material; editing or deleting a source invalidates its cached summary. An online summary model receives the required source text and intermediate summaries, without saved memories or profile context; a local model processes them on device. Large libraries can require multiple requests and incur provider charges. Results and cached summaries remain on this device and do not automatically change source notes, lasting memories or personal profile fields. Check the sources before saving a result.

Memory keeps up to 52 review records and 12 manually started result records on this device, including failed attempts. This history is excluded from backups and iCloud sync. Results may contain personal information; you can delete them or explicitly save a successful result as a new note. Saving creates an ordinary note with the usual note sync and backup behavior. It does not change the original notes or automatically add lasting memories.

Contact information and purchase support

When you send feedback, Wisp support receives your sender email address, message and any diagnostics you choose to include, to reply and investigate. If the attachment includes a RevenueCat purchase support ID, we can link that email to the corresponding purchase record; an anonymous ID does not remain unidentifiable after that connection. The diagnostics switch controls the automatic summary and attachment, not your email sender address.

Personal profile and online AI

If you enter a name in your profile and enable profile context, applicable online AI actions send that name and the needed profile information directly to your chosen provider to fulfill the request and personalize its wording. Notes, memories and intermediate summaries may also be sent as required by the selected feature. Wisp developers do not receive these AI requests through a content server. Providers may associate requests with your API account and retain them under their policies. Processing entirely on device does not send content to a provider.