Privacy Policy

1. Scope and contact

This Privacy Policy applies to the UAVideo Ads local advertising management and reporting application and its public informational website. The application is used for the operator's own Google Ads accounts or accounts they are explicitly authorized to manage. It does not offer public account registration.

The developer and privacy contact is honormagic8@gmail.com. Questions and data requests should identify UAVideo Ads and the relevant data or account, without including passwords, access tokens or private keys.

2. Information accessed and collected

After authorization, UAVideo Ads accesses the following information as needed for the requested operation:

• Advertising account information: customer identifiers, accessible account settings and configuration relevant to the operation.
• Advertising resources: campaigns, ad groups, ads, creative assets and copy, asset identifiers, budgets, bids and related configuration.
• Aggregate performance information: impressions, clicks, costs, conversions, conversion values and requested reporting dimensions.
• Operator-supplied content and local records: images, videos, ad copy, operation instructions, exported reports, API responses, errors, review records and operation receipts.
• Authorization information: OAuth credentials or operator-configured service-account credentials used to authorize Google API requests.

The Google Ads API scope is https://www.googleapis.com/auth/adwords. This authorization does not grant the application access to Gmail messages, contacts or private Google Drive files. The tool does not request individual ad viewers' identity profiles; reports mainly process account-level and ad-level aggregate metrics. The application does not ask users to provide their Google password to the developer.

3. How the information is used

Google Ads data is used to display and analyze advertising performance, produce local reports, organize and review creative assets, execute explicitly requested advertising operations, diagnose errors, avoid duplicate operations and preserve operation records. Access is limited to the permissions needed for these functions.

Credentials are used to authenticate authorized API requests. They are not included in the public website or supplied as prompts to assistance services. Advertising data is not published through this informational site.

4. Sharing, transfers and human access

• Google: receives authorization requests and the account operations, settings or creative content needed to perform the operator's requested Google Ads actions.
• Authorized operators: the operator and people they explicitly authorize may inspect local reports, creatives and records for analysis, review, support and troubleshooting.
• Explicitly selected processing services: the operator may provide selected reports, copy or assets to assistance services such as OpenAI / Codex. Such transfers must be authorized, necessary for the explicitly requested functionality, and handled under the applicable processing terms and settings. They do not permit sale of Google user data or general-purpose model training.
• Cloudflare: hosts and delivers the public application information and policy pages. Cloudflare may process technical request information for delivery and security under its privacy policy. Advertising account records and credentials are not published on this website.
• Legal requirements: information may be disclosed where required by applicable law.

UAVideo Ads does not sell Google user data or provide it to data brokers or information resellers. It does not use Google user data to build unrelated advertising profiles, determine creditworthiness, or train general-purpose AI or machine-learning models. Google Workspace APIs are not used by this application to develop, improve or train non-personalized AI or machine-learning models.

UAVideo Ads' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

5. Security and storage

Requests to Google OAuth and Google Ads API endpoints use HTTPS/TLS to protect data in transit. Credentials are configured separately in the operator-controlled local environment and are not embedded in public pages or public source code. Reports and operation receipts are saved to local directories controlled by the operator. This website has no account-data download or account-operation interface.

Local access protection relies on operating-system accounts, file permissions and device security. The application does not add encryption at rest or automatic scheduled deletion; this policy does not claim that all local files are encrypted. Operators must restrict device and backup access and must not publicly share credentials or unsanitized reports.

6. Data retention

OAuth or service-account credentials remain until replaced, revoked or deleted. Reports, exports, API responses, creatives and operation receipts are retained for the operator's reporting, operational, troubleshooting and audit needs. They should be removed when no longer needed or following a verified deletion request, unless retention is required by law.

There is no universal automatic expiry or scheduled deletion mechanism. The operator must also remove relevant exports and operator-controlled backups. Removing local records does not automatically remove advertising resources already created in Google Ads. Google controls retention of data on its own systems under its policies.

7. Access, export, correction and deletion

Operators can stop running UAVideo Ads and remove local credentials, reports, exports, API receipts, creatives and backups they control. Other authorized users can request access, correction, export or deletion by emailing honormagic8@gmail.com with the subject UAVideo Ads data request. Specify the relevant account and requested data scope without sending passwords, tokens or private keys.

The developer will verify the requester's authority over the relevant account before processing the request and will explain completion or any legally required retention. A deletion request concerns records controlled by the operator or developer; Google-held resources and data remain subject to Google's controls and policies.

8. Revoking Google access

For user OAuth, remove UAVideo Ads in your Google Account's third-party connections settings. For service accounts, an administrator can revoke the service account's Google Ads access or disable its relevant keys. Revocation prevents subsequent access under that authorization but does not automatically erase existing local files. Follow the deletion steps above to remove previously saved records.

