Privacy

Privacy Policy

Last updated 15 October 2026. This page describes the Windows desktop app. It is not a claim that the app or this text has been reviewed, verified, or found compliant.

What this policy covers

TimeBranch is a Windows desktop calendar and visual daily planner being prepared for release. It reads and, when you allow editing, changes events in Google Calendar. This policy explains that access for the desktop app as it works today. The public site is timebranch.app.

There is no TimeBranch account. Sign-in, when you choose it, is your Google account, handled on the computer where the app is installed. The app talks to Google directly. No dedicated TimeBranch server currently receives or stores users' Google Calendar event data.

This website

This website is a static description of the product. It does not create an account, does not offer a download, does not include a form, and does not set its own cookies. It does not include an analytics tracker. The host that serves timebranch.app may keep its own connection logs. This website does not receive those logs.

Google Calendar data

The purpose of Google access is to show your calendar on the timeline and to apply the changes you make.

Scopes

• Connecting requests https://www.googleapis.com/auth/calendar.events. That scope lets the app read events and, when you save or delete, create, edit, and delete events.
• A previously stored read-only grant for https://www.googleapis.com/auth/calendar.readonly can still be restored. In that state the calendar is shown and is not edited until you allow editing.
• Allowing editing opens the browser again so a read-only grant can be replaced with permission to change events.

What the app requests

From the signed-in Google account, the app requests:

• The calendar list: calendar id, name, color, whether the calendar is primary, access role, time zone, and default reminders. Calendars you have hidden in Google Calendar are skipped.
• Events on the remaining calendars for the dates on screen: title, location, start and end, all-day flag, color, event id, calendar id, and reminder settings.

The primary calendar id is used as the account label. For a Google account, that id is often the account email address. It can appear in the app and in the local files described below.

Event list responses are requested without a field mask. Google's response can briefly include other event properties, such as a description or attendees, in memory while the app reads the response. The local event cache does not keep a description or an attendee list. A save sends the title, location, time, color, and reminders the app knows. The current event model has no description field.

When Google is contacted

• When you connect, restore a saved sign-in, or allow editing.
• When the app loads or syncs events. While you are signed in, the running app syncs on its own.
• When you save a new event, edit an event, or delete an event. Those writes go out only for that action.

Sign-in opens in the system browser and returns to the app on this computer through a local address. The app does not send that sign-in through a TimeBranch server. Short-lived access tokens stay in memory. The refresh token and the granted scope are what get saved.

Limited use

This section is written with Google's API Services User Data Policy, including its Limited Use requirements, in mind. It describes the current architecture. It is not a statement of compliance, and it has not been submitted for Google's review.

• Google user data is used to provide the calendar features you can see in the app: showing events, syncing them, and creating, editing, or deleting an event when you do so.
• It is not sold.
• It is not used for advertising, and this website does not include an ads or analytics tracker.
• It is not transferred to a TimeBranch server. The transfers that do happen are the app's requests to Google, and local storage on the computer where the app is installed.
• The current app has no feature that uses Google Calendar data to develop, improve, or train generalized artificial intelligence or machine learning models.
• Because calendar events are not uploaded to a TimeBranch server, the publisher does not receive a copy of those events through the app's normal operation. People can still read data that is stored on a computer they can access.

Where data is stored

All of the following is on the Windows computer. None of it is a TimeBranch account in the cloud. The folders below use the name MidnightCalendar, which is the name in the current Windows build. The public product name is TimeBranch.

Refresh token

The OAuth refresh token, together with the granted scope, is stored locally in Windows Credential Manager. The target name is MidnightCalendar.GoogleCalendar. The token is not written into the calendar cache. An access token is kept in memory for the session and refreshed from the saved refresh token.

Calendar cache

Calendar data is saved under %LocalAppData%\MidnightCalendar\cache. The files are unencrypted. They can contain titles, locations, dates and times, colors, calendar names and ids, time zones, reminder settings, and the account id. They do not contain access tokens, refresh tokens, or the OAuth client secret. Each account has its own file, named with a short hash of the account id. The file contents, and index.json in that folder, store the account id in plain text. That id may be an email address.

Notification history

A local history is stored under %LocalAppData%\MidnightCalendar\notifications so the same reminder is not shown twice. The files are unencrypted. An entry is a key made from the event id, the start instant, and how many minutes before the event the reminder fires, plus the time it was recorded. The event id includes the calendar id, which is often an email address. The history file does not store the event title or location.

Settings and OAuth client file

%LocalAppData%\MidnightCalendar\settings.json stores whether Windows notifications are enabled, whether notification titles are hidden, and the app's default reminder minutes. It does not store calendar events or tokens.

The Google OAuth client id, and a client secret if one was placed there, live in %LocalAppData%\MidnightCalendar\google-oauth.client.json. That file is the app's client configuration, separate from your events.

Sharing

Event data is sent to Google when the app syncs and when you create, edit, or delete an event. That is your Google Calendar, under Google's own terms.

The app does not sell Google user data and does not pass it to an advertising network. No TimeBranch server receives it. Windows may show a notification on the same computer, as described below.

Retention and deletion

The app does not delete the local cache on a schedule. Files remain until they are removed.

• Disconnect deletes the refresh token from Windows Credential Manager and clears the in-memory session. It does not call Google to revoke the grant. You can remove the app's access from your Google Account's third-party access page at myaccount.google.com/permissions.
• Disconnect does not delete the cache files or the notification history. The history is kept so that connecting the same account again does not repeat a reminder that already fired.
• To remove the local copy, delete the folder %LocalAppData%\MidnightCalendar. That removes the cache, notification history, settings, and the local OAuth client file. Disconnect as well, so the credential is removed. The app has no separate control that deletes that folder for you.
• Deleting those files does not delete events in Google Calendar. An event leaves Google Calendar when you delete it there, or when you delete it in the app and Google accepts the delete.

Windows notifications

Windows notifications stay off until you turn them on. If they are on, a notification can include the event title, how long before the event it was set, and the event time. It does not include the location. A setting can hide titles. When titles are hidden, the notification says "Calendar reminder". The notification is shown by Windows on that computer. Email reminders configured in Google are not shown as these Windows notifications.

Before Google is connected

Before Google Calendar is connected, and on platforms that do not connect to Google, the app can show sample events that ship with the program. Those samples are not your Google data. Edits to them stay in memory for that session and are not sent to Google.

iOS

An iOS version is planned and is not available. This policy describes the Windows desktop app. It does not describe an iOS app. The current mobile builds do not connect to Google Calendar.

Contact and changes

For data protection and privacy requests, write to varstaviben@gmail.com.

This page will change if the app's access, storage, or sharing changes. The date at the top will change with it.