Your meetings stay yours.

Who we are

Gorp is made by Interplex Ventures LLC, a Wyoming limited liability company, 30 N Gould St, Suite R, Sheridan, WY 82801, USA. In this policy, “Gorp”, “we” and “us” mean Interplex Ventures LLC, which is responsible for the app and this website. Questions go to privacy@gorpapp.com.

What Gorp collects

No meeting data or usage events are sent to us by default. You can explicitly send a support report with selected passage words. Gorp has no account or Gorp sign-in. You can optionally connect a Google or Microsoft calendar account, as described below. Gorp has no server that stores meetings. We have no copy of your meeting library. We see only the content you choose to include in a support report.

What stays on your Mac

Recordings, transcripts, notes, meeting materials you attach, speaker names and settings are saved in Gorp’s library on your Mac (~/Library/Application Support/Gorp). API keys you enter are kept in the macOS Keychain. Gorp can show meeting titles and summaries in Spotlight; that index stays on your Mac too, and you can turn it off.

These run on your Mac and don’t send meeting data anywhere: Parakeet and Apple Speech transcription, Gorp’s built-in writing model, Apple Intelligence, and Ollama (a separate app you install that runs locally). Telling voices apart happens on your Mac too. Gorp stores speaker names you choose, not voiceprints.

On Macs without Apple Intelligence, choose the built-in private writer during setup; if you add an OpenAI key, notes go to OpenAI unless you change the writer.

You control this data. Deleting a meeting in Gorp removes its notes, transcript, audio and attachments from the library. Backups you make yourself, such as Time Machine or iCloud Drive, follow their own rules.

Calendars you connect

Connecting a calendar is optional. In Settings → Calendar you can connect a Google Calendar or Microsoft Outlook account, or let Gorp read the calendars in your Mac’s Calendar app.

What Gorp reads: your events’ titles, start and end times, whether you accepted or declined, the names and email addresses of invitees, and any video-call link (such as Zoom, Google Meet or Microsoft Teams). Gorp also looks through an event’s description for lines labelled as spellings, such as “Terms: Nguyen, Kubernetes”; it keeps only those short terms, not the description itself. Gorp also reads the list of your calendars, so you can choose which ones it uses. Gorp does not read your contacts, email or your organization’s directory. It never creates, changes or deletes calendar events.

Why: to show today’s meetings so you can start notes for one in a click, to name a new meeting after its event, to remind you when a video meeting starts (you can turn this off), and to suggest invitees’ names when you name speakers in a transcript. Suggestions are never applied without your click.

Where it goes: Gorp reads events directly from Google or Microsoft onto your Mac. There’s no Gorp server in between. When you start notes for an event, Gorp saves that event’s title, times, video link and invitees (names and addresses) with that meeting on your Mac. Gorp also saves a few spelling hints: capitalized words from the event title (for example a company or product name) and any terms from labelled spelling lines in the description. Invitees’ names, never their email addresses, and these terms are used as spelling hints for transcription and note writing. If you’ve chosen a cloud AI provider for note writing, the names and terms are sent to that provider with your transcript, along with any spellings you noted for that meeting. Cloud transcription doesn’t use them. Your recordings and notes are never sent to Google or Microsoft.

Sign-in and deletion: Gorp keeps its sign-in tokens in your Mac’s Keychain, on that Mac only. Disconnect in Settings → Calendar deletes them and stops all reading. For Google, Gorp also revokes the token. You can also remove Gorp’s access at myaccount.google.com/permissions or account.microsoft.com/privacy/app-access (Microsoft), or for your Mac’s calendars in System Settings → Privacy & Security → Calendars. Meetings you already recorded keep the invitees saved with them until you delete those meetings.

Gorp's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Gorp uses Google Calendar data only to provide the calendar features described above. If you choose a cloud AI provider for notes, Gorp may send invitees’ names and short terms from the event title or labelled description lines as spelling hints with your transcript, as described above. We don’t otherwise transfer Google Calendar data to others, use it for advertising, sell it, or use it to train AI or machine-learning models, and no person at Gorp reads it.

How we protect sensitive data

