Data practices
Privacy policy
Auralith Studio is a personal, local macOS production application. This policy describes its optional Google/YouTube integration and this informational website.
Google data accessed
With the owner’s consent, Auralith receives OAuth access and refresh tokens and reads the selected channel’s identifier, title, upload eligibility and playlists. It reads video identifiers, metadata, thumbnails, upload status, processing details and visibility for the delivery workflow.
The integration requests youtube.upload, youtube.readonly and youtube.force-ssl. These permissions support uploading videos, reading the connected channel, and updating video metadata and playlists. Google’s permission wording is broader than the operations used in an individual production. The connection does not give this website access to the account.
How data is used
Google data is used to connect the correct channel, upload owner-selected media, set thumbnails and metadata, check processing and visibility, and retain receipts that prevent duplicate uploads. Public publication is a separate owner-directed operation.
Auralith Studio’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not sold, used for advertising, or used to train general-purpose AI or machine-learning models.
Storage and retention
OAuth credentials and resumable-upload session information are stored in owner-restricted files in the local application-support directory. They are not included in public release packages or this website. The owner is responsible for securing the computer and its backups.
Media, metadata, channel/video identifiers and sanitized production receipts are retained locally until the owner deletes them. Selected media and metadata sent to YouTube remain there under Google’s services and privacy controls. Disconnecting Auralith does not delete videos already uploaded or local production files.
Sharing and automation
Chosen media, thumbnails and metadata are sent to Google/YouTube to perform authorized delivery. The owner’s configured production-assistant and Operations Hub integrations may read workflow metadata and sanitized delivery receipts. At the owner’s request, completion reports containing selected video links and production status are sent to the owner’s private Telegram destination through the existing Hermes connection. Those services apply their own data practices.
OAuth tokens are used by the local YouTube helper for authentication and are not intentionally included in assistant messages, Telegram reports or public artifacts. This informational website has no Google account connection, upload form or embedded private media.
Revocation and deletion
The owner can use Auralith’s Disconnect control to revoke its Google authorization and remove the local sign-in, or remove access through Google Account connections. Local projects, media and receipts can be deleted separately; uploaded videos can be managed or deleted in YouTube. For a data request, contact nbaxevanis@gmail.com.
Website visitors
The page source adds no analytics, advertising trackers, forms or cookies. The hosting provider may process ordinary request information, such as IP addresses and browser details, to deliver and secure the website. Emailing the contact address shares the contents of your message with the operator and the relevant email providers.
Changes
Updates to these practices will be reflected on this page with a revised effective date.