Data transparency
Privacy Policy
This policy explains what Google and YouTube information SatisfyNest Analytics accesses, why it is used, where reporting information goes, and how users can revoke access or ask for deletion.
SatisfyNest Analytics is a privately operated creator reporting application. It uses Google OAuth to access authorized YouTube data and to write reports into an authorized Google Sheets spreadsheet. It does not sell Google user data, use it for advertising, or request Google account passwords.
1. Application operator and contact
SatisfyNest Analytics supports the SatisfyNest creator workflow and is maintained under the NEXORA projects. For privacy questions, access or deletion requests, contact pichai.jaijit@gmail.com.
2. Services and permissions used
This application uses YouTube API Services, YouTube Analytics API and Google Sheets API. The Google authorization permissions used by the current application are:
- YouTube read-only: channel identity, playlists and video information available to the authorized account, including video identifiers, titles, publishing timestamps, view counts, likes and comments counts where available.
- YouTube Analytics read-only: authorized channel/video performance metrics, such as daily views, watch time and other available analytics fields.
- Google Sheets read/write: read and modify spreadsheets through the Google Sheets API, used by the application for the spreadsheet that the owner configures for reporting. The Google-granted scope may permit access to other spreadsheets; the current workflow targets the configured reporting spreadsheet.
The application does not request permission to upload or delete YouTube videos or manage your YouTube channel content. It does not ask you for your Google password.
3. How information is used
Authorized data is used to verify the expected YouTube channel, retrieve video statistics and reporting periods, and record performance snapshots or daily reports. Reporting records are stored in the connected Google Sheets spreadsheet selected by the operator. Data is not used to build advertising profiles or for unrelated products.
4. Storage and retention
OAuth authorization tokens are held in access-restricted application files in the operator-controlled environment running the reporting workflow, and are not published on this website. YouTube metrics and video metadata are stored in the configured Google Sheets spreadsheet for ongoing creator reporting while the authorization remains valid and the reports are needed. Backups, if maintained by the operator, follow the same access restrictions. We review authorization and refresh or remove stored API information as required by the applicable YouTube API policies.
The reporting spreadsheet belongs to the Google account that controls it. Deleting access tokens does not automatically delete reporting cells stored in that account's spreadsheet.
5. Data sharing and third parties
Authorized Google user data is not sold, rented or disclosed to advertisers. Data is exchanged with Google APIs to retrieve authorized YouTube data and update Google Sheets. Cloudflare delivers this public static website and may process standard service logs for security and delivery. Authorized reports are not published on this public website. Information may be disclosed where required by applicable law, and access is restricted to the authorizing user and persons they expressly approve.
6. Security
The reporting application uses OAuth authorization instead of collecting Google account passwords. Tokens must be kept out of public website files and source-code repositories. Access to operator-controlled devices or infrastructure should be restricted. No internet-connected system can guarantee absolute security.
7. Cookies and this public website
This public informational website has no application login, advertising tags, or first-party analytics JavaScript. Its hosting provider may process standard technical request information to deliver pages and prevent abuse. Any future tracking or material privacy change will be reflected in an updated policy.
8. Revoking access and requesting deletion
You may revoke the application's Google access at any time from Google Account connections. To request deletion of locally retained authorization tokens or reporting data controlled by the application operator, email pichai.jaijit@gmail.com. We will remove data under our control consistent with applicable API policies and legal obligations. If copies remain in a spreadsheet owned by your Google account, you may delete them directly or request assistance.
After an authorization is revoked, the application must cease using that authorization. Stored authorized YouTube data is subject to YouTube's deletion and refresh requirements, including applicable 30-day limits following revocation.
9. Google's and YouTube's policies
Google's handling of data in its own services is described in the Google Privacy Policy. By using an application that integrates YouTube API Services, you are also subject to the YouTube Terms of Service. See our Terms of Use.
10. Updates
We may update this policy if the application changes. The current effective date appears at the top of this page. Material changes to how Google user data is used will be disclosed before use where required.