John Assist - Privacy Policy

Last updated: 18 November 2026

Who this applies to

John Assist is a private AI assistant for one person (John) and the small church work he does. It is operated by Mike Pinch (the "operator"), contact Mike@dandlpress.com. It is not open to the public. The operator creates and manages everything it runs on: the computer, the assistant's Google account cosbyassistant@gmail.com, the AI service account and its key, and the web access. John uses the assistant; he does not hold those accounts or credentials.

This policy describes how the assistant handles information, including information it receives from Google. See the home page for what the assistant does.

What Google data the assistant can reach, and what limits we add

The assistant asks Google for a small set of permissions. The table shows two different things for each: what Google allows the permission to reach (the real extent of the access), and the extra limits that our own software applies. Our limits are not enforced by Google; they are rules built into the assistant's tools.

PermissionWhat Google lets it reachLimits our tools add
Calendar - view events (events.readonly)View events on every calendar the assistant's Google account can access: its own, and any calendar John chooses to share with it.The tools read only the calendars on a list the operator sets (the assistant's own, and John's if he shares it).
Calendar - manage events on calendars it owns (events.owned)See, create, change and delete events only on calendars owned by the assistant's account. It cannot change John's own calendar, even if John shares it.Writes only go to the allowed calendar. Sending invitations and deleting events each need John's clear approval first.
Calendar - free/busySee when calendars the account can access are busy, without event details.Only the allowed calendars are checked.
Drive - files the app creates (drive.file)Only the files the assistant itself creates or opens, including the Google Docs and Sheets it makes and can edit.It creates, organises and trashes files only inside a folder named "John Assist". Trashing needs John's approval and is recoverable in Drive's trash for 30 days.
Drive - read-only (drive.readonly)See and download every file the assistant's Google account can access: everything in its own Drive and everything shared with it, including shared drives it belongs to. Google treats this as a "restricted" permission.The tools search and read Google Docs, Sheets and plain-text files when John asks, and never read PDFs, images or other file types. They cannot change, share or delete anything outside "John Assist"; to edit a shared document the assistant makes a copy inside "John Assist" and edits the copy.

The assistant's Google account holds only what John shares with it and what the assistant creates, which keeps the real reach of the read-only permission small in practice. That is a practice, not a technical limit.

Not requested: permission to edit other people's Docs or Sheets, full Drive access, Gmail through Google's APIs, Contacts, or any permission to share files or manage who can see them. The assistant has no tool that shares files or sends email through Google.

The data accessed can include event titles, times, locations, descriptions and attendee names, and the names and text of files that John shares with the account.

Email

John can also write to the assistant by email at cosbyassistant@gmail.com. This mailbox is read over ordinary Gmail mail protocols (IMAP and SMTP) using an app password issued by Google for that mailbox, not through the Google APIs above. Only messages from addresses the operator has approved are processed; everything else is ignored. Replies go only to the person who wrote. The assistant does not send email on its own initiative. Email content is handled like conversation content in the sections below.

How the data is used

Accounts and credentials

The operator manages all accounts and enters all credentials. John does not hold them. Each credential is used with its own provider only:

CredentialIssued by and managed byUsed with
Google sign-in approval for the assistant (a refresh token) and the app's client secretGoogle; created by the operator when he signs the assistant's account inGoogle's APIs (Calendar and Drive), by the assistant's Google tools
Gmail app passwordGoogle, for the mailbox cosbyassistant@gmail.com; entered by the operatorGmail's mail servers only, by the email connector
Anthropic API keyAnthropic, from an account the operator manages and pays for (a workspace set up for John Assist); entered by the operatorAnthropic's API only, to get the AI's answers
Cloudflare tunnel token and Cloudflare Access sign-inCloudflare; managed by the operator. Access lets only approved people sign in with their Google account.Cloudflare only

What keeps credentials out of the AI's prompts, out of what John sees, and away from unrelated services:

Who receives what

Service and its roleWhat it receives
Anthropic - the AI that writes the assistant's answers (via the API account the operator manages)What John types or emails; text of files and attachments the assistant reads for a request; photos John attaches (a reduced copy); results the assistant gets back from Google for a request (for example event details, availability, or document text); and the assistant's standing instructions.
Google - the assistant's Calendar, Drive, Docs, Sheets and mailboxThe requests the assistant makes and the content it creates there.
Cloudflare - reaches the chat page securely and limits it to approved peopleThe chat page traffic (messages and replies) passes through Cloudflare's network, and Cloudflare Access sees the Google account used to sign in.
Web search and page-reading services - public informationSearch words the assistant writes, addresses of pages it opens, and the computer's network address. The assistant is instructed to use general words only and never to put private Google or email content into a search; this is an instruction to the AI, not a technical block.
Bible text services - exact Scripture quotationsThe passage reference and translation requested, and the computer's network address.
The operator's maintenance tool and its providers - see "Maintenance" belowFile names, sizes, checksums, technical logs and status information, which can include conversation titles and short log snippets.

Anthropic receives conversation and Google content in order to answer John; the other services receive only the limited items shown. Nothing is sent to advertisers or data brokers. Under Anthropic's commercial terms, inputs and outputs are not used to train its models by default (see Anthropic's explanation), and Anthropic keeps data for a limited period under its own policies (see its retention page). The operator cannot delete data held by Anthropic, Cloudflare or other providers directly; their own policies apply.

Where data is stored

The assistant runs on a computer managed by the operator in Arizona, USA. On that computer:

Data is protected in transit by HTTPS and at rest by access restrictions on the computer. No system is perfectly secure.

Who can see it, and when

Maintenance

The operator maintains the assistant with an AI-assisted administration tool that runs on his own computer account. This tool is itself an AI service. It uses Anthropic's AI through the operator's own Anthropic sign-in (not the API key the assistant uses, and possibly under different privacy settings and terms), may use other AI providers for software-coding tasks (it has not been given John's content for these), keeps its own history and notes on the operator's computer (which the operator's general encrypted backup includes), and posts its reports to a private Discord server the operator owns. Whatever it reads is therefore processed by those services under their own terms.

Routine work (updates, backups, restarts, health checks, cleanup) is done using file names, sizes, counts, checksums, status information and technical logs. The tool is instructed not to open the content of John's conversations, documents or Google data, and it labels test content as a test. So far it has seen only: those technical items; conversation titles (which are the first words of a conversation); short log snippets; and the clearly labelled test items it created. If a title or log snippet happens to contain Google information, that snippet may be seen. Troubleshooting that needs the content of John's conversations, documents or Google data is done only after John agrees to the specific items; it is not covered by any general maintenance exception.

Your control, deletion and backup copies

Children

John Assist is not directed to children and is not open to the public.

Changes and contact

If this policy changes, the new version will be posted on this page with a new date, and John will be told of material changes and asked to confirm again before Google data is used in a new way. Contact: Mike Pinch, Mike@dandlpress.com.

John Assist's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.