Privacy policy

Effective 10 October 2026

Barclay Personal ("Barclay") is a private personal assistant operated by Luke Adams for his own use. This policy explains what information Barclay accesses, how it is used and shared, where it is stored, and how access can be revoked and data removed.

Google access is not enabled. It starts only after the owner authorizes the requested Google permissions and the Google connector is turned on, and it will not be turned on until the Google privacy controls described in this policy are in place. The Google sections below describe how Barclay will handle Google information once access is enabled.

Google permissions requested

• openid and email: to confirm which Google account is signed in.
• calendar.events.owned: to read, create and delete events on calendars the account owns.
• contacts.readonly: to search contacts, read-only.

Barclay's own checks restrict use to the owner's personal Google account and a single configured private calendar. Google's broader consent does not authorize Barclay to use other calendars.

Google information accessed

• Identity: the connected account's verified email address, used to confirm it is the intended personal account.
• Calendar: relevant event identifiers, titles, dates and times, calendar identifiers and names, and any locations and descriptions. Google's permission covers events on owned calendars; Barclay's personal workflow is limited to the configured calendar. To review a deletion, Barclay briefly retrieves the full event to verify it, then keeps only its title, start and end time and all-day flag for the confirmation display. Barclay can create ordinary events, and can delete a selected eligible event only after a separate explicit confirmation. It does not create invitations or change recurring events.
• Contacts: matching contact identifiers, names, email addresses and phone numbers. Contact access is read-only; Barclay does not create, change, delete or migrate contacts.

How information is used and shared

Barclay is not sold or used for advertising. Google information is used only to carry out the owner's requests; it is not sold or used for advertising. This policy authorizes no use of Google information to train generalized AI models.

• AI processing of Google information: relevant Google results and the conversation context around them will be sent only to the commercial Anthropic API. Anthropic's Commercial Terms prohibit training models on customer content. This is not a promise that Anthropic retains nothing. Optional provider feedback or data-sharing programs will not be used for Google information.
• Other model routes: Google information will be blocked from Barclay's Gemini and OpenAI model routes, including automatic fallback during a provider outage, and from external web search. This applies to earlier conversation context as well, and continues after Google access is later disabled or conversations are deleted. If the approved provider is unavailable, Barclay will say so rather than switch providers.
• Voice: Barclay's ordinary voice service uses ElevenLabs to transcribe recordings and speak answers (ElevenLabs Privacy Policy). Its account training opt-out has not been verified. While Google access is enabled, external transcription, spoken replies and realtime voice will be paused and typed requests remain available. External voice will not process Google information unless verified data controls are in place and this policy has been updated first.
• Ordinary requests: requests that involve no Google information are processed by Barclay's configured AI provider, currently the Anthropic API with Google's Gemini API as a fallback.

Storage and retention

Google authorization tokens and account and permission details are stored in private backend files with restricted file-system permissions. Conversations are stored on the owner-controlled backend. Structured Google tool logs and action records will contain outcome information rather than contact details, event notes or full event records.

A deletion proposal holds only the event title and time needed for review during its ten-minute confirmation window. That display data is cleared when the confirmation is used, when its conversation is deleted, or after expiry by Barclay's startup or periodic maintenance. Downtime, database contention or delayed maintenance can postpone that cleanup.

Minimal action identifiers, fingerprints and outcome states are kept to prevent duplicate calendar actions and to stop uncertain results from being retried silently. These records can remain after a conversation is deleted and currently have no fixed automatic expiry. Deleting a conversation does not reset a past confirmation or allow an action to run again. Conversation text can also contain calendar or contact details; the expiry of a proposal does not erase conversation text, older records, backups or copies held by providers. Older records are not purged automatically.

Routine backups keep a rolling set of recent local snapshots, and incident or manually preserved recovery copies can remain until removed separately. Deleting current data does not immediately remove it from every backup. Copies held by providers are governed by their terms and controls.

Your choices and deletion requests

Google access can be revoked at any time from the Google Account's third-party access settings (myaccount.google.com/connections). Revoking access stops further access but does not erase information already stored in conversations, action records, backups or provider systems. To request review and removal of locally stored information and recovery copies, contact the operator below. Complete erasure is not currently a one-step feature of the application.

This website

These pages are static. They contain no forms, scripts, analytics or Google sign-in. The hosting provider may process ordinary web request information, such as IP addresses, in its access logs. No calendar or contact data is published on this site.

Contact and changes

Operator: Luke Adams. Privacy and support contact: luketadams@gmail.com.

This policy will be updated before Barclay's data practices change, and the effective date above will change with it.