Privacy Policy

1. Application identity

Application: AAD · GitHub Actions Reporting
Site / operator identity: ADZ Code Dev
Contact: adz.prime.origin@gmail.com

2. Google data accessed

The application requests these OAuth scopes:

• https://www.googleapis.com/auth/spreadsheets
• https://www.googleapis.com/auth/drive.readonly
• https://www.googleapis.com/auth/script.scriptapp

3. Purpose of access

• Google Drive read-only: read the run index and reporting source files required for GitHub Actions reporting refresh.
• Google Sheets: read and update destination reporting workbooks.
• Apps Script trigger management: create and manage the installable trigger used for scheduled refresh checks.

4. Use of Google user data

Google user data is used only to provide and maintain the reporting functionality described on the application homepage. The application does not use this data for advertising, profiling, unrelated analytics, credit decisions, or unrelated product development.

5. Limited Use compliance

AAD · GitHub Actions Reporting's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data is not sold. It is not transferred to advertising platforms, data brokers, or unrelated third parties. It is not used to train general-purpose artificial-intelligence or machine-learning models.

6. Storage, transfer, and sharing

The reporting workflow is implemented in Google Apps Script and uses Google Drive and Google Sheets. It does not intentionally transmit Google user data to a separate third-party backend service. The website itself uses no cookies, third-party analytics tags, advertising scripts, or embedded trackers.

7. Retention and deletion

Source artifacts remain in the user's Google Drive under the user's own retention controls. Materialized reporting data remains in the destination Google Sheets workbooks until the operator overwrites or deletes it. Revoking OAuth access prevents future refreshes but does not automatically delete files already stored in the user's own Google account.

8. Revoking access

A user can revoke this application's OAuth access through Google Account permissions. After revocation, the script cannot access the authorized Google data until authorization is granted again.

9. Changes

This policy will be updated if the application's functionality, requested scopes, or Google-data handling materially changes.