Privacy Policy

1. About Khepri

Khepri is a privately operated, local-first artificial intelligence assistant developed for personal use. It supports natural voice interaction, scheduling assistance, and explicitly authorized software integrations.

Khepri is operated on privately controlled computing hardware and is not offered as a public AI service. This policy describes its current Google Calendar integration and the related informational website.

2. Google Calendar Data Accessed

With the Google account holder's authorization, Khepri accesses the Google Calendar API using read-only permissions.

Depending on the calendars and events accessible to the authorized account, retrieved information may include:

• Calendar names and identifiers.
• Event titles, start dates, and end dates.
• Event locations.
• Whether events are all-day events.
• Event types and confirmation status.
• Availability information, including busy or free status.

Khepri's current Google Calendar authorization requests permission to read calendar listings and event information. It does not request permission to create, modify, or delete Google Calendar events through this integration.

3. How Calendar Information Is Used

Khepri retrieves authorized calendar information to support user-requested functions such as reviewing appointments, answering scheduling questions, and evaluating calendar availability.

Calendar information may be incorporated into responses generated by Khepri's local assistant software for these purposes.

Google Calendar information is not obtained for advertising, resale, or training a commercial artificial intelligence model.

4. Authorization and Credential Storage

Google Calendar access is authorized through Google's OAuth authorization process.

Khepri stores Google OAuth authorization tokens in a local JSON file to maintain previously authorized calendar access and renew access when permitted by Google.

The token folder has Windows permissions restricting access to the operator's account, system administrators, and the operating system. The token file is not independently encrypted. Related application configuration is stored separately and is subject to its own Windows file permissions.

Khepri does not require the user to provide their Google account password directly to the assistant.

5. Data Storage and Retention

Retrieved calendar information is processed by Khepri's local application components to fulfill calendar-related requests.

Khepri's spoken responses, including calendar information contained in those responses, are written to audio files in the local Windows temporary folder. Khepri does not currently delete these files automatically after playback.

Depending on how Khepri is launched, transcripts and spoken replies may also be recorded in local voice logs. Calendar-related request text may appear in local audit logs. Certain locally stored records and logs may also be included in system backups.

No fixed automatic deletion interval is currently promised for locally retained records. Such records may remain until they are removed through local data management and maintenance procedures.

Revoking Google authorization does not automatically erase information previously recorded in local files or backups.

6. Data Sharing

The Google Calendar integration communicates with Google's services to authenticate access and retrieve authorized calendar information.

In its currently audited configuration, Khepri processes retrieved Google Calendar information using a locally hosted AI model. Calendar information is not transmitted to external AI processing services, advertisers, or commercial data brokers.

Google processes the authentication and API communications necessary to provide the authorized Calendar service.

Any future feature involving additional external processing or sharing of Google Calendar information will require a review of the applicable disclosures and permissions before being enabled.

Khepri's use of information received from Google APIs is governed by the Google API Services User Data Policy , including its Limited Use requirements.

7. Security

Khepri uses speaker verification and Windows Hello authorization to control access to protected personal-calendar functions. Its current Google Calendar integration requests read-only API permissions.

Google OAuth tokens are stored in a locally restricted directory. Other application files, including certain configuration files and diagnostic logs, may have broader access permissions for local Windows users. Overall protection depends on the security of the operating system, user accounts, and backup environment.

No computer system can guarantee absolute protection against unauthorized access or data loss.

8. Revoking Access and Managing Data

The Google account holder can review or revoke Khepri's Google account authorization through Google's account connection settings.

Visit Google Account Connections to review applications and services with access to the account.

Revoking access prevents further authorized Calendar API requests using that grant. Any previously retained local records or backups must be managed separately.

9. Informational Website

The website at mykhepri.net provides information about Khepri and its privacy practices. It does not provide public access to the locally operated assistant.

The website does not request Google credentials or retrieve Google Calendar events from visitors.

The website's hosting provider may process ordinary technical information associated with visits, such as network requests and server logs, under its own applicable policies.

10. Changes to This Policy

This policy may be updated when Khepri's functionality, authorization permissions, or data-handling practices change.

Changes involving new uses of Google user data will be reviewed for applicable notification and consent requirements before those uses are introduced.

11. Contact

Questions about this privacy policy or Khepri's Google Calendar integration may be directed to:

MyKhepri1@gmail.com