PRIVATE ASSISTANT / DATA PRACTICES

Privacy policy

Skippy is a privately operated personal assistant. It connects only to Google accounts whose owners authorize access. This website describes that integration; it does not offer public account registration or collect Google credentials.

Google data and permissions

The current integration requests Gmail read, send, and modify permissions, and Google Calendar access. These permissions can allow reading messages and email metadata, sending email, modifying mailbox state, and reading or changing calendars and events. Requested actions remain subject to the operator’s instructions and approval requirements.

Google data is used to provide requested assistance, including email and schedule summaries, meeting preparation, and personal briefings. Automated briefings may access connected accounts on the operator’s configured schedule.

AI processing and delivery

When assistance uses email or calendar information, relevant content may be sent to the AI model provider configured for the assistant. Provider selection can change; the operator must review that provider’s data-handling and retention terms. Information included in a briefing may also be delivered through messaging or other services configured by the operator. Those services process delivered content under their own terms.

Storage and retention

OAuth credentials are stored in the private assistant environment, separately for each connected account, rather than on this public website. Assistant conversation history, logs, and configured briefing destinations may retain content that has been processed. Retention depends on the operator’s configuration and the services used; there is no promised automatic deletion period.

The hosting provider may process technical request information needed to serve and secure this website. The website itself does not include an advertising tracker, account database, or Google sign-in form.

Use restrictions

Google user data is used for the private assistant’s user-requested features, not for sale or advertising. Google API data must not be used to develop, improve, or train generalized AI or machine-learning models. The operator must configure integrations and providers consistently with this restriction.

The use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Control, revocation, and deletion

You can revoke the integration’s access through your Google account’s third-party connections settings. Revoking access prevents further authorized API access; it does not automatically remove previously saved content. The operator can remove locally stored credentials and retained assistant data, and must separately manage copies in configured delivery destinations.

Operator contact

Connected account owners should contact the operator through their existing private contact channel for access or deletion requests. A monitored support contact must be finalized before OAuth publishing.