AAMS privacy and Google Ads data notice
Effective date: 2026-11-05
This notice applies to AAMS — Automated Advertising Management System. Aurora Vector International Limited, Hong Kong (we, us), operates the application and is responsible for its related Google Ads data processing. The application is available at https://smartlinkmanager.org/.
1. Scope
This notice covers AAMS account connections, advertising operations, synchronization, reporting and related support. General enquiries submitted to Aurora's corporate website remain covered by that website's privacy policy. This notice describes AAMS specifically. Using AAMS does not change the advertiser's identity or the ownership of an advertising account.
2. Data accessed and stored
Depending on the permissions granted and features used, AAMS may process manager and client account identifiers, names, currencies, time zones and status; campaigns, ad groups, keywords, assets, landing pages, budget and bidding settings; impressions, clicks, spend, conversions and conversion value; and accessible budget, billing and verification status summaries.
AAMS also handles the OAuth authorization or service account connection information needed for existing connections, together with workspace users and operation and synchronization status. The categories processed depend on the connection permissions and enabled features; not every account supplies all categories.
3. Purposes
Data supports authorized account management, ad preparation and changes, keyword planning, reports, spend and budget reconciliation, operational monitoring, troubleshooting and support. Use is limited to these disclosed application functions and the user's authorization.
We handle Google API data in accordance with the Google API Services User Data Policy and applicable Limited Use requirements. Google account data must not be used for undisclosed, unrelated purposes.
4. External services and transfers
AAMS communicates with the Google Ads API to carry out authorized reads and changes. The hosting, database and backup infrastructure used by the application may also process relevant data.
When a configured external AI asset feature is used, its task inputs are sent to the selected service endpoint to generate or revise assets. These inputs can include keywords, brands and domains, target country and language, landing-page summaries, ad content and user-entered prompts. The service depends on the configuration, and its handling of task inputs is subject to the applicable service and data-processing terms. Do not enter account credentials or unrelated private information into prompts.
Where a task involves a client or another third-party advertiser, use and transfer of that advertiser’s data must remain within its granted management and data-processing authority. Advertising account management access does not by itself authorize sending the advertiser’s non-public data to an external AI service. The operator and application user must first establish that the relevant mandate, data-processing arrangements and provider terms permit the particular transfer. Without that authority, the advertiser’s non-public data should not be entered into external AI features. These checks are the responsibility of the operator and application user; this notice does not represent AAMS as having an additional automated consent or transfer-blocking mechanism.
Authorized users may also export data for their workflows. Infrastructure and external services may process data outside Hong Kong. New data purposes or expanded sharing require updated disclosure and appropriate authorization first.
5. Storage and access controls
AAMS stores synchronized account data, reporting history and operational settings in its application database. Workspace access is protected by sign-in and roles, and the credential-handling workflows use encryption for connection information. The application also handles sign-in sessions, interface preferences, and technical records needed for operation and security.
6. Retention and deletion
Retention is assessed against the disclosed functions, operational reconciliation and applicable obligations. Removing an AAMS connection clears its local authorization credentials and disables the connection. Previously synchronized account and reporting history may remain and is not automatically deleted in full by disconnection.
To ask about retention or request local data deletion, email info@auroravector.com with the relevant workspace or account and the requested scope. We will verify the requester's identity and authority and explain the scope that can be handled and any information that must remain. Revoking Google authorization, removing an AAMS connection and deleting local history are separate actions.
7. Disconnecting and revoking access
A workspace administrator can remove the relevant connection in AAMS. OAuth users can also revoke the application's authorization through their Google Account third-party access settings. For a service account connection, the relevant Google Ads administrator can remove that service account's access to the advertising account.
Stopping further Google access does not automatically delete previously synchronized local history. Contact us separately about that history. Do not send passwords, authorization tokens, private keys or complete credentials by email.
8. Contact and updates
For application support, developer contact and data-handling enquiries: Aurora Vector International Limited, Hong Kong; info@auroravector.com.
We update this notice when data-handling practices materially change. Additional purposes or permissions will be explained and authorized as required.