Data handling

Privacy

This notice covers Big Daddy Reporting’s private, single-owner Blogger connection and its information pages. Updated 31 October 2026.

Purpose and permission

The account owner connects their own Google account to prepare content inventory reports for five selected business blogs. The requested permission is View your Blogger account (blogger.readonly). The reporting tools expose fixed read operations; they do not publish, schedule, edit or delete Blogger content.

Information read and recorded

The fixed reader does not request post bodies, comments or author profiles. It does not collect Blogger pageviews or ClickBank earnings through this permission. Missing data is reported as missing, rather than treated as zero activity.

Where the information goes

A local connection helper sends authorized read requests to Google and obtains the requested metadata. Its credentials are stored locally using Windows CurrentUser encryption (DPAPI), for the Windows user who saved the connection. Credentials are handled by the helper and are not included in the reporting tools’ responses to the worker.

Read results and reports are used in Paperclip and can be retained in its execution records, local report files and local backups. Selected Google metadata and report content are sent to OpenAI through Codex to prepare the owner’s requested reports. The configured workflow uses the owner’s existing ChatGPT sign-in and Pro account, so model processing takes place outside the local Blogger helper.

The reporting application uses Google metadata for blog identification and content inventory reports. It has no function for selling that data, targeting advertising or training models. OpenAI’s processing of report requests is governed separately by its applicable service policies and account controls.

The owner’s optional ChatGPT setting “Allow chats to improve the model” was switched off and confirmed after reload on 30 October 2026 (UTC). That specific setting is not a promise of zero provider retention or a universal statement about every model service. Google and OpenAI can maintain service records under their respective policies and controls.

Website hosting and local sessions

The local setup page uses a session cookie and temporary sign-in state to bind the connection to the correct browser session. Google handles its own sign-in and consent screens.

Cloudflare Pages is the selected host for these static information pages. The deployment contains the app description and notices, not the local Google credentials or private business reports. The page files add no sign-up form, advertising, analytics beacon, remote fonts or third-party scripts.

When serving the published pages, Cloudflare processes technical request information, such as IP addresses, traffic-routing and system information, to operate and protect its services. Cloudflare may maintain traffic records and operational metrics under its own privacy policy. Its security features may set necessary operational cookies. A fixed retention period for all Cloudflare records is not promised by this notice.

Retention and removal

The owner manages local connection records, Paperclip records, exported reports and backups for their ongoing private reporting. These copies remain subject to the owner’s file, application and backup controls; the application does not impose one automatic deletion period across them.

The owner can revoke Big Daddy Reporting’s Google access through their Google Account. Revoking access stops further authorized reads once Google invalidates the connection; it does not automatically erase reports or copies already created. Removal of local credentials, Paperclip records, exported reports and backups is handled in their respective systems. Records held by Google, OpenAI or Cloudflare follow the applicable provider controls and retention practices.

Send questions or a removal request to the operator at patrickmagreevy@gmail.com. Do not send passwords, access tokens, refresh credentials or client secrets by email or chat.