Privacy policy

What we collect

Beta signup: name, email, and the answers you give on the form. Training: the workouts, sets, and challenge progress you log. That's it — no location tracking, no contact scraping, no ad pixels.

How we use it

To run your training programs, run monthly challenges, and email you about the beta and program updates. You can unsubscribe from email with one click, any time.

What we never do

We never sell your data. We never share it with advertisers. We never post to your social accounts. (DADZILLA publishes to its own YouTube channel through an automation described in section 4 — that concerns DADZILLA's channel, never yours.) Your workout logs are yours — full stop.

DADZILLA's own YouTube channel (Google API Services)

DADZILLA uses YouTube API Services, provided by Google, to publish videos to DADZILLA's own YouTube channel through an owner-controlled automation registered with Google as "DADZILLA Video Publisher". This section explains that use. The only Google account involved is the one that owns the DADZILLA channel; nothing here changes what the rest of this policy says about your data. A plain description of the tool is published at dadzillafit.co/youtube-automation.

Visitors and members. You are never asked to connect a Google or YouTube account to DADZILLA. The automation operates only on DADZILLA's owner-authorized YouTube channel and does not post on behalf of website visitors or members.

What the automation may do. With the channel owner's authorization it can upload DADZILLA-owned videos, install DADZILLA-owned thumbnails, set a video's title, description, tags and settings, schedule an eligible video for release, read back a video's processing and publication status, and check the channel's own uploads to avoid duplicates. Whether a video can be released publicly through this automation depends on YouTube's rules for API uploads; this policy does not promise public release.

Google permissions it requests. The automation signs in with the channel owner's Google account and requests two YouTube permissions: https://www.googleapis.com/auth/youtube.upload (upload DADZILLA's videos and thumbnails) and https://www.googleapis.com/auth/youtube.readonly (read DADZILLA's own channel and video details).

Google user data it accesses and keeps. The data involved is the channel owner's authorized YouTube data: the DADZILLA channel's ID, name and uploads-playlist ID, and for DADZILLA's own videos their video IDs, titles, descriptions and settings, privacy and processing status, scheduled release time, thumbnail result and public link. DADZILLA keeps two kinds of records: (1) in DADZILLA's private production records (a spreadsheet in DADZILLA's own Google account) — the video ID, public link and publication status of each published DADZILLA video, together with the episode title, scheduled release time, a checksum of DADZILLA's own video file, run timestamps, error codes, API quota diagnostics and the dated results of DADZILLA's periodic re-checks of its own videos; (2) automation run records held by n8n Cloud for the launcher workflow, which contain the outcome the publishing workflow reported and are deleted automatically by n8n Cloud no later than 30 days after the run. Production upload runs are configured not to retain WF12 execution records. Manual read-only preflight and verification runs may be retained temporarily under DADZILLA's n8n Cloud execution-retention setting. Manual runs are blocked from creating uploads, thumbnails or resumable upload sessions. The temporary upload-session address YouTube issues during an upload is therefore never persisted. Access tokens, refresh tokens and client secrets are never written into DADZILLA's production records and are never published.

How the sign-in credential is stored. The OAuth credential is stored as a restricted credential in DADZILLA's private n8n Cloud workspace and is not intentionally included in workflow logs or published records. n8n Cloud hosts the automation and stores the OAuth credential under its published security controls.

Who can see this data. The channel owner, and the service providers that host it — n8n Cloud, and Google for the spreadsheet and files in DADZILLA's own Google account. DADZILLA may permit owner-authorized technical service providers, including AI-assisted tooling, to process limited operational data solely to configure, validate and troubleshoot the automation. They are not authorized by DADZILLA to use that data for advertising, data brokerage or unrelated purposes. DADZILLA does not sell this data, does not share it with advertisers or data brokers, and does not use it for advertising. Once a DADZILLA video is public, its public YouTube link may appear in DADZILLA's own posts and pages.

Limited Use. DADZILLA'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. Google's own handling of data is described in the Google Privacy Policy.

Revoking access — two separate steps. Removing the credential from n8n removes DADZILLA's stored connection. Revoking access through Google Account permissions at https://myaccount.google.com/permissions terminates the authorization granted through Google. The channel owner can do either at any time; doing one does not do the other.

Refreshing and deleting stored data. DADZILLA re-reads or deletes the YouTube data it keeps no later than 30 days after it was last read. If the channel owner revokes access or asks us to delete this data, DADZILLA removes the stored credential, deletes the stored authorized YouTube data and the related production-record entries, and deletes any remaining automation run records, within 7 calendar days. Deleting DADZILLA's records does not delete videos, channel data or anything else held by YouTube or Google; those are managed in YouTube Studio and the Google account. Requests: email [email protected] — these requests are completed within the 7-day period above; the 30-day period in "Your controls" continues to apply to everything else in this policy.

Where it lives

Workout data is stored in your browser on the device you use, and is never transmitted to us. There is no cloud copy and no account. To move your log to another device, export a backup file from Settings inside the app and restore it there.

Your controls

Ask us any time to export or permanently delete everything we hold about you — email [email protected] and it's done within 30 days. Your training log is separate: clearing site data for dadzillafit.co in your browser erases it from that device permanently.

Changes

If this policy changes in a way that matters, we'll email you and post the new effective date here before it takes effect.