DATA HANDLING / OWNER-OPERATED APPLICATION
Privacy policy.
This policy explains how Crush Circuit Automation accesses and uses Google and YouTube account information. The application is a private tool operated for the CRUSH CIRCUIT YouTube channel, not a service that accepts public registrations.
01 Who operates this application?
Crush Circuit Automation is operated by Cemalettin Altinsoy for the owner's CRUSH CIRCUIT YouTube channel. The application is used to assist in preparing, reviewing, uploading and scheduling original AI-assisted industrial ASMR videos and analyzing their performance.
02 What information may be accessed?
Only after the Google account owner grants permission through Google's OAuth consent flow, the application may access information related to the authorized YouTube channel, including:
- Channel identification and basic channel information needed to target the correct account.
- Videos, upload results, video IDs, publishing states, titles and descriptions required to manage the owner's content.
- Channel-owned video statistics and performance metrics supplied by the YouTube Analytics API.
- OAuth access and refresh tokens required to maintain the authorized connection.
The application does not ask viewers of the public YouTube channel to sign in and does not collect their Google account credentials.
03 How is the information used?
Google and YouTube data is used solely to operate and improve the owner's channel workflow: upload and schedule videos, prevent duplicate publication, confirm publishing outcomes, monitor channel performance, and troubleshoot failures. Automated analysis may compare performance metrics across the owner's videos to inform future content decisions.
Google account data is not used for advertising, resale or unrelated user profiling.
05 Security and retention
The tool is operated on owner-controlled infrastructure. Access credentials and application records are held in access-restricted storage, and access is limited to the operator. Security controls are intended to reduce accidental disclosure, but no internet-connected system can guarantee absolute security.
Operational records and authorized account data are retained only as long as needed for channel operation, troubleshooting and accounting. They may be removed when no longer necessary or when the owner retires the integration, subject to applicable recordkeeping needs.
06 Access, revocation and deletion
The Google account owner can review or revoke the application's permissions at any time from the Google Account connections page ↗. Revoking permission prevents future API access through the revoked credentials, though records already held by the operator may still require deletion.
The owner can also request access to or deletion of locally stored account data by contacting the operator through the app's user support email shown on Google's OAuth consent screen.
07 Contact and changes
For questions, data access, correction or deletion requests, please use the user support email listed on this application's Google OAuth consent screen. This is the official support contact for the tool.
This policy may be updated if the application's features, data uses or service providers change. The date at the top of this page indicates its most recent revision.
The application is designed to use information received from Google APIs only for the purposes explained above, subject to the Google API Services User Data Policy ↗, including applicable Limited Use requirements.