Weekly Bellows private audio worker Privacy Policy

Effective date: October 5, 2026

About this policy

DysArtisan Innovations LLC operates the Weekly Bellows private audio worker. It converts operator-selected narration into audio using Google Cloud Text-to-Speech and saves the results in Google Drive. Access is limited to the operator and authorized collaborators; there is no public registration or upload service.

This policy covers the worker and its associated content workflow. General website browsing is covered by the separate dysartisan.com website privacy policy. Contact: [email protected].

Information processed and stored

The worker processes:

• Narration in its designated Google Sheets queue, including original news-recap scripts or other authorized content. This may contain personal information supplied by the operator.
• Job and chunk identifiers, status, character counts, content fingerprints, error codes, and output links.
• Generated MP3 audio, file identifiers, checksums, and recovery copies.
• Configuration and operational records, including resource identifiers, voice settings, usage reservations, character-limit settings, and timestamps.

Narration remains in the queue spreadsheet. A separate private state spreadsheet holds the processing ledger and recovery audio encoded as text. Script properties retain configuration and usage counters. Completed audio is stored in the designated Drive folder.

The worker has no Gmail permission and does not read inboxes. When separately authorized tools prepare narration from email or other sources, the worker submits only the narration placed in its queue for speech generation.

Google permissions

Google OAuth authorizes operations under the operator's account. The worker requests:

• Google Sheets access to read/update its queue and create/maintain its private state spreadsheet. This permission is broader than those spreadsheets; the code restricts operations to their configured identifiers.
• Drive per-file access (drive.file) to create and check its output folder and audio files, rather than whole-Drive access.
• Google Cloud access (cloud-platform) for Text-to-Speech. This is a broad permission subject to the account's Cloud permissions; the code limits its use to speech generation.
• External-request permission for the required Google HTTPS API calls.
• Apps Script trigger permission to enable or disable scheduled processing.

Google manages authorization. The worker uses an access token for API requests without saving it in its queue or job records. It does not request passwords or API keys.

Purposes and Limited Use

We use worker data to generate and deliver audio, display progress, enforce character limits, avoid duplicate processing, verify files, recover uploads, and diagnose problems.

Our use and transfer of Google API data complies with the Google API Services User Data Policy, including its Limited Use requirements. We do not sell this data or use it for advertising, credit decisions, or lending. We do not use Google Workspace API data to develop, improve, or train generalized, non-personalized AI or machine-learning models.

Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy

Who receives or can access information

Google provides Apps Script, Sheets, Drive, and Cloud Text-to-Speech. Each synthesis request sends queued narration and voice/audio settings to Text-to-Speech. Google services store the audio and records described above and may process account, billing, security, and operational information under their applicable terms.

The operator controls queue and audio access through Google sharing settings. Authorized queue editors can see narration and records; authorized audio viewers can access shared audio. The script and state spreadsheet are intended to remain private. Human review of another user's content requires specific permission, except where necessary for security or law.

When authorized, an OpenAI-powered assistant may prepare narration, update the queue, retrieve/assemble audio, and retain relevant content in its conversations, files, or working storage. Separately authorized steps may copy selected completed content or audio to Microsoft OneDrive or publish it through services and audiences chosen by the operator. Providers process those copies under their applicable terms and settings. Publication can make the selected content public. The worker itself calls only Google APIs and does not automatically publish content or change sharing permissions.

Provider privacy information: Google: https://policies.google.com/privacy Google Cloud: https://cloud.google.com/terms/cloud-privacy-notice OpenAI: https://openai.com/policies/privacy-policy/ OpenAI Google-data controls: https://help.openai.com/en/articles/10408842-google-app-data-controls-faq Microsoft: https://www.microsoft.com/en-us/privacy/privacystatement

Retention and deletion

The worker has no automatic deletion schedule. Queue text, audio, recovery copies, and records remain until the operator removes them. Ledger and usage counters support recovery, duplicate prevention, and character limits during continued operation.

Deleting an MP3 does not delete its recovery copy; deleting a queue row does not erase private records. Disabling processing or revoking access does not erase stored data. Version history, trash, backups, provider logs, assistant files, OneDrive copies, and published copies follow the relevant service's deletion processes.

Request access, correction, export, or deletion at [email protected], identifying the relevant content without sending credentials. Requests are subject to identity/authority verification and applicable legal requirements. Complete cleanup must address queue entries, output and recovery audio, associated records, and separately retained copies. Processing may need to pause during cleanup to preserve reliable usage controls.

Stopping access

The operator can run disableAutomation or remove the runQueue trigger in Apps Script, and revoke Google authorization at https://myaccount.google.com/connections. An already submitted synthesis request cannot be recalled. File permissions and separate assistant connections require separate management; revocation does not delete existing data.

Security

The worker uses HTTPS and Google account/file-access controls. Its code restricts outgoing endpoints, refuses redirects, and records sanitized error codes rather than raw API responses. Providers may retain operational logs. These safeguards cannot guarantee absolute security. The operator should keep script/state access private and limit queue/audio access to intended recipients.

Changes

Updates appear here with a revised date. Before materially different Google-data access or use, we will provide updated disclosures and obtain required consent.

DysArtisan Innovations LLC Privacy contact: [email protected]