ABU · Agentic Business Units
ABU privacy policy — Fundraising For Nonprofits
How ABU accesses, uses, stores and shares connected Google account data, and how to request its removal.
Scope and responsible operator
Effective date: 29 September 2026. This notice describes connected Google data processed by ABU by Fundraising For Nonprofits. The responsible operator is Roman Buznykovatyy, Seebrucker Str. 2a, 81825 Munich, Germany. Contact: [email protected].
For client account operations, our role and instructions are also defined by the client service and data-processing arrangements. This application-specific notice supplements F4N's general privacy and cookie policies. The narrower purpose and use limits in this notice apply to connected Google data; general descriptions of advertising or other services do not expand these permissions.
Address correction confirmed on 29 September 2026: the current postal address of the responsible operator is Seebrucker Str. 2a, 81825 Munich, Germany. This supersedes the street number printed in the linked general privacy and cookie policy PDFs dated 16 March 2026. Those documents remain available as historical policy documents; this correction does not change their other provisions.
Data we access
For authorized Google Ads operations, we access the account and manager identifiers, account settings, campaigns, ad groups, ads, keywords, budgets, bidding settings, assets, conversion configuration and performance measurements needed for the requested service. The exact data depends on the granted account permissions and the operation. Keyword planning uses submitted research criteria and the ideas, historical measurements and forecasts returned by Google.
We also process authorization credentials or service-account credentials used to obtain permitted access, plus operational records such as request identifiers, action receipts, errors and connection status. Credentials are handled by the backend and are not published in reports or these public pages.
This Google Ads connection does not by itself grant access to a person's Gmail mailbox, Google Drive files or private contacts. Separate services require their own permissions and disclosures. Data categories listed in the general F4N policy do not mean every category is collected through this connection.
Why and how we use connected data
We use connected Google data to provide the account owner's requested advertising service: reporting, analysis, campaign planning, authorized campaign changes, verification of outcomes, troubleshooting and protection of the connection. AI-assisted processing may summarize the relevant account information and prepare recommendations for an authorized operator.
We do not sell connected Google user data, use it to build unrelated contact databases, or use it to train or improve general-purpose AI models. We do not use one client's identifiable account data to market to another client's donors or to enrich unrelated prospect lists. Receiving advertising-account data is not permission to upload arbitrary third-party personal contacts into advertising audiences.
ABU's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including applicable Limited Use requirements.
Storage, access and service providers
Our backend uses Cloudflare services for application execution, protected credential storage, access control and operational data storage. Depending on the requested workflow, necessary data may also be processed in the authorized F4N business workspace and by configured AI service providers, including OpenAI. Data is shared only as necessary to operate the requested service under the applicable service and data-processing terms, not for the provider's independent advertising purposes.
Authorized operators may access account data as needed to provide or troubleshoot the service. Access is restricted to the appropriate accounts and projects. We use encrypted network connections and protected backend credentials. No security certification or absolute security guarantee is implied by this notice.
Processing may take place in the European Economic Area and in other countries where our service providers operate, including the United States. Applicable transfer safeguards and service-provider arrangements apply; further information can be requested using the contact address above.
Retention and removal
We retain connected data only for the service purpose for which it is needed, including necessary operational records, and for applicable legal obligations. The retention criteria are the duration of the authorized service, whether a record is still needed for the requested work or its verification, and any applicable legal retention requirement. We do not claim that all stored copies disappear automatically when access is revoked.
Removing Google's account permission prevents subsequent use of that permission. To request disconnection and deletion of retained copies, email [email protected] and identify the account or service concerned; do not send passwords or API keys. We will verify the requester's authority and delete data that is no longer needed or legally required. Any justified exception, including a legal retention requirement or a backup still awaiting normal expiry, will be explained in the response.
Your choices and rights
You can request information about your data, access, correction, deletion, restriction or portability where applicable, and object to processing or withdraw consent where consent is the basis. A client administrator can remove the authorized Google Ads user or service account. If an OAuth connection is used, it can be revoked through the Google account's third-party connections controls.
Processing for our own support and service administration relies on the applicable contract, consent where required, legitimate operational interests or legal obligations. Processing on behalf of a client follows that client's documented instructions and applicable arrangements. You may contact us for the basis relevant to your request and may lodge a complaint with the competent supervisory authority.
Cookies and public pages
These public ABU information pages do not themselves initiate Google Ads authorization or include advertising tags in their page source. Hosting, security and website analytics services may process technical visit data as described in F4N's general privacy and cookie policies. The application pages are publicly readable without a Google login.
Changes and contact
We update this notice when the application's data practices materially change. The current version and date are shown on this page. Questions and data requests: [email protected].