Privacy policy

1. Google data and permissions

The currently supported and authorized Google services are Google Calendar and Google Drive. The application uses full Calendar and Drive scopes rather than read-only scopes, within the access granted by the Google account.

• Calendar: calendar names and settings; event titles, descriptions, times, locations, attendees, and related event information. Granted permissions can allow viewing, creating, editing, sharing, and deleting calendars or events.
• Drive: file and folder names, identifiers, types, ownership and sharing information, other metadata, and file contents when needed for a request. Granted permissions can allow viewing, creating, editing, organizing, sharing, and deleting files.
• Authorization: OAuth access and refresh tokens that allow the assistant to make authorized Google API requests.

These permissions describe technical capability, not permission to make unrequested changes. Changes to Google data require explicit user approval through the private assistant. The application does not currently integrate other Google services.

2. Why the assistant uses this data

The assistant uses Google data to fulfill personal requests: list or search calendars, events, and files; retrieve relevant information; answer questions; and carry out explicitly approved changes. It does not publish Google data on this website.

The application does not sell Google user data, use it for advertising or ad targeting, or use it to train generalized AI or machine-learning models.

3. Private environment and AI processing

Google data and OAuth tokens are processed and stored in the operator’s private assistant environment. The operator administers that environment and can access its stored data, conversations, and logs. OAuth tokens are used to authorize Google API calls; they are not part of this public website.

Selected relevant Google data, request text, and conversation context may be sent to the configured AI provider to interpret requests and produce answers or proposed actions. For example, this may include relevant event details or excerpts from a requested file. The provider processes that information under its own applicable terms and the account’s settings.

This policy does not promise provider zero retention or a provider-wide no-training guarantee. The app’s commitment not to use Google data to train generalized models is separate from provider terms; the operator must use a provider configuration consistent with Google’s applicable data-use requirements.

4. Retention and deletion

Retrieved information can remain in conversation history, working files, or operational logs in the private assistant environment. Conversations and logs may retain Google data until deleted under local and provider settings. OAuth tokens remain stored for continued authorized access until removed or invalidated. There is no single fixed retention period promised by this policy.

To request deletion of locally stored tokens, retrieved data, or conversation records, contact alfred-4640@agentmail.to and identify the records concerned without sending passwords or tokens. The operator can address records under its control and use provider deletion controls where available; provider-held copies remain subject to that provider’s applicable settings and terms.

Deleting assistant records does not itself delete the original calendars, events, or files in Google. Changes to those originals require a separate, explicitly approved request.

5. Revoke Google access

You can revoke access through your Google Account’s third-party connections. Select Alfred Personnel, review its access, and remove that access. Google may require you to sign in.

Revocation stops future authorized Google API access through that grant. It does not automatically delete previously retrieved data, earlier conversation records, logs, or provider-held records. Contact the operator separately to request deletion.

6. This public website

This is a static informational site with no login, form, application database, analytics, tracking scripts, or external fonts. The site’s own files do not set cookies. Clicking an email link opens your email application; sending an email shares its contents with the operator and the email services used to deliver it.

Cloudflare hosts the public site and may process network metadata, such as IP addresses, request details, and security-related information, to serve and protect it. Hosting or security features may involve cookies or other processing under Cloudflare’s applicable policies. This is not a promise that the hosting layer never uses cookies.

7. Google API Limited Use

Alfred Personnel’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used to provide the requested assistant features, not advertising, resale, or training generalized models. This statement is not a claim of Google verification, certification, or endorsement.

8. Changes and contact

This page will be updated when the integration’s data practices change. Before accessing additional Google services or using data for a newly disclosed purpose, the operator must explain the change and obtain any required authorization.

Privacy and deletion contact: alfred-4640@agentmail.to. See also the private-use terms.