Privacy Policy

Para Pusulası · Last updated: 8 September 2026

1. Scope

This policy describes how the Para Pusulası application ("the application") accesses, uses, stores and shares data obtained through Google APIs. The application is a private automation tool operated by Sahar Noorizadehtehrani ("the operator"). It has no public sign-up, no end users other than the operator, and it operates only on YouTube channels the operator owns or manages.

2. Data the application accesses

Category	Purpose
OAuth credentials (refresh and access tokens)	To act on the operator's own YouTube channels without repeated manual sign-in.
Channel identity (channel ID, channel title)	To confirm that a token is bound to the intended channel before any publishing action.
Video metadata (title, description, tags, thumbnail, publication time, video ID)	To create and update the operator's own videos.
Channel and video statistics	To generate internal performance reports for the operator. These statistics remain on the operator's server.

The application does not access Gmail, Google Drive, Contacts, Calendar, location data, or any other Google service. It does not access data belonging to any Google account other than the operator's own.

3. Permissions requested

Scope	Why it is needed
`youtube.upload`	To upload video files to the operator's own channels.
`youtube`	To set and update video metadata, thumbnails and publication settings.
`youtube.force-ssl`	To create comments and manage the operator's own YouTube resources, including videos, thumbnails and comments.
`youtube.readonly`	To read the operator's own channel and video records.
`yt-analytics.readonly`	To read performance statistics for the operator's own channels.

The application uses two separate OAuth credentials for each channel. The publishing credential requests youtube.upload, youtube, and youtube.force-ssl. The analytics credential requests youtube.readonly and yt-analytics.readonly. These permissions reflect the application's current operation and will be reduced to the minimum verified set before replacement credentials are issued.

4. How data is stored

OAuth credentials are stored in access-restricted locations on a single private server rented by the operator. Each credential file is readable only by the account that runs the application.
OAuth credentials are transmitted only to Google OAuth and Google API services, for authentication and for authorised API operations. They are not disclosed to any other external provider.
Credentials are never written to source control and never included in logs or reports.
When a credential stops working it is renamed to a timestamped archive file on the same server and replaced by a new one. Archive files are retained until removed manually and are treated as sensitive credentials, with the same access restrictions as active ones.
Video metadata and statistics are stored on the same server for internal reporting.

5. How data is shared

The application currently sends two aggregated, channel-level YouTube performance indicators — average view percentage and average watch time — to Anthropic, where they form part of the input used to prepare content. It does not send click-through rate, impression counts, OAuth credentials, or any individual viewer identity. This transfer is being removed; this policy will be updated when it is.

Beyond the transfer described above, Google user data is not sold, not rented, and not shared with any third party. Media search terms may be sent to Pexels, and narration text or media-generation prompts may be sent to other configured providers when those features are enabled. Those services are not provided with Google account data, OAuth credentials, YouTube Analytics statistics, or scores, bands, labels, or guidance derived from those statistics.

The operator does not use Google user data for advertising, for building profiles of any person, or to develop or train machine-learning models. The operator does not intentionally disclose Google user data for human review by any external provider.

6. Limited use

The application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data is used solely to provide and improve the publishing and reporting functions described in this policy.

7. Retention and deletion

OAuth credentials are retained for as long as the application is authorised for the relevant channel.
Authorisation can be withdrawn at any time from Google Account permissions. Withdrawal immediately ends the application's access to Google APIs for that channel and makes the stored credential unusable.
Video metadata, aggregated performance statistics, and archived credential files are currently retained until manually deleted by the operator. No automatic time-based deletion is currently enforced.
The operator can delete any stored data on request to the contact address below.

8. Security

Access to the server is restricted to key-based authentication.
All communication with Google APIs uses HTTPS.

9. Children

The application is not directed to children and is not used by anyone other than the operator.

10. Changes

Material changes to this policy will be published on this page with an updated revision date.

11. Contact

para@eduofficial.org