Synopsule Privacy Policy
Synopsule is a Mac and iPhone app — with an Apple Watch companion recorder — for recordings, notes, files and a personal knowledge library. Recording, transcription, file extraction and search run locally. AI organization and private iCloud synchronization are optional. This policy explains what data the app handles, where it goes, and the choices you have.
On this page
Connected AI apps and optional app control
On Mac, a client you configure can launch Synopsule's local MCP server to search and read finalized, eligible transcript text, attached text and kept note context. The client controls where that text goes, including any processing by its provider. Audio, voiceprints, credentials, calendar contents and live transcript drafts are never returned over MCP.
Allow AI app control is off by default. When you enable it and keep Synopsule open, connected clients can request recording, local analysis, optional AI recaps/context, edits, action completion, authored Library changes, local playback, model management, file imports, document exports and portable backup/restore. The running app performs these operations with its existing local storage and optional synchronization rules. Native file choosers let you select originals and destinations. Deleting recordings, retained audio or Library items requires confirmation in the app. Recording still requires macOS permissions; AI requests retain the chosen destination's consent and subscription checks. MCP cannot approve a new destination, change your account, enable iCloud or purchase a subscription on your behalf.
Automatic text access withholds sources excluded from memory, external AI or retrieval. Imported/generated evidence is reviewed in the app rather than exposed as editable internal records. Transient requests and responses use a private local mailbox; completed results are held only for the app launch and current library. Activity messages name the action, without logging transcript content. Turn app control off to stop new control requests and result access; actions already performed may remain. Remove or disable a client connection to end its transcript access. Revocation does not retract text a client has already received. Standalone/custom-root sessions and clients launched with --read-only cannot operate the app. Synopsule does not provide a hosted control server.
Website analytics and advertising measurement
The separate advertising-operator setup page runs no analytics and sends no form data. It encrypts entered account setup details in your browser for a file you choose to download and share with the operator. Private signing and decryption keys remain on the operator's Mac.
The Synopsule website uses anonymous Mixpanel events to understand page visits and App Store button clicks. Google Ads also receives a button-click event when you choose an App Store link. A button click is an expression of interest, not proof of a download or purchase. Website tracking is disabled when your browser sends Do Not Track.
Links from a known advertising campaign can include Apple's publisher and campaign tokens so App Store Connect can provide aggregate acquisition reports. Those tokens describe the campaign, not your recording. We do not forward audio, transcript text, meeting titles, speaker names, or an app analytics device identifier in these links. We do not join website and app identifiers to identify you across devices.
TL;DR
- Audio stays on your own devices. Recordings are stored locally. Apple Watch recordings transfer to your paired iPhone. If you choose Analyze on Mac, selected stopped recordings transfer directly to your paired Mac for local analysis. Audio never passes through Synopsule servers or a cloud AI provider.
- Your library stays on your device by default. Transcription happens fully on-device. If you enable iCloud, library text, document and image originals, knowledge and edits are stored in your Apple account's private CloudKit database. Playback audio, voiceprints and AI keys are excluded.
- AI recaps, answers and note context are optional and opt-in. Off-device providers receive selected transcript, note and attached-source text only with your explicit consent. On-device AI sends none of that text online. Audio is never sent. Summarizing automatically after a recording is a setting you control, and it never starts sending to an outside provider on its own.
- Calendar awareness is optional and read-only. Events are read locally and never changed. Choosing a meeting can name a recording; that recording title can appear in exports or text you authorize an AI provider to process. Calendar times and attendee suggestions are not saved into the library, backups or AI prompts. Notifications are posted locally, and the recording Live Activity excludes meeting text and speaker names.
- Backups are yours to place. A library backup is an ordinary ZIP file you create and choose a location for. Synopsule never uploads one.
- Anonymous product analytics, easy to turn off. We send anonymous usage events (e.g. "a recording was started", "the export sheet was opened") to help improve the app. No transcript text, no audio, no account, and no advertising identifiers — and you can disable it any time with the Share anonymous analytics switch in Settings.
What we collect
Recording and transcription run locally. Your meeting library stays on your device by default. Optional cloud AI processes selected text only with your consent, and optional product analytics excludes your recorded content. Specifically:
- Microphone audio (and, on a Mac, that Mac's system audio) captured during a recording are processed locally on your device. While a recording is in progress, the in-flight audio is held in an encrypted temporary vault. In version 3, new recordings retain local playback audio by default. An existing explicit deletion preference is preserved. You can turn off “Keep audio after processing” or delete a recording's audio. The vault copy is cleared only after processing and a successful library save; unfinished work keeps its local recovery audio. Audio is never sent to Synopsule servers or cloud AI. You can explicitly send a stopped recording directly to your paired Mac as described below.
- Apple Watch recordings are captured from the watch's microphone, stored locally on the watch, and transferred to your paired iPhone over Apple's Watch Connectivity. Incoming recordings wait on your iPhone until you choose “Save to this library.” The app confirms the encrypted local audio and saved recording before telling the Watch that import succeeded. You can delete an incoming iPhone copy separately from a saved library recording or the Watch original. Interrupted transfers and unconfirmed imports retain local recovery files. Transcription runs on your own devices; audio is never sent to Synopsule servers or cloud AI.
- Transcripts and recording metadata (titles, speakers, timestamps, your local notes) are stored in the app's local storage on your device. Selected transcript, note or attached text can be sent to a cloud AI provider only when you choose that option and consent, as described below. To reopen the correct local library after a restart, Synopsule stores local database, file and storage-volume identifiers. These identifiers stay on the device and are not sent to analytics or AI providers.
- Vocabulary you teach consists only of spellings and optional misheard forms you explicitly add. It stays on this device, scoped to the selected library, and is used as a hint for local speech recognition and as aliases in local search. It is not inferred from recordings or calendars and is not sent to AI summary providers, included in transcript mirrors, or synchronized through iCloud. You can edit or remove it in Settings.
- Settings and preferences (selected model, source toggles, AI provider choice, consent acknowledgements) are stored in the app's local preferences on your device.
- API keys (if you bring your own LLM key) are stored in your device's Keychain. We never see them.
- Notes, files and knowledge include text you write, extracted passages and page information, people and projects you create or confirm, database definitions and values, actions, evidence and revision history. Selected document and image originals are copied into protected app storage; your original files remain untouched. PDF extraction and image OCR run on-device. Unsupported or unfinished extraction is identified rather than presented as fully searchable. JSON originals are inspected on-device as complete documents up to 8 MiB, including valid JSON recognized inside text files. Known keys for embedded credentials, voiceprints and model state cause rejection. Recognized JSON above this limit, and declared JSON that cannot be completely parsed, are refused; other file types keep their own limits. This check recognizes known fields and does not decode arbitrary encoded secrets.
- Editing drafts are saved separately on this device to recover unfinished typing. They do not enter iCloud, AI requests or library archives. A source deletion also removes its local editing draft after reconciliation.
- Audio files you import are decoded and transcribed on your device exactly like a recording Synopsule captured itself. The file you picked stays where you left it.
- Calendar events are read only if you switch on meeting awareness, and only to offer to record a meeting and name the recording after it. See below.
- Library backups are files you create and place yourself. See Backups you create.
- Library diagnostics in the device's system log record load/save outcomes, error codes and record counts. These messages exclude recording titles, transcripts, summaries, audio, file paths and keys. Synopsule does not upload these diagnostics; you choose whether to share them with support.
Calendar, notifications, and the Lock Screen
Synopsule can now speak up on its own — telling you a transcript is ready, or offering to record a meeting that is about to start. Everything it needs to do that is read and displayed on your device.
- Meeting awareness is optional and reads only calendars you select from Apple Calendar, including connected Google calendars. Synopsule uses event names, times and invitee names locally to offer recordings. It inspects event links and dial-in details locally for the optional reminder filter. It never changes calendar events. Choosing a meeting can name a recording. Calendar event identifiers, scheduled times, attendee suggestions, notes, links, phone numbers and guest email addresses are not stored in the knowledge library, included in exports or used in AI prompts. Calendar selections, dismissed occurrences and muted recurring-series identifiers remain local preferences. Disabling awareness stops reads and cancels scheduled reminders. A chosen recording title or a speaker name you manually confirm is ordinary recording content and can appear in exports and authorized AI text. Exact legacy recovery files from an older app can retain that older version's metadata; migration preserves those recovery copies rather than silently rewriting them. Calendar data is never used for analytics.
- Meeting-app detection (Mac only, and also off until you switch it on) offers the same thing when a video-meeting app comes to the front. It looks only at which app is frontmost — never at what is on screen, and never inside another app's windows.
- Notifications are delivered locally by macOS or iOS. Transcript notifications and meeting reminders have separate opt-in controls. Meeting reminders let you choose timing and sound, and optionally show the meeting title; title previews and sound are off by default for meeting reminders. A reminder carries an opaque event reference so tapping it can open the current meeting; it never carries attendee names or calendar notes. Your device’s notification settings and Focus can silence or delay delivery. Calendar changes refresh when Synopsule runs; a scheduled reminder may be stale until then, so the event is checked again when opened. Existing transcript notifications can include the recording title. No notification service or server receives this content.
- Continued analysis is an optional preview on supported iPhones. A user-started analysis can show generic progress and a cancel control while Synopsule is in the background. This system interface receives no recording title, transcript text or speaker names. Interrupted work keeps its on-device recovery audio for a later retry.
- The Live Activity on the iPhone Lock Screen and Dynamic Island carries exactly two facts: when the recording started, and whether it is paused. No meeting title, no transcript text, no speaker names. A Live Activity is drawn on a locked screen in front of whoever is in the room, so that ceiling is deliberate.
- Shortcuts, Siri, the Action button, the Control Center control, and the Home Screen widget can start, pause, and stop a recording. They carry the same instruction a button inside the app does, and no transcript content. The widget cannot see your library and never displays any of it.
Anonymous product analytics
Unless you opt out, Synopsule sends anonymous usage events to Mixpanel (mixpanel.com) so we can understand which features are used, where users get stuck during setup, and which errors are most common. We use this data to prioritize improvements.
What is sent:
- Event names like
app_launched,recording_started,recording_stopped,summarize_completed,purchase_completed,export_failed, and similar product-interaction events. - Coarse metadata about those events: app version, OS version (macOS or iOS), plan type (free vs Pro), recording duration, error category, export format, and similar non-identifying signals.
- A randomly-generated device identifier ("distinct ID") that Mixpanel assigns automatically.
- In builds supporting Apple Ads attribution, the Apple-reported campaign, ad-group, keyword and ad IDs, attribution status, and whether the install was a download or redownload following a click or impression. These describe our advertising campaign, not an advertising identifier for you.
What is NOT sent:
- Audio, ever.
- Transcript text or summaries.
- File names, paths, or session titles.
- Your name, email, IP-level account, advertising identifier, or any contact information.
- API keys.
- The text of any search query you type.
The data is not linked to your identity and is not used to track you across apps or sites. We use it to improve Synopsule and measure whether our Apple Ads lead to app use or Pro purchases. We do not send recordings, usage events or purchase events to ad networks.
Apple Ads attribution: On a new eligible App Store installation, a supporting build can request a short-lived opaque attribution token from Apple's AdServices framework and send it directly to api-adservices.apple.com. Apple returns attribution for its own ads. The token stays in memory for the bounded lookup attempts: it is not logged, saved, or sent to Mixpanel. Only the limited campaign metadata above is kept on-device and attached to anonymous analytics. A failed or unmatched Apple lookup is not evidence of an organic or Google Ads install. We do not match website visitors to app users or use fingerprinting, IDFA or contact details for attribution. Existing installations are not retrospectively assigned to a campaign by this feature.
Turning it off: Open Synopsule's Settings — Privacy on a Mac, Privacy & Microphone on an iPhone — and switch off Share anonymous analytics. Synopsule stops sending events immediately, cancels attribution lookups, clears the local attribution record and any queued events, and ignores results that arrive after opt-out. It does not delete analytics already received by Mixpanel. You can turn it back on at any time.
Analyze on your own Mac
Analyze on Mac is optional. You pair your iPhone with your own compatible Mac using a one-time code and approval on the Mac. The devices use direct local-network connections with TLS 1.3 and device certificates held in the device-only Keychain. Nearby discovery advertises a random installation identifier, not a recording title. There is no Synopsule relay, developer-hosted storage or cloud inference service.
Only the stopped recording you choose, its duration, and transcription settings (language, translation and an optional speaker-count hint) go to the Mac. Recording titles, calendar details, notes, tags, saved voiceprints and AI-provider credentials are not transferred. The Mac returns transcript text and speaker numbers. Voice matching and publication into the original library happen on your iPhone. The handoff does not automatically request a paid summary or send its transcript to cloud AI.
The Mac holds incoming audio and results in a separate encrypted compute queue, not its recording library. Unstarted audio expires after 72 hours; a result is removed after the iPhone confirms saving it, or after 7 days. Cleanup runs while the Mac app is open and when it next launches. Cancelling or removing a phone requests deletion of its handoff data; active inference must stop before its files can be removed. An offline Mac cannot receive a deletion request until it is reachable. The original iPhone recording remains subject to your existing keep/delete controls. Incomplete recovery audio is preserved until you explicitly delete it.
Camera access is used only when you tap Scan pairing code. Camera images stay on the iPhone. Pasting a code is an explicit paste action, and you can instead use a one-time pairing file. The app removes an imported copy from its own Inbox; it never deletes an original you open in place from Files. Pairing codes expire after two minutes and are never accepted as transcript or library-write authority.
When data leaves your device
For in-app AI, text leaves your device only if you choose and consent to a cloud provider — for a recap, a question with "Ask your meetings", or context for a note. Only the selected transcript, note, file passages, saved database entries or action details needed for the task is sent — never the audio. On-device AI keeps that text local. You can also choose to export text or archives and share them yourself, or give a connected tool access to the local text library.
AI can run on-device where supported, through a provider you configure, or through Synopsule Pro:
Bring your own key (BYO)
If you configure your own LLM API key, the text needed for your chosen task is sent directly to the provider you select, not through Synopsule:
- OpenAI — selected text is sent to
api.openai.com. - Anthropic — selected text is sent to
api.anthropic.com. - Google Gemini — selected text is sent to
generativelanguage.googleapis.com. - LiteLLM-compatible gateway — selected text is sent to the base URL you configure.
These requests use your API key and are subject to that provider's privacy policy. We never see them.
Synopsule subscription
If you subscribe via the App Store, selected text is sent to the Synopsule API Worker (hosted on Cloudflare), which validates your App Store subscription receipt and forwards the request to OpenAI for the AI task you requested. Summary request text is not retained after completion. For Library organization and answers in supported app builds, selected source passages, saved record values and action details may be processed with your consent. Complete Library AI results, including quoted source text, may remain in Cloudflare's cache for up to ten minutes to avoid duplicate processing. Durable processing receipts retain hashes, subscription identifiers, usage and status, not source or result bodies. Original document files and audio are not sent to this AI service.
Library organization and questions
Library AI extracts suggested people, projects, details, actions and collection fields, and answers questions with supporting source quotations. On supported Macs, the bundled Library model runs on that Mac without a provider account. The iPhone and iPad apps do not run or bundle this Library model; AI organization and answers require an explicitly selected API provider or Synopsule subscription with the existing text-processing consent. Recording, speech transcription, notes and text search remain available on-device. New Library setups use on-device processing; an existing Library-specific provider choice and an explicit automatic-processing Off setting are preserved. The Library choice is separate from the AI used for recording summaries. An unavailable local model never switches to an external provider on its own.
Suggestions do not prove identity or complete an action. A uniquely named mention in the same evidence passage can be linked to its extracted claims and actions without merging existing identities. The chosen engine receives selected source passages and eligible confirmed names, aliases and descriptors for context. Library questions can also use your current saved database values, field and option labels, related item names, and authored action status, owner or date. These entries are identified separately from original source quotations. A bounded comparison request includes several relevant items together; local source IDs and revision dependencies are not part of that comparison envelope. Linked source exclusions also apply to entries derived from those sources. Source exclusions, current revisions and destination permission are checked before processing and again before saving results. You can exclude a source from AI processing, cloud AI or retrieval. On-device organization can run automatically while recording is idle, and you can turn it off. Automatic organization with an external provider requires a separate device-local permission for that destination. Local-model memory is released for recording, app backgrounding or hiding, and memory-pressure events; interrupted work retains saved results. Optional iCloud synchronization is independent of the AI choice. Model setup checks use fictional text only and do not authorize automatic library processing. On Mac, for a LiteLLM-compatible gateway, Library Ask first offers a response-format check using a fictional question and passage at your selected endpoint, using your API key. After confirmation and a successful check, it sends your question and matching library passages with your foreground destination permission. The saved setup contains the endpoint, model name, context and output budgets, and answer-schema version, not your key, question, source text or response. Hosted model aliases do not pin the underlying model weights; each answer is still validated for source quotations.
Optional iCloud library
iCloud is off until you explicitly choose a library for this device. Apple stores synchronized text, speaker labels, authored corrections, notes, supported document and image originals, database content, actions, valid generated knowledge and revision information in your Apple account's private CloudKit database. CloudKit uses encrypted record values and assets; this policy does not claim that every field has Apple's end-to-end encryption. Synopsule operates no server copy of that library. Silent Apple push notifications can wake the app to reconcile an already chosen library; they do not enroll an account or contain source text.
Playback audio, temporary recording vaults, voiceprint embeddings, API keys, AI consent, model caches, search vectors and local calendar identifiers are excluded. A transcript on another device can therefore have no playable audio there. Switching an Apple account pauses the old scope and requires the appropriate library choice; it does not silently mix libraries. Original-file download and cache eviction are separate from logical library deletion. Turning iCloud off pauses future synchronization and preserves the local library; it does not erase previously uploaded private data or independently saved backups.
Preparing an iCloud library uses a separate local database and copies retained playback audio only between folders on this device. Your current recording audio-retention preference is carried into that local library; AI consent and destination permissions are not. Audio is never included in iCloud transfers. After a complete restart, you review the library choice before it becomes current; the previous library stays available. Preparation may already synchronize authorized library text with your private Apple account. Cancelling joins the original work and removes verified duplicated playback audio when it is safe to do so. Interrupted preparations can retain local text, document and audio recovery copies. Backup settings offers deletion of verified audio copies belonging to an unselected preparation; altered or busy material is kept for recovery. Existing saved libraries and original recordings are preserved.
Previously verified migration access
If this device already holds a credential for a remaining paid Memoral period, it stays local to this device. The import and migration setup screens have been removed. Previously verified access uses a device-bound credential from the Synopsule Worker. The Worker verifies the grant's signature and binding and checks authoritative paid status with Memoral for hosted use. It stores the scoped credential's hash and content-free entitlement, usage and revocation information. This grants eligible hosted AI access for the verified period; it does not move a subscription, payment method or billing ownership to Synopsule. Local library access does not require this exchange.
Ask your meetings
"Ask your meetings" lets you ask a question across your recordings. Synopsule selects relevant passages from your recordings, notes, labeled flags and files you explicitly attach — which can span multiple meetings — for the AI option you configured: Apple Intelligence on supported devices, local Ollama on Mac, your own provider key, or Synopsule Pro. On-device options keep the text local. Cloud options require the same explicit provider consent as summaries. Audio is never sent to an AI provider.
Attached sources and note context
You can explicitly select a PDF, Markdown or plain text file for one meeting or a meeting series. Synopsule copies readable text and page information into your local library, leaving the original untouched. Scanned or unreadable pages are reported and are not searched. These copies are removed when you remove the source or delete its recording and are included in backups you create. Source text can be included or excluded in a transcript export. The local Markdown mirror used by Files and MCP includes attached text and context you kept, so connected tools can read that content under your existing file-access choices.
“Add context” uses your note, nearby transcript passages and relevant attached text. The original note is preserved separately. Suggestions are saved locally for you to keep, edit or discard; only kept, current additions enter transcript exports. Library archives preserve locally saved context and its review state. Changes to the note or quoted evidence mark old additions for review. Unrelated edits do not invalidate kept context. Removing a file or its owning recording clears dependent file quotations and the derived search cache. Cloud use requires the updated provider consent; a previous transcript-only consent does not authorize sharing notes or attached text.
Local search and optional recording context
Keyword and semantic retrieval run on your device. An optional 165 MB EmbeddingGemma 2 text model is downloaded from Hugging Face, verified against a pinned checksum, and can be removed in Settings. The download service receives normal connection information but no recording, note or source content. This model helps search; it does not generate recaps or answers. Derived search vectors stay local and can be rebuilt from the library.
Meeting context during recording is off until you enable it. It uses a bounded, temporary live-text window to find quotations in recent saved meetings locally. No AI provider is called, live drafts are not added to the persistent search index, and no extra microphone, calendar or screen data is collected. Open items from earlier recordings are displayed without another AI request.
Automatic summaries
Synopsule can summarize each recording as soon as it finishes transcribing, so a meeting isn't left sitting behind a button. This is a setting — Settings → AI Summary → Summarize automatically — and three things are true of it:
- It does nothing until you have set up a summary provider.
- It never sends a transcript to a provider you have not already consented to. An automatic run is never the moment you are asked for consent.
- It is off for an off-device provider unless you turn it on. Allowing one transcript to go to OpenAI, Anthropic, Google, or a gateway of your choosing answers a question about that transcript — it is not a standing subscription to sending every future recording. So the first time you grant that permission, Synopsule writes this setting off for you. If automatic summaries are on for an outside provider, it is because you switched them on.
On an on-device provider (Apple Intelligence or a local Ollama), an automatic summary runs on your own machine and nothing is sent anywhere.
Before the first cloud recap, "Ask your meetings" or "Add context" request for a provider, Synopsule asks for your explicit permission, names the destination provider and explains that selected transcript, note and attached text may be sent. Earlier transcript-only consent is not reused. You can revoke this permission at any time in Settings → AI Summary → Reset AI consent, and you can stop using these features entirely by simply not using them — your recordings and transcripts continue to work fully offline.
Subscriptions and payments
Subscriptions are sold through the Apple App Store. Apple processes payments — we never see your payment card information. To validate access, Synopsule sends the App Store-signed transaction token, including purchase identifiers and entitlement fields, to the Synopsule API Worker for verification. It contains no audio or library content. Migration-period access uses the separate scoped exchange described above.
Permissions
- Microphone access is requested (on Mac, iPhone, and Apple Watch) so the app can capture your voice and in-room speakers. Audio capture happens entirely on your device.
- Audio recording access (macOS only) is requested so the app can capture this Mac's system audio for remote meeting participants. The iPhone app records from the microphone only and does not capture system audio.
- Calendar access is requested only when you switch on meeting awareness, and only for reading. Synopsule uses it to offer recordings. Choosing a meeting may name a recording; other calendar event details are not saved to the library as described above. Leave the setting off and the app never asks.
- Local Network access is requested for the optional direct Mac handoff. The Mac accepts recordings only from paired iPhones. The receiving Mac does not need microphone, calendar or system-audio permission for this work.
- Camera access is requested only when you choose to scan a Mac pairing code; pasted codes and pairing files work without it.
- Notification permission is requested only when you switch notifications on, so your device can remind you about meetings or tell you a transcript is ready. Notifications are composed and delivered locally.
Microphone access is needed only to make recordings. A Mac used only to analyze iPhone recordings does not need it. You can leave the other capabilities off. You can change or revoke any of these permissions at any time in Settings → Privacy & Security on iPhone, or System Settings → Privacy & Security on Mac.
Recording other people
When you capture this Mac's system audio during a meeting, you are recording the other participants on the call. You are responsible for obtaining their consent as required by the laws and norms of your jurisdiction. Synopsule will remind you of this when you first enable system audio.
Children
Synopsule is not directed to children under 13 and does not knowingly collect data from children.
Recommending Synopsule uses your device’s share sheet and includes only the public app link and recommendation text. It does not include your recordings, transcripts, or speaker names.
Library opening diagnostics
If a library cannot open, you can choose to copy diagnostics or open a support email draft. These details contain the app version, platform, opening stage, error codes and a fixed category for content that could not be verified (such as transcript or flags), without library content, file paths, account identifiers or credentials. Nothing is sent automatically: you choose whether to send the email. Synopsule keeps a local failure category and attempt count to offer a more useful next step after repeated failures; these are cleared when opening succeeds.
Data retention and deletion
- Your library is stored locally, and in your private Apple account if you enable iCloud. Version 3 retains new audio locally by default while honoring an existing explicit deletion preference. “Keep audio after processing” controls new audio retention; existing saved audio is unchanged. Audio is never sent to Synopsule servers or cloud AI. Direct transfer to your paired Mac happens only for a recording you choose.
- You can request deletion of a recording or library item at any time. On Mac, the keep-or-delete prompt also lets you discard audio after a recording. Logical deletion excludes the item and dependent generated context immediately and propagates to devices using that iCloud library when they reconcile. Independent authored actions or corrections can remain with their source marked unavailable. Revision and recovery history can still contain older text until its retention cleanup completes; a deleted current row is not a claim that every historical byte has already been erased.
- If an action's supporting text is still updating, deletion may require a retry; the app reports this and keeps the item until deletion succeeds. Deleted actions retain only identifiers and source-range information to prevent automatic suggestions from reopening them. A late change from an offline device remains unavailable after deletion. If its exact evidence cannot be verified, automatic organization may pause or require review instead of reopening a deleted action. Cleanup of a late iCloud copy may wait for a device or missing information to become available; there is no fixed completion time. The app reports missing information or a recovery requirement rather than claiming cleanup is finished.
- The encrypted temporary vault is cleared after processing and a successful transcript save. If processing, speaker separation, or saving is unfinished, recovery audio stays on your device until you finish processing or delete the recording.
- Downloaded-file eviction removes a local cache copy only. Backups, exports, older offline devices and files you shared elsewhere are separate copies; deleting an item cannot erase those copies remotely. Removing the app does not delete your private iCloud library, backups or exported files.
Audio and transcript files you save
You can explicitly save or share a transcript in your chosen format, audio as a playable M4A file, or a ZIP containing both. Transcript exports follow your choices for summaries, notes, flags and attached text. Available audio from a stopped, unfinished recording can also be exported on-device without changing your retention preference or deleting its encrypted recovery copy. Audio from a recording still in progress cannot be exported.
You choose the destination using the system file picker or share sheet. A cloud folder or another app you select handles the copy under that service's own terms. Synopsule does not automatically upload these files. A single-recording ZIP is for reading and playback; use a library backup below when you want an archive you can restore into Synopsule.
Recording files you inspect
Inspect recordings reads the app's recording metadata, saved library copies, retained audio and encrypted recovery files on your device, independently of the Library index. It can preview available text and prepare playable copies of readable audio. It does not restore entries into the Library or change original files. Automatic analysis waits while inspection is open. A recorded audio-deletion choice remains authoritative. Saved metadata copies may contain historical text, including entries removed from the current Library; inspecting them does not restore those entries.
You may explicitly save a metadata-only inspection report, individual documents or audio, or a preservation ZIP of the original files found. The report contains file names, sizes, dates and read status, without recording titles, transcript text, audio or encryption keys. The preservation ZIP contains private recording data and is not encrypted as a whole; recovery files inside it remain encrypted, and their device-bound keys are not exported. It is not a restorable library archive. These files leave the app only through a destination you choose.
Backups you create
Backups are independent of optional iCloud synchronization. Backup in Settings (Backup & restore on a Mac) writes a portable file you place yourself; Synopsule does not upload it. A cloud folder or app you explicitly choose handles that exported copy under its own terms.
- The backup is an ordinary ZIP file. Nothing in it is encrypted or obfuscated by Synopsule, so you can open it with the tools you already have — which is the point, and also the reason to think about where you put it.
- It contains library content and revision history — transcripts, notes, files, knowledge, database definitions and values, actions and supporting evidence — and, if Include the audio is on, locally available playback audio. Device credentials, consent and CloudKit transport checkpoints are excluded. Knowledge archives require a compatible version 3 reader; the app refuses unsupported formats before restore. Older version 1 and 2 recording archives remain readable.
- You choose where it goes. If you put it on a shared drive, in a cloud folder, or in a message to someone, it is as readable there as it is on your Mac — treat it as you would the recordings themselves.
- Restoring validates the archive before applying content. Same-library history merges through its revision and deletion rules; a stale backup does not silently undo a later deletion. Bringing an unrelated knowledge library into the current one requires a preview and a separate identity namespace. Legacy recording-only archives add missing sessions without replacing an existing session.
- When you choose to open a backup as a separate library, Synopsule creates a private on-device working copy for review after restart. The current library and your original backup remain in place. A verified restore opens the separate library only after its content and files are ready. You can reopen a retained library from Backup settings. Interrupted or cancelled work may retain local recovery copies; Backup settings offers deletion of verified temporary copies without deleting the original backup or a saved library. Unrecognized or altered recovery files are preserved for recovery rather than silently adopted or erased.
- A complete knowledge backup requires its document and image originals to be available locally. The app reports an unavailable original instead of claiming a text-only copy is complete. User-created backups remain readable ZIPs that you manage independently.
Security
- Audio and transcripts are stored in your device's user-protected app directories.
- API keys are stored in the device Keychain with at-rest encryption and per-item access control.
- Our cloud AI service and model-download requests use HTTPS. Local Ollama and custom gateway connections use the address you configure.
Third parties
The table below describes cloud AI requests and model downloads. Product analytics and App Store payments are described above.
| When | Who | What is sent |
|---|---|---|
| You enable private iCloud synchronization | Apple CloudKit in your Apple account | Library text, supported document and image originals, knowledge, edits and revision information; no playback audio, voiceprints or AI keys |
| Previously verified migration-period access is used for hosted AI | Synopsule Worker; Memoral for entitlement verification | Device-bound access credential; hosted use checks content-free entitlement status |
| You generate a summary (BYO OpenAI) | OpenAI | Selected transcript and note text + your API key |
| You generate a summary (BYO Anthropic) | Anthropic | Selected transcript and note text + your API key |
| You generate a summary (BYO Google Gemini) | Selected transcript and note text + your API key | |
| You generate a summary (BYO LiteLLM) | Your chosen gateway | Selected transcript and note text + your API key (if required) |
| You generate a summary (subscription) | Synopsule API Worker → OpenAI | Selected transcript and note text + your signed App Store transaction |
| You use "Ask your meetings" with a cloud provider | The AI provider you configured | Selected transcript, note, flag and attached-source excerpts |
| You use "Add context" with a cloud provider | The AI provider you configured | Your note, nearby transcript passages and relevant attached-source text |
| You download a transcription model | Hugging Face (via the WhisperKit framework) | Standard model-download request |
| You download the "Search on this device" model | Hugging Face | Standard model-download request; no recording, note or source content |
Cloud requests use your provider key for a BYO option, or your signed App Store transaction through the Synopsule API Worker for Pro, as described above. On-device AI does not make these cloud requests.
We only share data with these third parties to provide the functionality you request, and we require that any third party with whom we share data provides the same or equal protection of your data as stated in this policy. We do not sell your data, and we do not share it with data brokers.
Changes to this policy
If we change this policy in a way that affects how your data is handled, we will update the Effective date above and describe the change on this page.
Contact
Questions or requests? Email rxv2dev@gmail.com.