Affiliate Ads Manager Privacy Policy
Last updated: November 18, 2026. This policy applies to Affiliate Ads Manager, the internal advertising application developed for the operator of 1 True Reviews. Application support and data requests: [email protected].
Scope of this policy
This policy covers application data supplied through authorized reports and manual imports, and the intended handling of Google Ads data if direct API access is approved and enabled. Ordinary visits to this website are covered by the website privacy policy. Publishing this notice does not activate a Google connection.
Information accessed
Authorized advertising reports may include advertising account IDs, account names, currencies and time zones; campaign, ad group, ad and keyword identifiers or configuration; and aggregate performance information such as impressions, clicks, costs and conversion metrics when those fields are supplied. Manual keyword research imports may include keywords, countries, reporting periods, search volumes and low/high bid estimates.
The workspace also stores affiliate product and commission research, operator-entered brand corrections, and the source and update times used to compare records. These affiliate records come from separately configured sources and are not obtained from a visitor’s Google account.
The planned API connection is limited to the Google Ads services needed for authorized reporting and campaign-related keyword research. It is not intended to request access to Gmail messages, Google Contacts or a person’s general browsing history. Users should not submit passwords, payment-card details or unrelated personal information in application notes or support emails.
Authorization and credentials
Current imports require the operator to supply reports they are entitled to use. Before a direct Google connection becomes available, the application must obtain the relevant API access and the account holder’s authorization through Google’s authorization process. Google handles the account password. OAuth credentials and tokens, if the connection is enabled, are used to authenticate the authorized connection and must be kept in the operator-controlled environment, separate from public website assets.
Only necessary permissions will be requested. The consent screen and application will explain the enabled functions before authorization. New functions or materially different data uses will be disclosed before they are enabled.
How information is used
Advertising information is used to present reports, compare advertising costs with affiliate results, identify discrepancies and support brand, product and keyword research for authorized campaigns. Source records and correction history help the operator understand how displayed results were calculated. Support correspondence is used to answer the request and administer the application.
Google user data is not sold or used for unrelated advertising profiles, third-party surveillance or training generalized artificial-intelligence models. It is not published in the buying guides or disclosed to other advertisers as a data product.
Storage, retention and security
The current application stores imported reports, research records and history in local files and a local database on the operator’s computer. Its management interface is served on the local loopback address. The public website contains informational pages and static assets, not the management database or private reports.
Local report records and import history remain until the operator deletes the relevant records or files; the current application has no automatic retention expiry. Copies the operator exports or backs up must also be considered when handling a deletion request. Access to the computer, local application and any backups must be restricted to authorized personnel. No method of storage or transmission can be guaranteed completely secure.
Sharing and service providers
Advertising records are intended for the operator and explicitly authorized personnel working on the relevant accounts. When a Google connection is enabled, requests are transmitted to Google to perform authorized functions. Private advertising reports are not sent to Cloudflare as part of these public informational pages.
Cloudflare hosts these public pages and may process ordinary technical request information to deliver and protect the website. Application support email is processed by the email service for the support address. Information may also be disclosed when necessary to comply with applicable legal obligations or address abuse. The application will not expand sharing or data uses without updating the relevant disclosures and obtaining authorization when required.
Limited Use
Affiliate Ads Manager’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable.
Access, correction, revocation and deletion
Contact [email protected] to request access, correction or deletion of application records relating to an account you own or manage. Identify the relevant advertising account and the requested action; do not send passwords or access tokens. The operator may ask for information needed to verify your authority over that account.
When a Google OAuth connection is in use, you can review and remove its access from your Google Account connections. Removing authorization prevents further authorized access but does not automatically erase reports already stored locally. Request deletion of retained records separately, including relevant operator-controlled exports or backups. Requests will be handled subject to applicable retention obligations.
Changes
This notice will be updated as the application develops. Material changes to Google data access, use, storage or sharing will be disclosed before the new practices take effect, with renewed authorization where required. The date above identifies this version.