Gorp connects to Google Calendar over HTTPS, which encrypts data in transit. Google sign-in opens your system browser and uses PKCE and a random sign-in state to protect the authorization flow. Calendar requests use a network session that does not keep cookies or a disk cache of responses.

Gorp stores Google access and refresh tokens in the macOS Keychain as items restricted to this Mac; they are not stored in your meeting files or synced through iCloud Keychain. Gorp keeps fetched events in memory for the meeting list. If you start notes for an event, the event details described above are saved in Gorp’s library under your macOS user account. macOS account access controls protect those files, and FileVault can encrypt the Mac’s storage if you enable it. Gorp does not separately encrypt the library files or backups it creates, so anyone with access to those files or backups may be able to read them. Protect copies you export or back up. Gorp has no server that stores your Google Calendar data.

AI providers you choose

Some features can use an outside AI service, but only if you set it up. When you do, Gorp sends data straight from your Mac to that provider. It never passes through us.

• Transcription with your own OpenAI or Groq API key: the meeting audio goes to that provider.
• Notes and answers with your own OpenAI, Anthropic, Google Gemini or Groq API key: your rough notes and the transcript go to that provider, with the spelling hints described under Calendars you connect. Text from attached materials is included only if you turn that on in Settings.
• Your Claude or ChatGPT subscription: Gorp passes the same text to the Claude Code or Codex app on your Mac, which sends it to Anthropic or OpenAI under your account. Codex can read files on your Mac while it works; Gorp runs Claude Code with its tools turned off.
• Assistants you connect, such as Claude, Codex or Cursor: they can read your library, and may send what they read to their own provider. They can make changes only if you turn on Let assistants make changes in Settings → Assistant; Gorp logs those changes, and you can undo recent ones in the same place.

The provider’s own terms and privacy policy apply to that data, and any costs are between you and them. Check how each one stores data or uses it for training. You can switch back to on-device choices at any time.

Downloads Gorp makes for you

Gorp downloads a local model when you prepare it, or the first time you use it if you haven’t prepared it. Parakeet, the speaker-separation and spelling-helper models, and the built-in writing models come from Hugging Face. macOS may download Apple’s speech and Apple Intelligence assets from Apple. The Ollama installer comes from ollama.com. These requests share your IP address and ordinary download details with those sites. They don’t include your meetings.

Recordings from your iPhone or Watch

The iPhone and Apple Watch recorders are coming. The Mac side is in Gorp today, in Settings → Devices, and both ways of receiving recordings are off until you set them up. Over your local network, the Mac accepts recordings only from a phone you paired, over an encrypted connection; nothing passes through us. Through iCloud, recordings travel via your own iCloud Drive, encrypted on the phone before upload, with the key kept in your iCloud Keychain. Apple can see the size and timing of those files but not their contents.

Update checks

Once a day, and when you choose Check for Updates…, Gorp fetches a small update list from dl.gorpapp.com. Update downloads come from the same place. It’s hosted on Cloudflare R2. The request shows Cloudflare your IP address and the app name and version (for example “Gorp/0.1.1 Sparkle/2.10.0”). Gorp does not turn on Sparkle’s optional system profile, so it doesn’t send your Mac model, macOS version or other system details. You can turn off automatic checks in Settings → Help → Updates.

This website and downloads

gorpapp.com’s pages have no cookies, scripts, forms or third-party resources. Cloudflare processes your IP address and browser details to deliver pages and downloads and block attacks. We use Cloudflare’s aggregate HTTP counts for requests to each versioned Gorp disk image. A request can be a retry or a partial download, so we do not call those counts unique people or installs. We do not use website traffic to identify anyone.

Optional anonymous usage counts

In Settings → Privacy, Share anonymous usage counts is off until you turn it on. If you do, Gorp sends a one-time opt-in event with app version, build and macOS major version, plus coarse results when a recording is saved, transcription or note generation finishes, or a calendar connection succeeds, fails or is cancelled. Those later events contain the app version and build, a broad provider category where relevant, and a result. They do not contain meeting titles, names, email addresses, account IDs, calendar events, transcripts, notes, recordings, attachments, files, API keys, raw errors, diagnostic logs or a device identifier.

