Privacy Policy

This policy explains what AdsFlow Manager does with information obtained from Google APIs. It is written for the reviewers of our Google Ads API and OAuth access, and for the members of our own team who authorise the application. It describes the way the application actually handles data rather than a hypothetical service.

1. Who we are

AdsFlow Manager is an internal software application operated by the AdsFlow Manager team, the advertising operations team that owns the Google Ads accounts the application connects to. This website is published at adsflow.beautyedithub.com, and questions about this policy can be sent to [email protected].

The application is not a public service. It is used only to manage advertising on Google Ads accounts that our organisation owns. It is not offered, sold or licensed to anybody else, and no third party can create an account on it.

2. Scope of this policy

This policy covers two things:

• the AdsFlow Manager application, and the Google Ads data it reads or changes after a member of our team authorises it; and
• the information-only website published at adsflow.beautyedithub.com.

It does not describe Google's own handling of data. Google's practices are set out in theGoogle Privacy Policy.

3. Information we access through Google

Access begins only when a member of our team signs in with a Google Account that already has access to our Google Ads manager account and grants the application authorisation on Google's OAuth 2.0 consent screen. The application requests the Google Ads API scopehttps://www.googleapis.com/auth/adwords from the Google Cloud projectGoogle Ads Automation AD.

With that authorisation, the application accesses the following for accounts we manage:

• Account structure data, such as the manager account, the client accounts linked to it, campaigns, ad groups, ads, keywords, budgets and bidding settings.
• Advertising status and performance data, such as the serving status of campaigns, ad groups and ads, and daily cost, click and conversion figures.
• Change history for the accounts we manage, so that our team can see what was modified and by which staff account.
• The authorising user's identity, such as the Google Account email address of the person who granted access, used to attribute each action to a person rather than to an anonymous session.
• OAuth 2.0 authorisation credentials for the authorising account, which the application needs in order to call the Google Ads API on our behalf.

The application is limited to the Google Ads accounts our organisation owns and the client accounts linked to them. It does not request or receive access to any other advertiser's account, and it does not request access to Gmail, Google Drive, Calendar or any other Google service.

4. How we use the information

Information obtained through the Google Ads API is used only to:

• operate, monitor and report on advertising campaigns that our organisation runs;
• create, edit, pause, resume and retire campaigns, ad groups, ads and budgets in our own accounts;
• maintain final URL suffixes, tracking parameters and tracking links for the campaigns we select;
• keep an internal record of the changes the application performs and their outcome;
• diagnose faults and maintain the security of the application.

5. Google API Services User Data Policy and Limited Use

In particular, information received from Google APIs is used only to provide and improve the features of the application described on this website, and for no other purpose. It is not transferred to third parties except where that is necessary for security purposes, to comply with applicable law, or as part of a merger or acquisition approved under Google's policy. It is never used for serving advertisements, and it is never used for advertising, profiling or credit assessment. No person reads Google Ads data except where that is necessary for security, required by law, or done with the consent of the account holder.

6. Information we do not collect or share

We do not:

• sell, rent, trade or otherwise share Google Ads data or personal information with third parties for their own purposes;
• use Google Ads data to target advertising at individuals, to build profiles, or to assess creditworthiness;
• allow advertisers, data brokers or analytics services to receive data from the application or from this website;
• collect information from visitors to this website. There is no sign-up, no login form and no data submission of any kind on these pages.

7. Where the information is stored

The application stores the minimum it needs in order to operate:

• Our own workspace. Account configuration, the advertising task queue, tracking-link history, imported performance figures and the archive of finished records live in a spreadsheet workspace inside the Google account our organisation controls.
• Our own infrastructure. The automation service that processes the queue runs on a machine our organisation controls. It keeps lock files, working files and operational logs in its own local data directory on that machine.
• Application credentials. The authorisation credentials and the service-account key file that the service uses to reach our workspace are kept in local configuration files on our own machine. They are never published on this website, never committed to the source repository of this website, and never displayed in any interface.

Nothing about the application's data is hosted by this website. The site you are reading is a set of static pages that contain no application data, no database and no login.

8. How long we keep it

Records are kept only for as long as they are needed for the purposes described in this policy:

• High-volume operational records, such as tracking-link rotation history, are held online for a short working window (of the order of a week, by working day) and are then archived. The detailed rows are cleared only after the archive and its integrity check have completed successfully.
• Advertising tasks are archived once their outcome is final. Tasks that ended in an unresolved or failed state are held for a short verification window, of the order of a week, before being archived.
• Imported performance figures are kept as a rolling daily history that is used for reporting on our own campaigns.

A request to delete stored advertising data can be sent to[email protected]. We will act on it promptly, subject to any record-keeping obligation that applies to us. When a member of our team revokes the application's authorisation in their Google Account, the credentials we hold for that account stop working and are removed from our systems.

9. Service providers and third parties

The application and this website rely on the following third-party services:

• Google. The Google Ads API and the OAuth 2.0 authorisation flow, the Google Ads and Google Ads Scripts environment in which advertising changes are executed, and the Google Workspace account that hosts our workspace.
• Cloudflare. Hosting and DNS for the website at adsflow.beautyedithub.com, including the platform-level features described in section 12.
• Affiliate networks. Order and revenue statistics are imported from the affiliate networks our organisation holds accounts with. These imports are inbound only: the application reads our own affiliate account data, and no Google Ads API data is sent to those networks.
• A commercial proxy provider. When the application checks that a tracking link and its redirect chain resolve before use, the outbound request may be routed through a third-party proxy service. Those requests contain the public landing-page address being checked and technical request metadata, and no Google Ads account data.

Apart from the services listed here, information received from Google APIs is not transferred to any third party, as described in section 5.

10. Security

Access to the application is restricted to authorised members of our team. Traffic between this website, the application and Google's APIs is carried over HTTPS. Credentials are held in local configuration files that are excluded from source control, actions performed through the Google Ads API are recorded with their outcome, and access is removed when a person leaves the team or no longer needs it.

No method of transmission or storage is completely secure, but we take these measures to protect the data our organisation is responsible for, and we review them as the application changes.

11. Revoking access and your choices

A person who has authorised the application can withdraw that authorisation at any time from the Google Account permissions page atmyaccount.google.com/permissions. Removing the application there ends its ability to reach the associated Google Ads data. Access can also be ended by removing the person's access to the Google Ads account, or by contacting us at [email protected].

12. This website, cookies and analytics

The website at adsflow.beautyedithub.com is a static information site with three pages. We have added no sign-up, no login, no comment feature, no advertising tag and no analytics of our own to it. The pages set no cookies of ours, and there is no form anywhere on the site that collects information from a visitor.

The site is delivered through Cloudflare, which is also the provider of our DNS. Cloudflare applies platform-level features to pages on our domain on our behalf: a cookie-less web analytics beacon that records aggregate page views and performance data, and an email address rewrite that keeps published addresses away from automated address harvesters. As a hosting and security provider, Cloudflare also processes request metadata such as IP address, user agent and response timing in order to deliver and protect the site. That processing is described in Cloudflare's ownprivacy policy.

Apart from links to the Google and Cloudflare policy pages mentioned in this document, the site contains no external content.

13. Children

AdsFlow Manager is an internal business tool for advertising professionals and is not directed to children. We do not knowingly collect information from children through this application or this website.

14. Changes to this policy

We update this policy when the application or our practices change. The revision date at the top of the page always shows the current version, and material changes are reflected here before they take effect.

15. Contact

For any question about this policy, about the data the application holds, or about a deletion request, write to[email protected].