Privacy, explained.

Who operates Charlie

Charlie is the assistant presented under the MyPersonalCOS project name. Charlie is operated by Eran Ben Shmuel, as an individual, in Israel. Support, privacy and deletion contact: seranb1@gmail.com.

Information used

When Google is connected, enabled features can use:

• Email: senders, recipients, subjects, dates, snippets, message text and selected attachments; draft and sent-message information.
• Calendar: event titles, descriptions, times, locations, attendee details and event changes.
• Contacts: names, email addresses and telephone numbers returned by contact searches.
• Documents: titles and text supplied for Google Doc creation, plus limited service-availability metadata.

Charlie also processes conversation text, enabled voice input, instructions, memory notes and technical records needed to operate the assistant.

Charlie asks for Gmail modification, Calendar, app-associated Drive files, Documents and read-only Contacts. It does not ask for spreadsheet access and has no general Drive browser.

Why information is used

Information supports answers, email assistance, calendar management, document creation, requested memory and configured reminders. When enabled, scheduled routines may check new email or calendar changes and prepare briefings without a new message from the user each time. Technical records support delivery recovery, debugging and quality measurement.

AI and other service providers

Relevant Google information, including email text and tool results, can be sent to the configured Claude/Anthropic service as part of the conversation context. Creating a personal Google OAuth application does not prevent this AI processing.

When voice is enabled, input audio can be processed by Deepgram or ElevenLabs. Spoken response text can be processed by Cartesia or ElevenLabs. LiveKit carries live-call media. Enabled messaging services, such as Dailight/SGI or Telegram, carry messages and attachments sent through them. Google processes requests made to its connected services.

The providers actually used depend on configuration. Their processing locations, retention and model-training terms require review of the applicable accounts and agreements; this policy makes no blanket claim that providers retain nothing or never use data for training.

Storage and protection

Charlie stores Google authorization tokens, conversation records, memory notes, downloaded attachments and operational records on its host. Local search and relationship databases can contain copies or summaries of information. Enabled SDK conversation persistence can create additional local history.

Authorization tokens use restrictive file permissions and atomic writes. The application does not itself encrypt that token file at rest. Hosting access controls, disk encryption and backup arrangements require confirmation by the operator. These measures are not a guarantee against unauthorized access.

Retention and deletion limits

There is no single automatic deletion period for all Charlie data. The dedicated quality-metric tables have a thirty-day retention rule; that rule does not apply to all transcripts, memory, attachments or operational logs. Some delivery payloads are pruned after completion and recovery windows, while identifiers needed to prevent repeated actions can remain.

Local forgetting tools have limits. They do not comprehensively erase Google originals, every database copy, binary attachments, SDK or provider history, or backups. A forgotten phrase may remain in a restriction list intended to prevent remembering it again.

No-log handling suppresses specified Charlie records. It cannot undo data already processed by a provider or guarantee erasure of history written before a no-log decision. Do not interpret it as universal private processing.

Controlling access and requesting removal

You can revoke Charlie's Google authorization through your Google account's connected-app controls. Revocation stops future access under that grant; it does not automatically remove information already stored by Charlie or other services. Removing Charlie's local authorization, stored information and backups is a separate operator task.

Send support, privacy or deletion requests to seranb1@gmail.com. This is the contact supplied in the Google Branding configuration. Mailbox monitoring and the process for handling deletion requests must be confirmed before these pages are published.

This informational website

These pages contain no scripts, forms, analytics or externally loaded assets. The pages are served by GitHub Pages, which may keep access logs; GitHub's logging practices must be confirmed before the site is published.