Privacy Policy

Last updated 12 August 2026

The short version Clawd Calendar has no server and no database. Your calendar data is requested by the app on your own Mac, shown to you, and never sent anywhere else. Nothing is collected about you, because there is nowhere for it to be collected to.

Clawd Calendar ("the app") is an independent macOS application. This policy explains exactly what data the app touches, why, where it is kept, and how to remove it. It covers the macOS app distributed from this website.

Who is responsible

Clawd Calendar is made and operated by an individual developer, reachable at dhruvsingh2084@gmail.com. There is no company, no staff, and no third party with access to anything described here.

Google user data the app accesses

The app asks your permission for two Google OAuth scopes, and no others. You grant them once when you connect your account.

Scope	What it reads or writes	Why the app needs it
`.../auth/calendar.events`	Reads events in your primary calendar within a short window around the present time — title, start and end time, location, meeting link, organiser, and the attendee list with each person's response. Writes back only your own attendance response when you press RSVP Yes or RSVP No.	These are the details the reminder puts on screen, and the reason it knows when to appear. The write is what makes the RSVP buttons work; the read-only alternative would remove that feature entirely.
`.../auth/userinfo.email`	Reads your Google account's email address. Nothing else from your profile.	So the menu bar can show which account is connected. Without it the app cannot tell you whose calendar it is watching.

How that data is used

Google user data is used for exactly one purpose: showing you your own upcoming meeting on your own screen, and acting on the buttons you press. Specifically:

Event details are drawn on the reminder that appears before a meeting.
Start times determine when a reminder is due, and whether one has already been shown.
Your email address is displayed in the menu bar menu.
Pressing RSVP Yes or RSVP No updates your response on that event in Google Calendar.
Pressing Join opens the meeting link in your browser. Pressing the copy icon puts the link on your clipboard.

Where it is stored

On your Mac, and nowhere else

Your OAuth tokens — the access token, the refresh token, and your email address — are stored in the macOS login keychain, encrypted at rest by macOS. They are never written to preferences, never written to a log line, and never transmitted anywhere except to Google when renewing the token.
Event details are held in memory only. The app keeps the most recent calendar response in memory so it can check every ten seconds whether a reminder is due. It is replaced on the next fetch and lost when the app quits. Event titles, locations, guest names and meeting links are never written to disk.
A record of what has already been shown is stored in the app's local preferences, so a meeting does not remind you twice. Each entry holds the event's identifier, its start time, when it was shown, and any snooze time — no titles, no guest names, no links. Entries are deleted automatically two hours after the event's start.
Your settings — how far ahead to remind, snooze length, and the two skip options — are stored in the same local preferences.

Who it is shared with

Nobody. To be concrete about what does not happen:

There is no Clawd Calendar server, so your data is never uploaded to one.
No analytics, telemetry, crash reporting or usage tracking of any kind.
No advertising, no advertising identifiers, no profiling.
Your data is never sold, rented, or transferred to anyone.
No human — including the developer — can see your calendar data.
Google user data is never used to train any artificial intelligence or machine learning model.

Network connections the app makes

The app contacts exactly two places:

Google — accounts.google.com, oauth2.googleapis.com and www.googleapis.com, to sign in, renew the token, read your calendar and write your RSVP.
This website — about once a day, to ask whether a newer version has been released, and to download it if you choose to update. The request goes to clawd-calendar.vercel.app, which serves this same site under its original hostname; update checks were deliberately left there because that address cannot lapse, and an installed copy that could no longer find updates would be far worse than a broken link. This request carries no personal data and no calendar data. Like any web request it necessarily reveals your IP address to the host, which tells us only that some copy of the app checked for an update. No identifier is attached, and no record is kept.

Limited Use disclosure

Clawd Calendar's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How to revoke access and delete your data

Two independent ways, either of which is sufficient:

In the app — menu bar → Sign out. This deletes the stored tokens from your keychain immediately and clears the record of shown reminders. The app stops contacting Google.
From your Google account — visit myaccount.google.com/permissions, find Clawd Calendar, and remove access. The app's tokens stop working at once.

Deleting the app removes it and its local preferences from your Mac. Because no copy of your data exists off your machine, there is nothing else to request the deletion of — but if you would like confirmation of that in writing, email the address below and you will get it.

Children

The app is a work tool and is not directed at children under 13. No age information is collected, because no personal information is collected at all.

Security

Tokens are kept in the macOS login keychain rather than in a settings file. Sign in uses the authorization-code flow with PKCE, and the callback listener is bound to your machine's loopback interface only. Application updates are signed with a private key and verified by the app before installation, so a compromised host or a hostile network cannot deliver code to your Mac. No system is perfect, and the app's remaining limitations are documented publicly rather than hidden.

Changes to this policy

If this policy changes, the revised version will be posted here with a new date at the top. Any change that would broaden what data is collected or who it is shared with would require your consent through a fresh Google sign-in.

Contact

Questions about this policy, or about your data: dhruvsingh2084@gmail.com.