Ranjha Solutions monogram RANJHA SOLUTIONS LEGAL • CONTENT • AUTOMATION • BUSINESS SETUP
AUTOPILOT TOOL

Privacy Policy

This policy explains, in plain language, what data Autopilot Tool by Ranjha Solutions stores, where it is stored, and how it is used. It is short because the tool genuinely handles very little data.

LAST UPDATED: 21 OCTOBER 2026

The short version: Autopilot Tool stores only the OAuth tokens issued when the channel owner signs in, plus the job details the owner types in and the resulting video IDs. Everything is stored locally on the owner's own machine with owner-only file permissions. Nothing is sold, shared, rented or used for advertising. Sign-in happens only on Google's own pages, and access can be revoked at any time.

1. What the app is

Autopilot Tool is a publishing automation tool built by Ranjha Solutions and currently used only on Ranjha Solutions' own YouTube channels. It uploads the owner's own videos at scheduled times through the official YouTube Data API v3, using the single permission described in section 3. Full details are on the Autopilot Tool page.

2. What data the app stores

The app stores only:

  • the OAuth tokens issued when the owner consents to connect a channel;
  • the job metadata the owner types into the tool — titles, descriptions, tags and the schedule; and
  • the video IDs of the videos the tool uploads.

No passwords are ever seen or stored by the app. Sign-in happens entirely on Google's own pages.

3. The one permission it uses

The app requests a single Google permission — the YouTube upload scope (youtube.upload) — and uses it for exactly one thing: uploading the owner's own video files to the owner's own channels, with the metadata the owner supplied, and attaching the owner's own thumbnail where one is provided. The app does not read channel analytics, comments or subscriber data, and it does not modify or delete existing videos.

4. Where the data is stored

Everything is stored locally, on the owner's own machine. Tokens sit in a secrets/ folder with owner-only file permissions (chmod 600), and job records sit in a local SQLite database on the same machine. Nothing is stored on third-party servers.

5. How the data is used

The refresh token is used solely to obtain access tokens so that scheduled uploads can run unattended — the exact purpose the owner authorised. Tokens are never sent anywhere except Google's own OAuth and API endpoints. Job metadata is used only to create the uploads it describes, and video IDs are recorded only so the tool can confirm each upload to the owner by email.

6. Sharing

No data is sold, shared or rented, and no data is used for advertising or profiling. There are no third-party analytics, advertising or tracking services in the app.

7. How long tokens are kept — and how to revoke access

Tokens are kept only while the owner uses the tool. The owner can revoke the app's access at any time from the Google Account third-party access page. Deleting the local token file disconnects a channel immediately.

8. Contact

Any question about this policy or about the data the app holds: info@ranjhasolutions.com.