Privacy Policy

Data we access

With the channel owner's OAuth consent, the application accesses YouTube channel identity, channel counters, public video identifiers, titles, publication dates, duration and statistics. Authorised YouTube Analytics reports may include views, engaged views, watch time, average viewing duration and percentage, likes, comments counts, shares and subscribers gained.

We request only youtube.readonly and yt-analytics.readonly. We do not request access to Gmail, Google Drive, financial analytics, upload or channel-management permissions. The current collector retrieves aggregate counts, not individual viewers' identities or comment text.

Instagram Insights access is planned but is not currently connected. This policy will be updated to describe any additional connected data before it is used.

How we use data

Data is used solely to identify the authorised channel, collect dated measurements, prepare private performance reports, check data quality and help the owner decide what content works. Missing information remains unknown; the application does not invent results.

We do not sell Google user data, use it for advertising, or use it to develop, improve or train generalised artificial intelligence or machine-learning models.

Storage and security

Analytics snapshots are stored on the owner's Hetzner server and may be copied to the owner's computer for analysis. OAuth credentials are kept separately from public website files and source repositories in restricted configuration files. API connections use HTTPS; transfers between the owner's computer and server use SSH.

This public website does not contain the owner's private statistics, reports, OAuth tokens or credentials.

Sharing and service providers

Google supplies the authorised YouTube API data. Hetzner provides the server used to store and process it. The owner may provide selected reports or aggregate summaries to their chosen AI assistant, including OpenAI's ChatGPT/Codex, solely for analysis requested by the owner. Such processing is subject to that provider's terms and the owner's account settings; this application does not authorise use of Google user data for training generalised models.

The public information pages are hosted using OpenAI Sites and its hosting providers. Routine hosting request logs may include technical information such as IP address, request time and user agent. The application does not add advertising trackers, tracking pixels, analytics cookies or contact forms to these pages.

Retention and deletion

Channel measurements are retained for the owner's reporting until the owner deletes them. There is currently no automatic retention-expiry job. The owner can delete snapshots and reports on the server and local computer, or request help by emailing tg@trypace.app. Credential files can also be removed.

Revoking OAuth stops future access but does not automatically delete previously collected reports. Data copies supplied to an AI assistant or another provider may need to be deleted separately using that provider's controls. No promise is made that deleting one local file removes other copies or provider backups.

Control and revocation

The owner may review or revoke the application's Google access at any time through Google Account permissions. If access is revoked or expires, collection stops until the owner authorises it again.

Google API Limited Use

Luda Analytics' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Contact and changes

For questions, correction or deletion requests, contact Arina Nesinova at tg@trypace.app. Changes to this policy will be published here with an updated effective date.