Privacy Policy — ResidentAI Chief of Staff

Effective date: July 2026

Overview

ResidentAI Chief of Staff ("the Application") is a personal software tool operated by a single individual for their own private use. It is not a commercial product, is not offered to the public, and has exactly one user: its operator and developer. The Application runs entirely on infrastructure the operator owns and controls.

This policy describes what Google user data the Application accesses, why, and how it is handled.

What the Application does

The Application allows its operator to interact with a personal AI assistant that can, on the operator's own behalf and at the operator's direction:

Read the operator's Gmail messages.
Create draft email messages in the operator's Gmail account.
Send a draft email message, but only a specific draft the operator has personally reviewed and explicitly approved in that exact form. The Application never sends email autonomously or without the operator's direct, explicit approval of that exact message.
Read events on the operator's Google Calendar.
Create new events on the operator's Google Calendar, at the operator's direction.

The Application does not modify or delete existing calendar events, does not delete email messages, and does not perform any action beyond what is listed above.

Google user data we access

Data	Scope requested	Purpose
Gmail messages (read)	`gmail.readonly`	Let the operator ask their assistant questions about their own email and have it summarize or reference message content.
Gmail drafts (create, and send only an operator-approved draft)	`gmail.compose`	Let the operator ask their assistant to prepare an email for their review, and, once approved, send that exact message on their behalf.
Calendar events (read)	`calendar.readonly`	Let the operator ask their assistant about their own schedule.
Calendar events (create)	`calendar.events`	Let the operator ask their assistant to add an event to their own calendar.

No other Google data or scopes are requested.

How we use this data

Google user data accessed by the Application is used exclusively to fulfill the operator's own direct, in-the-moment requests to their personal assistant (e.g., "what's on my calendar tomorrow," "draft a reply to this email," "add this to my calendar"). Data is not used for advertising, analytics, profiling, or any purpose other than directly answering the operator's own request.

Where this data is processed and stored

All processing happens on private server infrastructure owned and administered solely by the operator. No Google user data is transmitted to or processed by any third-party service, cloud provider, or external company beyond Google's own APIs.
OAuth credentials (tokens used to access the operator's Gmail and Calendar) are stored locally on that private infrastructure with restricted file permissions limiting access to the operator's own system account. They are never committed to source control, logged in plaintext, or transmitted anywhere outside the operator's own infrastructure.
The Application does not maintain a separate, durable copy of Gmail or Calendar content. Any data read from these APIs is used transiently to answer the operator's immediate request and is not retained as a permanent archive.

Security safeguards

OAuth credentials are stored with restricted file permissions (accessible only to the operator's own system account), on infrastructure the operator alone administers.
Credentials are never committed to source control, logged in plaintext, or transmitted outside the operator's own infrastructure.
All Google API access uses OAuth 2.0; no Google account password is ever collected, stored, or handled by the Application.
Access is limited to the specific scopes listed above — the Application does not request or use broader account access.

Data sharing

We do not sell, rent, trade, or otherwise share Google user data with any third party for any purpose, including advertising. Google user data is never used to train any generalized or third-party machine learning model; any AI processing occurs on a locally-hosted language model running entirely within the operator's own private infrastructure.

Data retention and deletion

Because the Application does not retain a durable archive of Gmail or Calendar content, there is no separate stored copy to delete beyond revoking API access.

Revoking access

The operator may revoke the Application's access to their Google Account at any time via Google Account permissions, which immediately invalidates all stored credentials and prevents any further API access.

Compliance with Google API Services User Data Policy

ResidentAI Chief of Staff's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data obtained through this Application is used only to provide or improve the user-facing features described on this page, is not used for serving advertisements, and human access to this data is limited to circumstances the operator themselves initiates (they are, and will always be, both the sole operator and sole user of this Application).

Changes to this policy

If this policy changes, the updated version will be published at this same URL with a revised effective date.

Contact

Questions about this policy or the Application's data practices can be directed to: deboerja@gmail.com