Last updated: 29 October 2026
This policy explains what personal data AI News Trend collects, why, how long we keep it, and the rights you have under the EU General Data Protection Regulation (GDPR) and the ePrivacy Directive.
Google / YouTube account data: Our publishing integration's data protection mechanisms and data use, retention and deletion practices are described below.
The data controller for this website is AI News Trend (“we”, “us”). For any privacy question or to exercise your rights, contact us at privacy@ainewstrend.com.
We do not set any non-essential cookies until you give consent. When you first visit, all analytics signals are set to “denied” (Google Consent Mode v2) and no Google Analytics script is loaded. Only if you choose “Accept all” is the analytics script loaded and a cookie set.
| Cookie | Purpose | Type | Retention |
|---|---|---|---|
cookie_consent_v1 | Remembers your cookie choice | Essential (local storage) | Until you clear it |
_ga, _ga_* | Google Analytics — anonymous usage statistics | Analytics (only after consent) | Up to 24 months |
You can change or withdraw your choice at any time: .
These providers act as processors on our behalf and may transfer data outside the EU under appropriate safeguards (e.g. EU Standard Contractual Clauses).
Under the GDPR you have the right to access, rectify, erase, restrict, and port your data, and to object to processing. You may withdraw consent at any time without affecting prior processing. To exercise any right, email privacy@ainewstrend.com. You also have the right to lodge a complaint with your local data protection authority.
Analytics data is retained for up to 24 months. Newsletter data is kept until you unsubscribe. Technical logs are retained only briefly for security purposes.
AINewsTrend uses YouTube API Services in an owner-operated publishing tool to upload our news videos, attach thumbnails and check publication results on our own YouTube channel. Website visitors do not need to connect a Google account. Google authorization for this tool is separate from website analytics and newsletter subscriptions.
Data accessed and stored. With the channel owner's authorization, the tool accesses the connected channel's ID, name and status, and the IDs, titles, descriptions, thumbnails, duration, processing status and visibility of videos it manages. It also handles the video files, thumbnails and publication settings supplied for upload. We store an OAuth refresh token, granted permissions, connection time, upload receipts and local operational records so scheduled publishing can continue without asking the owner to sign in for every upload. We request YouTube read-only and upload permissions; this integration does not request access to Gmail, Google Drive, Google Photos, contacts or a viewer's Google account. We do not request or store the owner's Google password.
How this data is used and shared. We use it to verify the correct channel, perform owner-authorized uploads, apply thumbnails, check processing and publication, prevent duplicate uploads and diagnose failures. Videos and their publication metadata are sent to Google/YouTube; public uploads are visible to viewers according to their YouTube visibility settings. Operational records are processed locally by the channel operator and are not sent to our newsletter or website analytics services. We do not sell Google user data, use it for advertising, or provide raw or derived Google account data to AI services for model training. Our news-script and media generation is separate from this account connection and does not use OAuth credentials or private channel data as model input.
Google API requests and token exchanges use HTTPS/TLS to protect data in transit. The saved refresh token is encrypted on the local Windows machine using Windows Data Protection API (DPAPI), tied to the Windows user account that runs the service. Short-lived access tokens are used in process memory. The authorization flow uses a random state value and PKCE, and its callback listens only on the local loopback interface. The upload client checks the expected channel and restricts authenticated requests to allowed Google API destinations. Credentials are kept outside public website assets and excluded from the source repository; normal connection reports contain status information rather than token values. Other local publication records are ordinary files, not covered by the refresh token's DPAPI encryption. Browser-based Studio steps use the operator's local signed-in Chrome profile; its session is separate from the API token store.
Retention, revocation and deletion. The refresh token is retained while the owner keeps the publishing connection active. Local publication and diagnostic records support upload recovery and operational history. The operator handles removal of stored account data; there is no self-service account portal on this website. To disconnect, remove AINewsTrend in your Google account's connected-app permissions. To request deletion of locally stored Google account data, email privacy@ainewstrend.com or hello@gitstudio.se, identifying the connected channel. We handle these requests manually, stop the connection and delete the associated saved credentials and account records within seven calendar days. Deleting our local records does not delete videos or other data held by YouTube; manage those separately in YouTube Studio.
Google's handling of data is described in the Google Privacy Policy. Use of YouTube is also subject to the YouTube Terms of Service.
We may update this policy as our practices or the law evolve. The “last updated” date above reflects the most recent change.