Penguin for Zoom

Privacy Policy

Effective date: 15 November 2026 · Last updated: 15 November 2026

Short version. Penguin for Zoom keeps its settings on your computer. Your meeting audio, video, screen share and chat go directly between your computer and Zoom; we never see them. Our only server creates the join signature Zoom requires and keeps nothing about you after the request. No analytics, no cookies, no tracking, no ads, and we never sell or share your data.

1. Who we are

Penguin for Zoom ("the app", "Penguin") is made and run by Aviv Vaknin, an independent developer (GitHub user vaknin), referred to here as "we" or "us". We are the controller of the personal information described in this policy that our signing service and support channels process. Contact: dibs.apps@gmail.com.

Penguin is not made, endorsed or supported by Zoom Communications, Inc. ("Zoom"). Zoom is a trademark of Zoom Communications, Inc.

2. What this policy covers

This policy covers the Penguin for Zoom desktop app, the signing service we run for it, this website, and our support channels.

It does not cover Zoom. When you join a meeting, Zoom processes your meeting data (audio, video, screen share, chat, name, and so on) under its own Privacy Statement and Terms of Service. The meeting host's settings (for example recording) are controlled by the host and Zoom, not by us.

3. What data is involved, and where it goes

Data inventory
DataWhere it is keptWho receives itHow long
Settings: join muted, join with camera off, interface style, hide controls when idle, follow desktop theme, chosen speaker, and the display name you last joined withYour computer only, in ~/.config/penguin-zoom/settings.jsonNobody. (The display name is sent to Zoom when you join; see next row.)Until you change or delete the file
Display name you type on the join screenYour settings fileZoom, when you join, so other participants see itOn your computer: until you change it. At Zoom: per Zoom's policy
Meeting number and passcode (from the link you open)App memory while it runsZoom (both, to join). Our signing service (meeting number only, see section 5)Gone when the app quits. Not stored by our signing service
Zoom sign-in tokens (OAuth access token and refresh token)Access token: app memory only. Refresh token: your system keyring (for example GNOME Keyring), so you stay signed in after a restart; never in a plain fileZoom's API. For joining as host only, the access token is sent to our signing service for a one-time checkAccess token until you quit; refresh token until you sign out, Zoom rejects it, or it expires (Zoom: 90 days)
ZAK (Zoom's short-lived join token for your account)App memory, for the few seconds of joiningZoom (it goes back to Zoom to join the meeting as you)Discarded after the join; it expires within minutes
Meeting audio, video, screen share, chat messages, participant listNot stored by the appDirectly between your computer and Zoom. We never receive themNot kept by us. At Zoom: per Zoom's policy
Camera and microphone preview on the join screenShown on your screen onlyNobody until you joinNot kept
Audio device list and speaker routing; desktop theme coloursRead from your computer when neededNobodyNot kept (except your speaker choice in settings)
Diagnostic messages the app prints (tokens and signatures are masked)Your terminal or your system log, if your desktop captures itNobody; we only see them if you paste them into a support requestAs your system keeps logs
Your IP address, when the app calls our signing serviceSigning service memoryNobodyUsed only for rate limiting, in memory; never written to disk
Zoom's deauthorization notice (sent by Zoom when you remove the app from your Zoom account)Not storedNobodyNot kept; we hold no account data to delete
What you send us for support (GitHub issue, email)GitHub (issues are public) or our mailboxGitHub, our email providerAs long as needed to help you; you can ask us to delete emails

The app runs a small web server for its own window. It listens only on 127.0.0.1 (your own computer), cannot be reached from the network, and refuses requests from other websites.

We do not collect analytics, telemetry or crash reports, and the app and this website set no cookies and contain no trackers or advertising.

4. Data the app gets from Zoom

Zoom requires apps like Penguin to join meetings as a signed-in Zoom user, so you sign in with your own Zoom account before joining. When you sign in, Zoom asks you to approve the app and gives it tokens for your account. The app asks Zoom only for:

The app does not read your meetings list, contacts, recordings, chat history or any other Zoom data, and it does not change anything in your Zoom account.

The access token is held only in the memory of the running app. The refresh token, which keeps you signed in after a restart, is stored in your system keyring (for example GNOME Keyring), never in a plain file. "Sign out" in Settings revokes the token with Zoom and deletes both.

5. Our signing service

Zoom requires every join to carry a signature made with the app's secret key. To keep that key off your computer, a small service we run on Oracle Cloud (over HTTPS) creates it. For each join it receives:

The service does not store meeting numbers, tokens or IP addresses, keeps no request logs that identify you, and has no database of users.

When you remove the app from your Zoom account, Zoom sends the service a deauthorization notice. Because we store nothing about you, there is nothing to delete; the service acknowledges the notice and discards it.

6. Why we use data, and legal bases

We do not use any data for advertising, profiling, selling, or training machine-learning models, and we do not make automated decisions about you.

7. Who we share data with

We do not sell personal information and do not share it for cross-context behavioural advertising, as those terms are used in the California Consumer Privacy Act (CCPA/CPRA).

8. How long data is kept

9. After you remove the app

When you sign out, remove the app from your Zoom account, or uninstall it, we hold no data about you to delete: our signing service never stored any. Your settings file stays on your computer until you delete it. How to do each of these is in the documentation. Data that Zoom keeps about your meetings is handled by Zoom.

10. Security

All traffic to Zoom and to our signing service uses HTTPS. Sign-in uses OAuth with PKCE, so no app secret ships with the app. The app's local server only accepts requests from its own window. The sign-in token that keeps you signed in is stored in your system keyring (for example GNOME Keyring), never in a plain file; other tokens are kept in memory only, and all tokens are masked in diagnostic output. No method is perfectly secure; please report security problems privately to dibs.apps@gmail.com rather than in a public issue.

11. Your rights and how to use them

Depending on where you live (for example under the EU/UK GDPR, the Israeli Privacy Protection Law, or the CCPA/CPRA in California), you may have the right to:

To make a request, email dibs.apps@gmail.com with the subject "Privacy request". We will answer within 30 days. Because the app keeps your data on your own computer and our service stores nothing, in most cases the answer is that we hold no data about you; you can delete the local data yourself as described in the documentation. For data Zoom holds, contact Zoom as described in its Privacy Statement.

12. International transfers

We are based in Israel. Our signing service runs in an Oracle Cloud data centre in Israel Central (Jerusalem), and GitHub's servers are mainly in the United States. Data that passes through these services may therefore be processed outside your country. Where the law requires, we rely on appropriate safeguards such as adequacy decisions or standard contractual clauses offered by these providers.

13. Children

Penguin is not directed to children under 16, and we do not knowingly collect personal information from them. Zoom's own age rules also apply to Zoom accounts. If you believe a child has sent us personal information, contact us and we will delete it.

14. Changes to this policy

If we change this policy, we will update the date at the top and keep the previous versions in the site's public history on GitHub. If a change affects what data we collect or how it is shared, we will also note it in the app's release notes before it takes effect.

15. Contact

Aviv Vaknin · Email: dibs.apps@gmail.com · General questions: GitHub Issues (public; do not post personal information there).