Privacy Policy

Last updated: October 3, 2026

This policy covers the Sleepfathom website and Sleepfathom Automation, our self-hosted n8n application for preparing ambient-sound videos and uploading owner-approved videos to a connected YouTube channel. The application is operated by Sleepfathom. Contact: sleepfathom.channel@gmail.com.

Google and YouTube data we access

When a channel owner connects a Google account, Google provides OAuth access and refresh tokens that let the application upload videos to the authorized YouTube account. The application requests only https://www.googleapis.com/auth/youtube.upload. Google handles account sign-in and consent; Sleepfathom Automation does not receive or store the Google account password.

For an approved upload, we process the video file and the title, description, category, tags and visibility selected for that upload. We also process the video identifier and upload responses returned by YouTube, including operational status or error information needed to confirm or troubleshoot the upload. This workflow does not request access to Gmail, Google Drive, contacts, comments, channel-wide analytics or a library of existing channel videos.

How we use Google user data

We use OAuth tokens only to authenticate the connected account and perform uploads approved by the channel owner. We use video files and metadata to submit those uploads to YouTube, and the returned video identifier and execution information to verify the result and support the owner. Test uploads are submitted as private videos for owner review. Public publication requires a separate owner decision.

We do not sell Google user data, use it for advertising or profiling, or use it to develop, improve or train generalized artificial intelligence or machine-learning models. Sleepfathom Automation's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Sharing, transfers and service providers

Video files, upload metadata and authentication requests are sent to Google/YouTube to perform the requested upload. Our self-hosted n8n application, its credentials and operational files are hosted on a Hostinger virtual private server; Hostinger provides the infrastructure used to store and process them. Access to the application and its server is restricted to the operator and authorized administrators.

Separate content-preparation steps may use OpenAI for generated text, Pexels for images and Bannerbear for thumbnails. These services receive the content inputs needed for those steps, such as a theme, generated thumbnail text or an image URL. They are not used to process Google OAuth tokens or data retrieved from the connected Google account. We do not otherwise share, transfer or disclose Google user data except at the account owner's direction or where required by law.

Use of YouTube is also subject to Google's Privacy Policy.

Data protection

The application uses HTTPS for browser access and requests to Google's APIs. OAuth credentials are kept in n8n's encrypted credential storage rather than in public pages or video metadata. Application authentication and server access controls restrict access to credentials, video files and execution records. Credentials and tokens are not intentionally included in demonstration recordings or public content. Access is limited to the work needed to operate, maintain and support the application.

Retention and deletion

OAuth tokens are retained while the owner maintains the authorized connection. Disconnecting the integration and deleting its stored credential removes the application's stored connection information. Upload identifiers and workflow execution records are retained only as needed to confirm uploads, diagnose failures and maintain the owner's project records; they can be removed through the application's execution and project controls or by contacting the operator. Prepared video files and thumbnails remain on the server while needed for review, delivery or the owner's content library, and can be deleted at the owner's request.

To request deletion of stored Google connection data, upload records or prepared files, email sleepfathom.channel@gmail.com with the connected channel and the data to remove. Please do not send passwords or tokens. We verify that the request comes from the account owner before removing their data. Copies in existing server backups may remain until those backups expire or are replaced under the configured backup schedule; they are not used for ongoing uploads after the connection is removed.

You can revoke the application's Google access at Google Account third-party connections. Removing local application data does not delete videos already uploaded to YouTube. The channel owner can manage or delete those videos in YouTube Studio.

Website information and cookies

The public website does not require visitors to create an account and does not use advertising, analytics or tracking cookies. Standard technical logs may be generated by the hosting provider to operate and secure the website. When you follow links to YouTube or other services, their own privacy policies apply.

Changes and contact

We update this policy when the application's data practices change and display the revised date on this page. Material changes to access, use or sharing of Google user data will be communicated before the changed practices take effect and will require renewed consent where applicable. For privacy questions or deletion requests, contact sleepfathom.channel@gmail.com.