The receipt, in full.

Reproduce it yourself

You don't need to be a network engineer. Either tool below shows you, live, every connection an app on your Mac makes. Install one, run logga through a full session, and compare what you see against the table above. Budget five minutes.

With Little Snitch (the easy way)

1. Install Little Snitch. Its free demo mode is enough for this, and the lighter Little Snitch Mini works too.
2. Open the Little Snitch Network Monitor from your menu bar. It lists every app and every server it talks to.
3. Launch logga. Start a recording, talk for a minute, stop, and let it transcribe and summarise.
4. Find logga in the Network Monitor's app list.
5. Compare against the table. At launch you'll see api.lemonsqueezy.com. On a first run you'll also see huggingface.co and github.com while the models download. During recording, transcription and local summarising: nothing at all.

With Wireshark (the thorough way)

1. Install Wireshark. It's free and open source, and it captures raw network traffic, so nothing can hide from it.
2. Start a capture on your active interface (usually Wi-Fi). Quitting other apps first keeps the capture easier to read.
3. Run a full logga session: record, transcribe, summarise.
4. Stop the capture, then type tls.handshake.extensions_server_name into the display filter bar and press Enter. Each remaining line names a server your Mac contacted, readable even though the traffic itself is encrypted.
5. Any other apps still running will show their own servers. The check that matters: the only logga destinations you'll find are the ones in the table, and your meeting audio never appears in the capture at any size, because it is never sent.

What each call carries

1 · Licence check

At launch, logga contacts api.lemonsqueezy.com, our payment and licensing provider, to confirm your licence is valid. The request carries three things: your licence key, a hashed machine ID, and the app version. The hashed machine ID is a one-way fingerprint that stops one licence being shared endlessly; it can't be reversed into anything about you or your Mac. What's never in the request: audio, transcripts, summaries, meeting titles, file names, or content of any kind. If you're offline, logga keeps working for 7 days between successful checks, so a week off-grid changes nothing.

2 · Model downloads

On first run, and only when you click to start it, logga downloads the models that do the actual work: Whisper for transcription, pyannote for speaker diarisation, and a local summarisation model. About 3.5 GB in total, fetched over standard HTTPS from huggingface.co and github.com. Every file is checked against a SHA-256 checksum pinned inside the app, so a tampered or corrupted download is rejected rather than installed. The models live on your disk afterwards and are never re-downloaded unless you delete them.

3 · Cloud summaries, optional and off by default

Local summaries are the default and need no network connection at all. If you want a bigger model to write your recaps, you can add your own API key for a provider you choose. When you do, logga sends transcript excerpts, and only transcript excerpts, to that provider. Never audio. Never anything unless you've switched it on. Remove the key and the app is fully local again. Your key, your provider, your call.

4 · Update check

The auto-updater in this build ships dormant. It makes no requests, scheduled or otherwise, which is why its row in the table reads "Nothing". When automatic updates go live in a future release, we'll document exactly what the updater sends, on this page, before it makes its first call.

What we don't collect

The receipt is short because there's genuinely nothing else. Specifically:

• No telemetry. There is no usage tracking in the app. We can't see what you record, how often you record, or whether you opened the app today.
• No analytics. No analytics SDK ships in the build. There are no "anonymous usage statistics", because anonymised data is still data we'd rather not hold.
• No crash reporting. Nothing is sent automatically when something goes wrong. If logga misbehaves, you tell us by email, on your terms.
• Logs stay local. The app's logs are plain-text files on your disk. Open them in any text editor and read exactly what logga has been doing. They go nowhere else.

Who's behind this

Logga is built by Papi Labs, a UK product studio founded by Saman Taherimoud. It's not an anonymous app with a template privacy policy: there's a named founder, a company you can look up, and a real inbox. If anything on this page is unclear, or you spot something in your own network trace you can't explain, email hello@logga.ai and the person who built the app will reply.

We publish this page because the whole product rests on it. A privacy-first tool that overclaims loses everything the first time someone runs Wireshark, so we'd rather write down exactly what happens and invite you to check.

Honest caveats

Two things sit outside logga's control and are worth knowing about:

• Your own backups. Time Machine or iCloud may copy logga's local files as part of backing up your Mac, like any other files on your disk. That's your backup, under your control in System Settings, and it never involves us.
• Company-managed Macs. If your Mac is managed by your employer through MDM, your IT team can read the local disk, again like any other files. Logga sends them nothing; it simply stores files on a machine they administer.

In both cases the data flows are yours or your organisation's, not ours. We mention them because a trust page that skips the awkward bits isn't one.

Last updated: July 2026 · reflects the current pre-launch build