Privacy Policy for Hekate

Effective 24 October 2026 · Personal, single-user Google integration

Hekate is Kirill's personal AI assistant. This Google integration is operated for his own use; it is not offered as an app for other users. This policy explains how it handles data authorized through his Google account.

What it accesses and why

When Kirill authorizes the integration, Hekate may access Gmail messages and send mail on his instruction; read and manage calendar events on his instruction; read contacts and Drive files; and use Docs and Sheets for tasks he requests. The inbox briefing reads recent mail and calendar events to prepare a personal digest. Access depends on the Google permissions granted and the specific task. Hekate does not use this Google data for advertising or sell it.

Where the data goes

OAuth credentials and automation state are stored in Kirill's own local Hermes environment. Google data needed for a task is processed in that local environment and by his own DGX Spark AI system; it is not sent to third-party AI model providers. The integration necessarily communicates with Google APIs to access or change authorized Google data. A digest or requested result may be delivered to Kirill through the messaging channel he uses, including Telegram; that delivery service processes the message. Google data is not intentionally published on this website.

Storage and retention

Tokens, local task state, digests, and other outputs may remain on Kirill's own devices until he deletes them or revokes access. The original mail, calendar events, and files remain in his Google account subject to Google's own settings. No fixed retention period is promised. Kirill controls this single-user setup and can delete local copies or revoke the application's Google access through his Google account security settings.

Website visitors

This policy is hosted on unosanity.uno by Neocities. Visiting this page sends ordinary web requests to the hosting provider. The website may also load third-party content on other pages; this policy does not claim to control those services. This policy page itself does not request Google sign-in.

Changes and contact

This policy may change if the integration's actual data practices change. The effective date above will be updated. Questions: sanity@unosanity.uno.