Skip to content
yadacall
GitHubDownload
← Back to the homepage

Privacy policy

In short: YadaCall is a program for your computer. Audio and transcripts never leave it, we have no server and no accounts, and the app only reads Google Calendar data and keeps it on your device.

01Who we are

YadaCall is a free, open-source (MIT) desktop app that records and transcribes calls. It is developed by the GitHub project limeflash/yadacall; “we” in this text means that project.

The app has no servers and no accounts. We do not receive your recordings, transcripts, names, email addresses or anything else you do in the app: all of it stays on your computer.

02Audio and transcripts

  • Audio is recorded and processed only on your computer: transcription is done by models that run locally, with no internet needed.
  • Meetings are stored as plain files in a folder you choose: the transcript (transcript.md, transcript.json), the summary and, if you choose to keep it, the audio as FLAC.
  • Audio retention is a setting: don’t keep, 7 days, 30 days or forever. Text and summaries stay until you delete them.
  • We never receive your audio or transcripts. There is nothing to request from us because we do not have it.

03What goes over the network

The app connects to the internet only in these cases:

  • Downloading models (Hugging Face and the hf-mirror mirror) and app updates (GitHub). These requests contain none of your audio or text; the servers, like any website, see the IP address of the request.
  • Google Calendar — only if you connected a Google account yourself (see “Google user data” below).
  • A calendar via ICS link — if you added one, the app downloads its events from that link.
  • A cloud summary provider — only if you pick one in settings: Ollama (local or Ollama Cloud), Anthropic (Claude), OpenRouter or any OpenAI-compatible server. In that case the text of the transcript (in full or in fragments, for example for summaries or questions across meetings) is sent to the provider you chose and handled under that provider’s own privacy policy. Audio is never sent. API keys are kept in the system keychain (Keychain / Credential Manager). If you choose on-device summaries or “No summaries”, no text leaves your computer.

The app shows exactly what went out, for example “6 text fragments to Claude, no audio.”

04Google user data

Signing in with Google is optional. If you connect a Google account, the app asks for read-only access and exactly these permissions (scopes):

  • openid, email, profile — to know which account is connected and to show its name and address;
  • https://www.googleapis.com/auth/calendar.events.readonly — events in your calendars (title, time, meeting link, attendees);
  • https://www.googleapis.com/auth/calendar.calendarlist.readonly — the list of your calendars, so shared and team calendars show up too.

How we use it

Only inside the app and only for calendar features: to show your upcoming meetings, remind you 1, 2 or 5 minutes before a call, open the meeting link in the right Google account, and suggest participant names for speaker labels in the transcript. The app never creates, edits or deletes anything in your calendar.

Where it is stored

  • Calendar events are processed and cached on your device.
  • Google sign-in tokens are stored in the operating system keychain (Keychain / Credential Manager); the access token is kept in memory only.
  • This data is never sent to us or to any third party, never used for advertising, never sold, and never used to train AI models. No humans read it.

How to revoke access and delete the data

  • In the app, disconnect the Google account: the token is revoked at Google, removed from the keychain, and the account’s events are dropped from the app.
  • Or revoke access on Google’s side: myaccount.google.com/permissions.

Google API Services User Data Policy (Limited Use)

YadaCall’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.

05Telemetry, analytics and cookies

The app has no telemetry, analytics, crash reporting or trackers.

This website has none either: no cookies, no counters, no ads, no third-party scripts or fonts. The site’s only network request goes to api.github.com to show the current version and download links; the answer is remembered in your browser for an hour. The site is hosted on GitHub Pages — GitHub, like any host, may keep its own request logs under its own rules.

06Children

YadaCall is not directed at children and does not collect data about anyone, children included: we hold no user data at all.

07Changes to this policy

If the policy changes, the new version will be published on this page with a new date, and the history is available in the project repository. We will also mention significant changes in the release notes.

08Contact

Questions, remarks and privacy requests: please open an issue in the project’s GitHub Issues.