9. Website access and policy changes

This static informational website has no login form, added analytics trackers or advertising scripts. Cloudflare may process IP addresses and other technical access information for hosting and security under the Cloudflare Privacy Policy.

Updates to this policy are published here with a revised date. Affected authorized users will be notified before material changes to previously authorized uses of their Google data take effect, and renewed consent will be obtained where required.

10. Data categories, sources and specific uses

The following details explain the data handling of UAVideo Ads. The categories accessed in a particular run depend on the account permissions and the operator's requested task; the tool does not need to retrieve every available field for every operation.

Advertising account identifiers and configuration

Source: the operator's configuration and authorized Google Ads API responses. Information: customer identifiers and relevant account configuration. Purpose: identify the intended account, direct API requests correctly and associate reports and operation receipts with that account. Storage and recipients: local configuration and relevant report records; Google receives the identifiers needed to process API requests. The identifiers are not displayed on this public website.

Campaigns, ad groups, ads and creative metadata

Source: authorized Google Ads API responses and operator-supplied instructions. Information: resource identifiers, names, status, asset associations, advertising copy and configuration such as budgets and bids. Purpose: list and review advertising resources, associate performance with campaigns or assets, and execute specifically requested operations. Storage and recipients: local reports and receipts; relevant parameters are transmitted to Google when an operation requires them.

Advertising performance metrics

Source: Google Ads reports for the requested dates and reporting dimensions. Information: aggregate impressions, clicks, costs, conversions and conversion values, with requested dimensions such as date, country or advertising channel. Purpose: generate local performance reports and support the operator's analysis. Storage and recipients: local JSON, CSV or HTML reports. Selected report data may be processed by an assistance service only where the operator explicitly requests and authorizes that function. These reports are not a collection of individual ad viewers' identities.

Creative files and advertising copy

Source: files and text supplied or prepared by the operator, and authorized creative information returned by Google. Information: images, videos, ad text, asset identifiers, file metadata and review notes. Purpose: organize creative versions, support human quality review and submit authorized creative assets. Storage and recipients: operator-controlled local files; Google receives assets selected for submission. Optional creative-processing providers receive only the material necessary for an explicitly requested task. Operators must hold the necessary rights and consent for any people or other protected content depicted.

Authentication material

Source: Google authorization and the operator's credential configuration. Information: the applicable OAuth or service-account credentials and access tokens. Purpose: authenticate authorized API calls. Storage and recipients: the local execution environment and the relevant Google authentication/API endpoints. Credentials are not placed in public pages or repositories, included in public reports, or intentionally sent as prompts to analysis or creative services. The application does not ask users to disclose their Google password to the developer.

Operational and troubleshooting records

Source: the tool's requested operations and their API responses. Information: request parameters relevant to the operation, resource identifiers, returned errors, timestamps and operation outcomes. Purpose: understand failures, reconcile uncertain results, avoid duplicate operations and provide traceability. Storage and recipients: local operation records available to authorized operators. Users should avoid sending secrets in support requests; relevant record excerpts may be shared for a specifically authorized support task.

Support correspondence

Source: messages you choose to send to honormagic8@gmail.com. Information: your email address, message and any information you include. Purpose: respond to application, privacy and data-management requests, including checking authority to request account data changes. Storage and recipients: the developer's support mailbox and its email provider under the provider's terms. Correspondence is retained as needed to handle and document the request or satisfy applicable legal requirements. Do not include passwords, private keys or access tokens.

Public website access information

Source: requests made by your browser to this Cloudflare-hosted website. Information: Cloudflare may process IP addresses and technical request information for hosting and security. Purpose and recipient: Cloudflare's delivery and protection of the public website, under its privacy statement. UAVideo Ads does not add a visitor registration database, advertising scripts or analytics trackers to this site.

11. What happens when you revoke access or request deletion

1. Stop new processing: stop the local tool and revoke the relevant OAuth grant or service-account access.
2. Identify retained copies: locate relevant credentials, reports, exports, creative files, API responses and operation receipts in the operator-controlled environment, including backups.
3. Remove controlled records: the operator deletes records that are no longer needed or are covered by a verified deletion request, subject to applicable legal retention requirements.
4. Address separate service copies: where an explicitly selected service has processed relevant information, its deletion controls and applicable processing terms govern that service's retained copies. Local deletion alone does not delete those copies.
5. Distinguish Google Ads resources: previously created campaigns, ads or assets remain in Google Ads unless separately changed through authorized account controls. Deleting a local report does not delete a campaign or stop advertising spend.

For assistance, email honormagic8@gmail.com. Include the request type and the relevant data scope. The developer verifies account authority before disclosing or changing records and explains completion or any required retention. UAVideo Ads does not claim to have an automatic deletion scheduler or to control retention on Google's or other providers' systems.