These small events go directly to gorpapp.com over HTTPS and are stored as aggregate-oriented records in Cloudflare Workers Analytics Engine for three months. Cloudflare sees your IP address to deliver the request, but our event dataset does not store it, an IP-based hash, your user agent or a referrer. Counts can be queried by day, version, category and result. They are not a count of all users: people who leave the switch off send nothing. Turn the switch off at any time to stop new events; there is no retry queue. Because events have no identifier, we cannot locate or delete one person’s past events, and they expire automatically.

Reviewed sharing and Reminders

Gorp can add captions and audio moments to local photo copies on your Mac. The iPhone recorder, which is coming, opens the camera or photo library only when you choose to add a photo. Shared photo copies remove original GPS and camera metadata. Captions enter AI context only under your existing materials setting and selected provider.

Story chapters keep your draft separate from the source recording. You select the passages and photos, review the complete sharing preview, and export a local folder containing only that selection. Export does not publish it online. You decide who receives the folder; a selected audio range may still contain private words, so listen before sharing.

Adding a reviewed follow-up to Reminders is optional and requires an explicit click and the macOS Reminders permission. The copy includes the action text, planning details you set, completion state and a link back to its Gorp source. No recording is attached. It goes to your default Reminders list and may sync through that list’s account. Gorp checks its source links to avoid duplicate copies; it does not save unrelated reminders in your meeting library or overwrite existing copies. Local receipts are kept on this Mac, and later edits in either app stay separate. Removing a Gorp note does not remove its Reminders copy; manage that copy in Reminders.

Feedback and support email

Help → Send Feedback… lets you send a report directly from Gorp to support@gorpapp.com. Nothing is sent until you press Send feedback. You can review the message and selected details first. An optional reply address lets us respond. Open Email remains available if you prefer your own mail app.

With Include system details on, the report lists your Gorp and macOS versions, your Mac model, chip type and memory, your region setting, the names of your chosen transcription and writing providers, permission status for microphone, screen and system audio, and speech recognition, your update channel and last check time, and how many meetings are in your library. System details never include meeting titles, transcripts, notes, audio, file names, API keys or model paths. When reporting a transcript passage, its words are included only if you select Include this passage’s words in the report. Audio is not attached automatically. You can turn system details off.

Gorp also keeps a diagnostic log and crash reports as local files on your Mac. The log records events, such as “recording started” or “transcription failed”, not meeting content. Nothing is sent automatically. You choose whether to attach them to a report. In-app attachments are limited to a diagnostic ZIP of up to 512 KiB.

In-app reports travel over HTTPS through our Cloudflare website service to Resend, which delivers them as email to our support inbox. These services process the message, optional reply address and selected attachment to deliver the report. The endpoint uses request-size limits and rate limits; delivery credentials are held on the server, never in the app. Cloudflare also processes ordinary request metadata, including IP addresses, for routing and abuse limits. Resend acceptance is not a guarantee of inbox delivery.

Emails and attachments you send are kept in our email account so we can help you and fix problems. We delete them when they are no longer needed, or sooner if you ask. We don’t sell them or use them for marketing.

People you record

Gorp records only when you press Start. You are responsible for telling participants and getting any consent the law requires where you and they are. Gorp can help: it can copy a disclosure message for the call chat, and it can stop a recording and delete what it captured.

Children

Gorp is not meant for children under 13, and we don’t knowingly collect personal information from them. If you believe a child has sent us information, email us and we will delete it.

Your rights

Depending on where you live, laws such as the GDPR (EU and UK) and the CCPA (California) give you rights to access, correct, delete or move your personal information, and to object to how it’s used. Because your meetings live only on your Mac, you already hold that data and can export or delete it in Gorp. We may hold email you sent us and Cloudflare processes ordinary request data as described above. Optional usage events have no person or device identifier; they expire after three months. Ask us at privacy@gorpapp.com and we will answer within 30 days. We don’t sell or share personal information for advertising. If you’re in the EU or UK, you can also complain to your local data protection authority.

Changes to this policy

If this policy changes, we will update this page and its effective date. If a change affects what leaves your Mac, we will also say so in the app’s release notes before it applies.