belki

Legal information

Privacy Policy

This policy explains what stays in your vault, what the optional Google Calendar integration accesses, and where that information is stored.

Last updated: July 14, 2026

1. Overview

belki is an open-source task manager built as an Obsidian plugin. Its core task functionality is local-first: belki reads and writes task data inside the Obsidian vault you choose to use.

This website is an informational site. It does not provide user accounts and does not receive task files, Google OAuth tokens, or Google Calendar event data.

2. Task data

belki task data is stored as Markdown files inside a configurable data folder in your Obsidian vault. belki does not operate a server that receives or stores those task files.

You may independently choose to synchronize your vault with a service such as Obsidian Sync, iCloud, Dropbox, or Git. Those services operate under their own terms and privacy practices. belki does not control or take responsibility for a sync provider you choose.

3. Optional Google Calendar integration

If you enable the optional Google Calendar integration, belki requests read-only access to:

  • the list of calendars available to the connected Google account; and
  • events from calendars you select, as needed to show them in belki.

For that display, belki uses the following event information:

  • event title;
  • start date and time;
  • end date and time;
  • all-day status;
  • source calendar name and color;
  • the Google Calendar event link;
  • event and calendar identifiers required for the integration to operate; and
  • the connected account email, only when Google returns it and belki needs it to show connection status.

The integration is optional and read-only. Calendar events appear above belki task rows in existing Today and Upcoming date sections. They are not converted into belki tasks.

4. Google Calendar scopes

belki requests these two Google OAuth scopes:

https://www.googleapis.com/auth/calendar.calendarlist.readonly

Used to read the calendars available to the connected account so you can choose which calendars are visible in belki.

https://www.googleapis.com/auth/calendar.events.readonly

Used to read selected calendar events and display them inside the Today and Upcoming views.

Neither scope gives belki permission to create, modify, complete, or delete Google Calendar events.

5. Data not intentionally requested

belki does not intentionally request, use, retain, or display:

  • event descriptions;
  • attendee lists or guest email addresses;
  • event attachments;
  • conferencing information;
  • Google Contacts;
  • Gmail data;
  • Google Drive files; or
  • write access to Google Calendar.

Google APIs may technically include fields beyond those belki needs in an API response. belki limits its intentional use, retention, and display to the information described in this policy.

6. Storage

  • OAuth credentials are stored locally in Obsidian’s private plugin data.
  • OAuth credentials are not written into belki task Markdown files.
  • Calendar events are cached temporarily in memory while the plugin is running.
  • Calendar events are not permanently copied into the vault or converted into belki tasks.
  • This website does not receive OAuth tokens or calendar event data.

7. Use of Google data

belki uses Google data only to:

  • list the calendars available to the connected account;
  • let you choose which calendars are visible;
  • display read-only events inside Today and Upcoming; and
  • open the corresponding event in Google Calendar when you click it.

belki does not use Google Calendar data for advertising, analytics, profiling, or training machine-learning models.

8. Sharing

belki does not sell Google user data. When you enable the integration, the plugin communicates directly with Google APIs to request the read-only information described above. Google is the API provider and handles those requests under its own policies.

The website does not act as an intermediary for the plugin’s Google API requests.

9. Retention and deletion

OAuth credentials remain stored locally until you disconnect Google Calendar in belki or remove the plugin’s local data. In-memory event data is temporary and is not retained as a permanent event archive.

Disconnecting Google Calendar clears the credentials stored by belki. You can also revoke belki’s access from your Google Account permissions page.

10. Security

The desktop authorization flow opens Google’s authorization page in your system browser and uses an authorization code with PKCE. No Google OAuth client secret is embedded as a security boundary in the distributed plugin.

belki is designed to limit access and local storage to what the integration needs. However, no software or storage method can be guaranteed to be completely secure. Keep Obsidian and your operating system up to date and protect access to your device and vault.

11. Google API Services disclosure

belki’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

12. Children’s privacy

belki is not specifically directed at children and does not knowingly operate an account-based data collection service for children. The core plugin does not require a belki account.

13. Changes to this policy

If belki’s data practices change, material updates will be published on this page and the “Last updated” date will be revised. Changes to the optional Google integration will be reflected here before new uses of Google user data are introduced.

14. Contact

For privacy questions, support requests, or concerns, open an issue in the public belki GitHub Issues tracker. Please do not include OAuth tokens, private calendar information, or other sensitive data in a public issue.