Privacy Policy

Last updated: October 14, 2026

Jiva is a meeting recorder, transcriber, and assistant for macOS. It is designed to be fully local: your meetings, transcripts, dictations, and any connected data are processed and stored on your own Mac. We do not run servers that receive your content, and Jiva has no user accounts.

The short version: Everything Jiva captures or connects to stays on your device. We can't see it, we don't collect it, and we never sell or share it. The only data that leaves your Mac is a request you initiate directly to a third party you connect (such as Google, to read your own calendar).

Information Jiva handles

Jiva works with the following, all of it on your device:

Audio and transcripts. Meeting audio you record, the transcripts and summaries generated from it, and hands-free dictations. These are written to a folder on your Mac and are not transmitted to us.
Speaker information. Voice characteristics used to recognize recurring speakers across your meetings, stored locally.
Calendar data (only if you connect it). See the next section.

Google Calendar data

If you choose to connect your Google Calendar, Jiva requests read-only access to your calendar (the calendar.readonly scope). Here is exactly how that data is handled:

What we access: your upcoming calendar events — their times, titles, locations, descriptions, and attendee information — for the purpose of finding meeting join links and who is on the call.
How it is used: solely on your Mac, to notify you shortly before a meeting begins, to give you a one-click link that opens the meeting and starts recording, to name each recording after its calendar meeting, and to label participants in your transcripts. It is not used for advertising and is never used to train any AI or machine-learning models.
Where it is stored: only on your device. The authorization token and any fetched event details are kept in Jiva's local application-support folder on your Mac.
Who it is shared with: no one. Calendar data is never transmitted to Jiva (we operate no servers that could receive it) and is never sold or shared with third parties. The only network exchange is directly between your Mac and Google's own APIs, which is required to read your calendar.
How to revoke it: disconnect the calendar inside Jiva at any time (this deletes the stored token), or revoke Jiva's access from your Google Account at myaccount.google.com/permissions.

Jiva's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect your data

Jiva protects your information, including the Google Calendar data you choose to connect, with the following safeguards:

Kept on your device, with no central copy. Jiva runs no servers that receive your content. Your recordings, transcripts and calendar data never reach us, so there is no Jiva database that could be breached and no Jiva staff member who can access your data.
Encrypted in transit. Every connection Jiva makes to Google (sign-in, token exchange and reading your calendar) uses HTTPS (TLS) with certificate verification. Calendar data is never sent over an unencrypted connection.
Secure sign-in. Jiva connects to Google using OAuth 2.0 with PKCE and a loopback redirect to your own Mac (127.0.0.1). You sign in on Google's own page in your browser, so Jiva never sees or stores your Google password.
Least-privilege access. Jiva requests read-only calendar access only, so it cannot create, change or delete your events. Each sync fetches only the events in the next 12 hours, and when a recording finishes Jiva looks up only the event during that recording, to name it. Nothing from that lookup is stored except the recording's title.
Protected token storage. The Google authorization token is saved in a file that only your macOS user account can read (file permission 0600), inside your user Library folder. Other users on the same Mac cannot read it.
Encryption at rest. Jiva keeps its data in your macOS user Library, protected by your Mac's account permissions. When FileVault (macOS's built-in full-disk encryption) is turned on, all of it is also encrypted at rest. We recommend keeping FileVault on.
Minimal retention. The list of upcoming events is replaced on every sync rather than accumulated. Disconnecting the calendar in Jiva deletes the stored token immediately, and deleting Jiva's data folder removes everything Jiva stored.
Reporting a concern. If you believe you have found a security issue, email ceo@jiva.works and we will respond promptly.

Data we do not collect

The Jiva app has no accounts, no analytics, and no advertising. We do not build user profiles and we do not track your usage. To let you know when a new version is available, the app may request a small version file from our software-distribution host; that request does not include any of your personal data or content. This website (jiva.works) uses Umami, a cookieless analytics service that counts page visits without identifying you, and offers an optional live-chat widget run by Tawk.to. Anything you type into the chat is handled by Tawk.to under its own privacy policy.

Data retention and deletion

Because your data lives on your Mac, you are in control of it. You can delete recordings, transcripts, dictations, and the calendar token at any time by removing them from Jiva or from your Mac's file system. Uninstalling Jiva and clearing its data folder removes everything it stored.

Children

Jiva is a professional productivity tool and is not directed to children under 13.

Changes to this policy

If we change this policy, we will update the date above and post the revised version at this address. Material changes will be reflected here before they take effect.

Contact

Questions about this policy or your data? Email ceo@jiva.works.