Pipsar

Privacy Policy

Pipsar YouTube Automation · Last updated 20 November 2026

This policy explains what data Pipsar YouTube Automation (“Pipsar”, “the app”, “we”) accesses, how it is used, stored and protected, and how access can be revoked. It covers the app’s use of Google OAuth and the YouTube Data API, and visits to the website pipsar.eu.

1. Who operates the app

Pipsar is a private, single-operator tool run by the owner of the domain pipsar.eu. It produces educational videos and publishes them to the operator’s own YouTube channel. It has no public user accounts; the only Google account connected to it is the operator’s. Contact: contact@pipsar.eu.

2. Google user data we access

The app uses Google OAuth 2.0 and requests only these scopes:

ScopeWhat the app does with it
https://www.googleapis.com/auth/youtube.uploadUploads finished videos to the authorised channel (video file, title, description, tags, category, language, privacy status, “made for kids” and synthetic-media declarations) and sets the video thumbnail.
https://www.googleapis.com/auth/youtube.readonlyReads the authorised channel’s ID, title and public subscriber count to confirm which channel is connected before uploading.

In the course of this, the app handles:

The app does not access or store the Google account’s email address, contacts, Gmail, Drive files, YouTube comments, subscriber lists, watch history, analytics or any data of other YouTube users.

3. How we use Google user data

Google user data is used only to provide the app’s single feature: publishing the operator’s own videos to the operator’s own YouTube channel and confirming the connected channel. It is not used for advertising, is not sold, is not used to build user profiles, and is not used to develop, improve or train artificial-intelligence or machine-learning models.

4. Sharing and transfer

Google user data is not shared with, transferred to or disclosed to any third party. Uploaded video content and its metadata are sent only to YouTube (Google), which is how publishing works.

The app uses other services to create videos, but none of them receive Google user data: scripts are drafted with the Anthropic Claude API and narration is generated with the Google Gemini API from the video script text only; terrain and satellite data are downloaded from public open-data sources (Copernicus, AWS Open Data).

5. Storage and protection

6. Retention and deletion

7. Revoking access

Access can be revoked at any time on the Google Account permissions page: myaccount.google.com/permissions. After revocation the app can no longer upload or read channel data, and the stored tokens become invalid and are deleted.

8. Google API Services User Data Policy

Pipsar’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

9. YouTube API Services

Pipsar uses YouTube API Services. By using the app you agree to be bound by the YouTube Terms of Service. Google’s handling of data is described in the Google Privacy Policy.

10. Visitors to pipsar.eu

This website uses no cookies, no analytics, no advertising and no third-party scripts, fonts or embeds, and has no forms. Like any web server, it records technical access logs (IP address, date and time, requested page, browser user-agent) for security and troubleshooting. These logs are rotated daily and deleted after 14 days.

11. Your rights

If you are in the European Union, you have the right to access, correct or delete personal data about you, to object to or restrict its processing, and to lodge a complaint with your data-protection authority. To exercise these rights, contact contact@pipsar.eu.

12. Children

The app is not directed at children and does not knowingly collect data from children.

13. Changes

If this policy changes, the updated version will be published on this page with a new “Last updated” date. Any change in how Google user data is used will be reflected here before it takes effect.