This policy is in English. A Croatian version is available on request: [email protected].
This page covers the TalkLog app that you install on iPhone, iPad and Apple Watch. The memrelay service itself, which TalkLog can connect to, has its own policy: memrelay Privacy Policy. If you use both, both apply.
TalkLog records meetings on your device and turns them into a transcript, a summary and private coaching. This policy says what stays on the device, what leaves it, where it goes, and what you can switch off. In it, "the App" means TalkLog, and "we" and "us" mean the team that builds TalkLog and operates the memrelay service it can connect to.
1. Summary
TalkLog records meetings on your device, sends audio to third-party speech-to-text and AI services solely to produce a transcript and meeting analysis, and stores the result locally on your device and (if iCloud is enabled) in your private iCloud account.
Your content is not what we measure. Recordings, transcripts, who said what, meeting titles, participants and anything from a connected knowledge base are never part of the usage and error reports in section 3. Content goes only where you send it: the transcription and AI services you hold the keys to, your private iCloud, and your own memrelay workspace if you connect one, where it is held for you and governed by your memrelay agreement.
If you connect a memrelay workspace, some calendar detail goes with it. To prepare your brief, the App sends the title, the date and the invitees of the meetings in your day to that workspace, and an invitee is identified by the email address on the invite (by their name when the invite carries no address). This happens only while the connection is on, and section 7 describes it in full.
We do measure how the app is used and where it breaks. Privacy-first analytics: usage and error reports, never your content. Section 3 lists exactly what is in a report, and you can switch it off in Settings.
You provide your own API keys for the third-party services. Those services process your data under their own terms.
2. Data we collect on your device
TalkLog stores the following on your device (and syncs to your private iCloud if you have iCloud Drive enabled for the app):
Audio recordings (deleted automatically after a successful transcription unless you intervene)
Transcripts, summaries, action items, and coaching analysis
Speaker hints (people, companies, nicknames) you choose to add
Your user profile (name, role, optional notes about how you want to be coached)
API keys you enter for third-party services (stored in the iOS Keychain)
Calendar events you grant access to, read on the device to suggest meeting titles and attendee names. If you connect a memrelay workspace, the title, the date and the invitees of your meetings are also sent there to prepare your brief, an invitee being identified by their invite email address (see section 7).
Approximate location at the start of a recording, used to tag where the meeting took place. It travels off the device only inside a meeting export, as described in sections 6 and 7.
None of this leaves your device except as described in sections 3 to 7.
3. Usage and error reports
TalkLog measures how the app is used and where it fails. We do this on purpose: it is how we see which features people actually reach for, where they get stuck, where the app breaks, and how much the transcription and AI calls cost. It is also how support can tell that something is wrong before you have to write to us.
What a report contains
App opens, recordings started and stopped (recording mode, duration, whether you stopped it or something interrupted it)
Transcription and AI calls: which engine and model, token counts, latency, estimated cost, and what the call was for (summary, coaching, brief, and so on)
Which features you used (summary, coaching, brief, vault export, speaker fixes, watch recording, and so on)
Whether sending a meeting to memrelay succeeded or failed
Errors: the subsystem, an error family, a numeric code, a key from a fixed catalogue of failure meanings, and whether the app went down with it
App version, operating system and its version, and device class (iPhone, iPad, Mac)
Country, read from your device region setting
Who a report is tied to
If you have connected a memrelay account, reports carry that account's email address, and its workspace and role when the app knows them. That is deliberate: it lets us see that you have five failed uploads instead of that someone does.
If you have not connected an account, reports carry a random identifier generated when you installed the app. It is not the advertising identifier, it is not derived from your device, and it is not shared with anyone.
Reports are never used to track you across other apps or websites, are never sold, and are never shared with advertisers or data brokers.
What is never in a report, under any circumstance
Audio, transcripts, summaries, action items, or coaching analysis
Who said what, participant names, or meeting titles
Anything from a connected knowledge base, and any file name or path
Your precise location, and your IP address
That boundary is enforced by the code, not only by this promise. Every report is assembled from a fixed list of properties whose values can only be a number, a true or false, a version, a random identifier, or a word from a closed list written into the app. There is no path for free text (a meeting title, a transcript line, a raw error message) to enter a report, and a report that does not match that shape is discarded before it is sent rather than sent and cleaned up afterwards.
What that boundary does and does not say. It is about usage and error reports, and only about them. It is not a claim that nothing else ever leaves your device: sections 4 to 7 describe the paths that do carry content, including the audio sent for transcription and, if you connect a memrelay workspace, the meeting titles and the invitees (by email address) sent there to prepare your brief.
Where reports go. To PostHog Cloud EU (eu.i.posthog.com), into a project we control, as our data processor. We switch off PostHog's IP-based location lookup and send a placeholder address, so no IP address and no city is recorded on their side. The country in the report comes from your device settings instead.
How to turn it off. Settings, then Privacy, then "Usage & Error Reports". Reports are on by default. Switching the toggle off stops all sending immediately and deletes anything still queued on the device. Nothing is sent from that point on, not even anonymously.
Storage on your device. When you are offline, reports wait in a small local queue (at most 300 reports or 7 days, whichever comes first) and are sent when a connection returns. Older ones are dropped rather than kept.
4. Data sent to third parties
To produce transcripts and meeting analysis, the App sends data to the services you have configured with your own API keys:
Soniox (terms, privacy) receives the audio of each recording. Used for live and post-recording speech-to-text.
Anthropic Claude API (privacy) receives the transcript text and short context derived from your profile and entity hints. Used for summary, action items, meeting type classification, and coaching analysis.
These services process your data under their own privacy policies and terms. We do not have access to those services on your behalf; you control them through your own API keys.
One more service receives data, and it never receives content:
PostHog Cloud EU (privacy) receives the usage and error reports described in section 3, as our data processor, into a project we control. No audio, no transcripts, no meeting titles, no participants.
Apart from those, and apart from a memrelay workspace if you connect one (section 7), the App does not transmit your audio, transcripts, profile, or anything read from your calendar to any server.
5. iCloud sync
If you enable iCloud Drive for the App, your transcripts, profile, and entity hints are stored in your private iCloud database. Apple, not us, hosts this data, and we have no access to it. See Apple's Privacy Policy for how Apple handles iCloud data.
6. iCloud Drive Vault
The App can read meeting briefs from and write meeting exports to a folder in your private iCloud Drive at iCloud Drive, TalkLog, Vault:
briefs/ holds markdown files you place there manually (or generate yourself from another tool). The App reads these to pre-load meeting context (agenda, goals, attendees) before recording.
incoming/ is where the App writes a markdown export of each meeting (summary, decisions, action items) when you tap "Push to Vault" or have auto-push enabled in Settings. Files contain the same data already stored on your device.
This folder lives entirely in your private iCloud Drive. We have no access to it. You can disable auto-push in Settings under iCloud Vault, manage files via the iOS Files app, or delete the folder at any time.
7. memrelay workspace (optional, off by default)
The App can connect to a memrelay workspace, the knowledge base service the App is built to feed. This is off unless you turn it on in Settings and sign in, and everything below happens only after you do:
When you push a reviewed meeting, the App sends that meeting's markdown export to app.memrelay.com, where it lands in your workspace for review. It is the same document the Vault export contains: summary, decisions, action items, plus the heading fields that identify the meeting (title, date, attendee names and, where the calendar invite supplied them, attendee email addresses, and the place the recording was tagged with).
Before a meeting, the App asks your workspace for context about the people and topics involved. To ask, it has to say what the meeting is, so it sends the meeting's title, the date and the invitees, taken from your calendar, to app.memrelay.com. Each invitee is identified by the email address on the invite, because that is the only way your workspace can tell for certain which person it is; where an invite carries no address, their display name is sent instead. The address is used to look the person up in your own workspace, it is not shown back to you in the brief. Nothing else from a calendar event is sent: not the invite notes, not the location, and not the conference link. This is how the calendar detail described in sections 2 and 8 leaves your device.
That request is made when you open Today's Brief, and also when the App refreshes the brief in the background as you come back to it, so it can happen without you tapping anything. What comes back is your own knowledge base content.
Your account's email address, workspace, and role are then also attached to the usage and error reports described in section 3.
A meeting goes to your workspace when you send it, or, if you leave push enabled for that meeting, when the app delivers it after your review. You can exclude any individual meeting, and turning the connection off in Settings stops all of it. Your workspace content is governed by your memrelay agreement and the memrelay Privacy Policy, not by this one.
8. Calendar, microphone, location, and notifications
The App requests these permissions at first use:
Microphone is required to record meetings. Audio is captured only while you actively start a recording.
Calendar is optional. It is read on the device to show meeting context, suggest titles, and pre-populate attendee names as speech-to-text vocabulary hints. The App never uploads your calendar itself. If you connect a memrelay workspace (section 7), the title, the date and the invitees of the meetings in your day are sent to that workspace, an invitee being identified by their invite email address, so it can prepare your brief. If you do not connect one, nothing read from your calendar leaves your device.
Location is optional. A coarse location stamp is captured when you start a recording so you can see where a meeting took place. The place name travels off the device only inside a meeting export you push (sections 6 and 7); no latitude or longitude is ever sent.
Notifications are optional. They alert you when long transcriptions complete or when a watch-initiated recording needs the iPhone to come to the foreground.
You can revoke any permission at any time in iOS Settings under TalkLog.
9. Children
TalkLog is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect data from children.
10. Data retention and deletion
All app data lives on your device. To delete it: uninstall the App. To delete your iCloud copy: open iOS Settings, then your Apple ID, then iCloud, then Manage Storage, then TalkLog, then Delete Data.
Three things persist outside your device, and each is deleted where it lives:
Usage and error reports. To stop new ones, switch off "Usage & Error Reports" in Settings. To have the reports already collected about your account deleted, email us at the address in section 13 and we will remove them from our PostHog project.
What the third-party services hold (section 4). Their retention is governed by their own terms, under the API keys you control.
What you sent to a memrelay workspace (section 7). Meeting exports live in your workspace and are deleted there, under your memrelay agreement. Brief requests are read requests: what the service keeps about them is covered by the memrelay Privacy Policy, not by this one.
11. Security
API keys are stored in the iOS Keychain. Audio and transcripts are stored in your app's sandboxed Documents directory and (optionally) in your private iCloud database. We rely on iOS, iCloud, and the third-party services you configure for transport-layer and at-rest security.
12. Changes
If we materially change this policy, we will update the "Last updated" date and, where appropriate, surface an in-app notice.
13. Contact
For questions about this Privacy Policy or the App in general, email [email protected].