1. Scope

This policy explains how Sage accesses, uses, stores, and protects information when its owner connects Google accounts. Sage is a private, single-user personal operations assistant operated by Hrudai Nirmal.

2. Google data Sage accesses

Depending on the permissions granted and the feature being used, Sage may access:

• Gmail: message content and metadata, senders, recipients, subjects, labels, threads, and drafts.
• Google Calendar: event titles, descriptions, attendees, times, locations, status, and related metadata.
• Google Drive: file and folder metadata and, only when needed for an explicit request, file content.

3. How Google data is used

Sage uses Google data only to provide user-facing assistant functions: searching and summarizing information, monitoring for requested events, preparing contextual notifications and reminders, drafting email, managing calendar events, finding Drive files, and carrying out actions the user explicitly requests.

Consequential operations use deterministic controls. Sending email and deleting Google data require explicit user approval. Sage does not silently grant itself additional permissions.

4. Storage and processing

Sage’s operational database, indexes, context, and AI processing run locally on the owner’s Mac. Google OAuth credentials are stored encrypted within the owner’s local n8n installation. The public website at this domain is static and does not receive Google account data.

Google information may remain in local indexes or operational records until it is removed by the owner or the related retention process. Temporary files are cleaned after use where the feature does not require durable storage.

5. Sharing and commercial use

Sage does not sell Google user data, does not use it for advertising, does not use it to create advertising profiles, and does not share it with data brokers. Google data is not transferred to third parties except when the user explicitly directs an action that requires such a transfer or when required by law.

7. Security

Sage restricts its application services to the owner’s computer, separates model decisions from approval enforcement, stores secrets outside source control, and records sensitive operations in local audit logs. No system can guarantee absolute security, but access is intentionally minimized and bounded.

8. User control and deletion

The owner may stop Sage’s services, disconnect an account in the local credential manager, delete locally stored records, or revoke Google access through the Google Account security settings. Revocation prevents future API access but does not automatically remove local records already created; those can be deleted separately.

9. Policy changes

This policy may be updated when Sage’s data practices change. The effective date at the top of this page will identify the current version.

10. Contact

Questions or requests about this policy can be sent to hrudainirmalwork@gmail.com.