Privacy Policy

1. Overview

LifeBot is a private, personal-use productivity application operated by Yoshi Suzuki. It combines calendar commitments, tasks, focus sessions, and check-ins to create daily plans and personal productivity reviews. It is not offered for public registration.

This policy explains how LifeBot accesses, uses, stores, and shares information received from Google APIs.

2. Google data LifeBot accesses

LifeBot requests the Google Calendar read-only permission. Within a selected calendar and synchronization date range, it may access:

• calendar and event identifiers;
• event title;
• start and end date or time;
• all-day status;
• event status, including cancellation status;
• event location;
• Google Calendar event link; and
• event label identifiers, names, and colors.

LifeBot also stores OAuth credentials required to maintain authorized access. LifeBot does not request Calendar write permission through this integration and cannot create, edit, or delete calendar events using it.

3. How Google data is used

Google Calendar data is used only to provide and improve the user-facing features requested by the user, including:

• importing selected calendar events as LifeBot tasks;
• rendering calendar commitments in private Obsidian daily notes;
• detecting schedule changes, cancellations, and selected productivity labels;
• building daily plans around fixed commitments; and
• generating personal planning, coaching, and review responses.

Calendar-derived context may be processed by the configured AI service provider when necessary to generate a requested personal planning or coaching response. It is not used for advertising, sold, or used to develop, improve, or train generalized AI or machine-learning models.

4. Storage and retention

Imported data is stored in the operator’s private LifeBot event records and Obsidian vault on operator-controlled devices and server infrastructure. OAuth credentials are stored in a restricted private configuration file. Data may also exist in operator-controlled backups.

Calendar-derived records are retained while they are needed for personal planning, history, and analytics, or until the user deletes them. OAuth access is retained until authorization is revoked or the credentials are deleted.

5. Sharing and disclosure

LifeBot does not sell Google user data and does not share it for advertising. Data is disclosed only as necessary to operate the requested functionality:

• to infrastructure providers that host the private application or its data;
• to the configured AI service provider when calendar-derived context is needed for a requested LifeBot response; or
• when required by applicable law or necessary to protect security and legal rights.

Any service provider access is limited to providing the application’s user-facing features and is subject to applicable confidentiality and data-protection obligations.

6. Google API Limited Use

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

7. Security

LifeBot uses reasonable technical measures intended to protect stored data, including restricted credential-file permissions, encrypted HTTPS transport for public web pages and API communications, and access controls on private infrastructure. No system can guarantee absolute security.

8. User controls and deletion

The user can revoke LifeBot’s Google access at any time from Google Account third-party connections. To request deletion of locally stored LifeBot data or OAuth credentials, contact yoshitaka.s.work@gmail.com.

9. Changes

This policy may be updated when LifeBot’s functionality or data practices change. The effective date at the top of this page will be revised when an update is published.

10. Contact

Questions about this policy may be sent to:
yoshitaka.s.work@gmail.com