Privacy Policy

Smart Consumer Guides

Effective date: September 17, 2026

This Privacy Policy explains what Smart Consumer Guides — a private desktop automation tool used by its owner to produce and upload video content to their own YouTube channel — accesses, why, and how it is protected. It is operated by the same person who builds Didi, but it is a separate product from the Didi mobile app and holds none of Didi's data. If you are looking for Didi's own privacy policy, see usedidi.com/privacy instead.

Who uses this tool

One person: its owner. Smart Consumer Guides is not a public-facing service and is not offered to anyone else. It has no user accounts, no sign-up, no multi-tenant storage and no other operators. It runs locally on the owner's own computer, and the only YouTube channel it is ever authorized against is the owner's own channel.

Google user data this tool accesses

The owner authorizes the tool through Google's standard OAuth 2.0 consent screen. It requests exactly these scopes, and only these:

• https://www.googleapis.com/auth/youtube.upload — permission to upload a video file to the authorized channel. This is how a finished video reaches YouTube.
• https://www.googleapis.com/auth/youtube.readonly — read access used for two things only: reading the authorized channel's own identity (its channel ID, title and handle) so a video cannot be uploaded to the wrong channel, and reading back the status of a video the tool itself uploaded (whether YouTube has finished processing it, and its current privacy setting).
• https://www.googleapis.com/auth/youtube.force-ssl — required by the YouTube Data API to set a custom thumbnail on a video the tool has uploaded, and to change that video's visibility when the owner explicitly chooses to do so.

In practice the tool calls four YouTube Data API endpoints: channels.list (channel identity), videos.insert (upload), thumbnails.set (custom thumbnail) and videos.list (processing status). It also calls videos.update in the single case described below, when the owner deliberately changes a video's visibility.

What the tool does not access

It does not read or manage any channel other than the one the owner authorizes. It does not access comments, subscriber lists or identities, private messages, watch history, search history, analytics about viewers, monetization data, playlists, live chat, or any other person's Google account data. It does not request Gmail, Drive, Contacts, Calendar or any Google scope outside the three YouTube scopes listed above. It never sees or stores a Google account password: sign-in happens entirely on Google's own consent screen.

What is stored, and where

Everything is stored locally on the owner's own computer. There is no server, no hosted database and no cloud account associated with this tool. Specifically:

• An OAuth refresh token and access token, written to a file in the application's own secrets/ directory on the owner's machine, with owner-only file permissions where the operating system supports them. The directory is excluded from version control, and the tool never prints, logs or transmits the token anywhere except to Google's own token endpoint over HTTPS/TLS.
• The authorized channel's ID, title and handle, so the tool can show which channel it is connected to and refuse to upload to a different one.
• A record of videos it has uploaded — the YouTube video ID, the title, the upload and processing status, and the time — kept in a local database file so the tool can tell that a video has already been uploaded and refuse to upload it a second time.

How this data is used

Exclusively to operate the tool's single function: uploading the owner's own finished videos to the owner's own YouTube channel, and confirming afterwards that YouTube received and processed them. It is not used for advertising, for profiling, for training any machine-learning model, or for any purpose unrelated to that function.

We do not sell or share Google user data

Google user data obtained through these scopes is never sold, rented, traded or shared with any third party. It is not shared with Didi or with any other product. It is transmitted only to Google's own APIs, as required to perform the actions the owner has asked for. There are no advertising networks, analytics providers, data brokers or human reviewers with access to it.

Google API Services User Data Policy

Smart Consumer Guides' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Use of the tool is also subject to the YouTube Terms of Service and the Google Privacy Policy.

Retention, revoking access and deletion

The stored token remains on the owner's computer until it is revoked or deleted. Authorization can be revoked at any time, independently of this tool, from Google Account → Third-party apps & services; revoking there immediately makes the stored token useless. Deleting the token file from the application's secrets/ directory removes it from the computer entirely. The local record of uploaded videos can be deleted with the rest of the application's local database at any time; it contains no personal data about anyone other than the owner's own channel.

Data security

All communication with Google is over HTTPS/TLS. The token file is stored outside version control with owner-only permissions where the operating system supports them, and the application is written so that a token value is never written to a log line, an error message or a URL. The computer itself is the security boundary: there is no remote service to breach.

Children

The tool is not directed at children and is not usable by anyone other than its owner. It collects no data from any member of the public.

Changes to this policy

This Privacy Policy may be updated from time to time. The "Effective date" above reflects the most recent revision.

Contact

For privacy-related questions or requests, including revoking access or deleting stored data: legal@usedidi.com

See also the tool's homepage and its Terms of Service.