Ambition logo
Ambition AI
PlatformTeamHow it worksResultsFAQ
Log inTry 1 month freeTry free

Home · Data processing agreement

Legal

Data Processing Agreement

How Ambition processes personal data in the accounts a client connects to Ambition AI, including managing the client's ad accounts on its instructions, as required by Article 28 of the GDPR.

Version 1.2Effective 13 November 2026

The short version

  • The client decides what happens to its data (controller). We process it only to run Ambition AI and the client's campaigns for that client (processor).
  • We read ad results, change history, daily sales totals and product and stock data. Depending on the features in use and the permissions the client grants, we manage the client's own ad accounts on its instructions: ads, creatives, campaigns, audiences, budgets, bids and keywords. A senior specialist approves new ads before they go live and reviews the AI's optimisations, and every change is logged.
  • We don't store shop customers' details, and we never use one client's personal data for another client.
  • Everything is stored in the EU, with AWS in Frankfurt. Our sub-processors are AWS and our two developers, who can reach the data from the Philippines to maintain the platform, under the EU Standard Contractual Clauses (sections 9 and 10).
  • We tell you within 48 hours of a personal data breach, and delete your data within 30 days when you disconnect or leave.
Contents
  1. Parties and roles
  2. What we process and why
  3. How we access the client's accounts
  4. Data per platform and changes we make
  5. Instructions and approvals
  6. The client's responsibilities
  7. Confidentiality
  8. Security measures
  9. Sub-processors
  10. Where data is processed
  11. Rules per platform
  12. Helping the client
  13. Personal data breaches
  14. Deletion and return
  15. Information and audits
  16. Liability and precedence
  17. Changes and versions
  18. Contact

1. Parties and roles

This agreement is between Ambition Agency B.V. (KvK 99931052), Spoorstraat 11 A, 1211 EZ Hilversum, the Netherlands ("Ambition", "we"), and the client that accepts the Ambition AI Terms of Service ("the client"). It is part of those terms, and the client accepts it by ticking the box when connecting an account.

For personal data in the accounts the client connects, and in the material the client gives us for its ads, the client is the controller and Ambition is the processor, as defined in the EU General Data Protection Regulation (GDPR). For Ambition AI logins and our website, Ambition is the controller; the privacy policy covers that.

Google, Meta, Microsoft, Shopify and Adobe (Magento) are not our sub-processors. They provide the client's own accounts under the client's own agreements with them, and their terms keep applying to those accounts. When we publish an ad, upload a creative or update an audience in a client's account on the client's instructions, we act as the client's processor, and the client's agreement with that platform governs what the platform does with that data.

2. What we process and why

  • Subject matter: personal data in the advertising and shop accounts the client connects, in the client's ad accounts where Ambition team members work directly with access the client gives them, and in the material the client gives us to make its ads, such as product information, customer reviews, photos and videos.
  • Nature: reading data through the platforms' APIs; storing, combining, analysing and displaying it; preparing proposals and ads with Ambition AI; managing the client's ad accounts as described in section 4; and deleting the data.
  • Purpose: providing Ambition AI and running the client's campaigns: reporting dashboards that combine ad spend, sales and stock, comparing results with targets, explaining what changed in an account, importing the client's products into the Brand Brain, writing and checking ads, managing budgets, and managing the client's ad accounts as the client authorizes under the Terms of Service. Nothing else.
  • Duration: while the account is connected and the client's service agreement runs, plus the deletion period in section 14.
  • Data subjects:
    • people who use or make changes in the client's ad accounts (the client's staff, agencies and other account users);
    • the client's Ambition AI users;
    • the client's shop customers, whose orders we read to calculate daily sales totals, without storing their details;
    • people who appear in or are named in the client's ads, creatives, product photos and customer reviews, such as models, creators, founders and reviewers;
    • people searching online, where a search term that triggered the client's ad contains personal data.
  • Types of personal data: names, email addresses and user names of account users; shop customers' order data, which we don't store; names, images and voices of people in ads, creatives, product photos and reviews; and search terms.

We do not sell data, share it with data brokers or other advertisers, use it to advertise for anyone other than the client, or use it to train AI models. Personal data from one client is never combined with other clients' data or used for another client.

No special categories of personal data, such as health data, are processed. We do not build profiles of individuals, make eligibility decisions about people, or try to re-identify anyone, and we make no automated decisions about individuals that have legal or similarly significant effects on them.

3. How we access the client's accounts

We only access accounts the client connects, only through the access the client grants, and only with the permissions shown on the platform's own screen:

  • Google Ads, Meta Ads and Microsoft Advertising: a user signs in with their own account on the platform's sign-in screen (Google, Facebook Login or Microsoft) and approves Ambition AI's access. We receive a login token, never the password.
  • Shopify: the client installs the Ambition AI app from Shopify and approves the permissions Shopify shows, which are limited to reading orders, products and inventory.
  • Magento (Adobe Commerce): the client creates an integration in its Magento admin with the permissions in our setup guide, switches on the store setting for integration tokens, and gives us the access token. The Terms of Service explain what that setting means.

The user who connects an account confirms that the client may grant this access. We use it only for the purposes in section 2, and not to access other services from these providers, such as Gmail, Google Drive or a Facebook profile. The client can withdraw access at any time by disconnecting in Ambition AI, which deletes our login token at once, and on the platform's side, as the privacy policy explains. A Magento token only stops working when the client deletes the integration in Magento.

4. Data per platform and changes we make

What we read and keep per platform; personal data in bold
PlatformWhat we read and keep
Google AdsAccount IDs; campaign names and IDs; daily impressions, clicks, cost, conversions and conversion value; change history for campaigns, ad groups, ads and keywords, including the email address of the person who made each change.
Meta AdsAd account IDs; campaign names and IDs; daily impressions, clicks, spend, conversions and conversion value; the names and IDs of the Facebook Pages and Instagram accounts the client advertises with, to publish ads in their name; change history, including the name of the person who made each change.
Microsoft AdvertisingAccount IDs; campaign names and IDs; daily impressions, clicks, spend, conversions and conversion value; change history, including the user name or email address of the person who made each change.
ShopifyOrders: daily totals only (number of orders, gross sales, discounts, refunds and net sales), plus the shop's time zone and currency. We read orders to calculate them, without customer names, email addresses, phone numbers or addresses, and store only the totals. Products and inventory: product titles, descriptions, images, variants, prices, SKUs and stock levels, for the dashboard and the Brand Brain product import. Product and stock data is not personal data; product photos can show models (section 2).
Magento (Adobe Commerce)Daily totals only, as for Shopify. Magento's API returns complete orders, including customer names, email addresses and addresses; we use only the order amounts, in memory, and never store customer details.

In the ad accounts we manage, we also read and keep the settings of campaigns, ad groups, ad sets and ads; ad copy, images and videos; keywords and the search terms that triggered the client's ads, which can occasionally contain personal data; budgets, bids and bid strategies; and targeting settings and audiences, including their names and settings but not the people in them.

For every platform we also keep the account IDs we can access, the permissions granted, an encrypted login token, and the log of changes we make (section 5). We add other platforms only with a new version of this agreement, and before any connection starts keeping personal data not listed here, we also publish a new version. Each time, we ask the client to accept it.

Changes we make in ad accounts

Depending on the features in use and the permissions the client grants, Ambition AI and the Ambition team manage the client's connected Google Ads, Meta Ads and Microsoft Advertising accounts on its instructions, as the client authorizes under section 5 of the Terms of Service. This covers:

  • creating, editing and publishing ads and ad copy, and uploading images and videos;
  • creating, changing, publishing, pausing, re-enabling and removing campaigns, ad groups, ad sets and ads;
  • setting and moving budgets, and changing bids and bid strategies;
  • adjusting targeting and schedules, such as locations, devices and times of day;
  • creating and changing audiences built from the platform's own data, such as interest, lookalike, website-visitor and engagement audiences, and using them in targeting;
  • adding, changing and removing keywords and negative keywords, and excluding search terms.

We don't change an account's payment settings, its users or their access rights, and we don't close the account. We do not upload customer lists or other personal data about the client's customers to ad platforms. We make no changes in the client's shop: for Shopify we only read orders, products and inventory, and for Magento only orders. Ads, creatives and settings we create stay in the client's own accounts and belong to the client, also after the client disconnects or leaves.

5. Instructions and approvals

We process the client's personal data only on the client's documented instructions. These are the terms, this agreement, the client's service agreement with Ambition, the goals and budgets agreed with the client, the client's settings and approvals in Ambition AI, and written instructions from the client's authorized users, for example by email or in Ambition AI. An authorization to make a change in an ad account also covers the personal data that change involves.

New ads and ad copy are approved by a senior Ambition specialist before they go live. Routine optimisations within the goals and budgets agreed with the client, such as moving budget, changing bids, pausing ads that lose money and excluding search terms, can be made by Ambition AI around the clock, and our senior specialists review them. Where the client has asked to approve certain changes itself, such as new ads or a higher budget, we wait for its approval. The client can tell us at any time to stop making changes, or to make them only with its own approval, and we follow that.

Every change made through Ambition AI is logged with what changed, when, who or what made it (Ambition AI or a named Ambition specialist) and the reason. The client sees these changes in Ambition AI.

The client instructs us that the Ambition team members who work on its account may view its data, including data received from Google APIs, to provide the services, and that our developers may do so where needed to maintain the platform, fix problems or keep it secure.

If an instruction would, in our view, break the GDPR or other data protection law, we tell the client and do not follow it. We also don't carry out an instruction that would break a connected platform's terms or advertising policies, and we tell the client why. If the law requires us to process data otherwise, we tell the client first unless the law forbids that.

6. The client's responsibilities

As controller, the client:

  • makes sure it may connect each account and have us process the data in it, and that its instructions comply with the GDPR;
  • has a legal basis, and any consent needed, for the names, images and voices of people in the ads, creatives and reviews it gives us or approves;
  • does not give us special categories of personal data or data of children, and does not ask us to target people on that basis;
  • keeps to the terms and advertising policies of each platform it connects, including its own duties as advertiser, such as a privacy notice on its landing pages and consent for tracking where the law requires it;
  • keeps the list of users who can give us instructions up to date.

7. Confidentiality

Everyone at Ambition who can access the client's data is bound to confidentiality. Only the Ambition team members who work on the client's account see its data, and only to do that work; our developers can reach it only where needed to maintain the platform, fix problems or keep it secure. This obligation continues after the relationship ends.

8. Security measures

  • Encryption: login tokens for connected accounts are encrypted with a key unique to each client, protected by AWS Key Management Service. All traffic uses HTTPS.
  • Client isolation: the database separates clients at the database level, so one client's data can't appear in another client's results.
  • Access control: every user has a personal login; two-factor authentication is available for every login; passwords are stored only as one-way hashes.
  • Least privilege: we ask each platform only for the permissions Ambition AI uses; Ambition's client teams see only the clients they work on, and developers reach client data only where their work needs it.
  • Audit logs: signing in, connecting, syncing and disconnecting accounts are logged with who did it and when. Every change we make in a connected account is logged as described in section 5.
  • Data minimization: shop customer details are never stored (section 4).
  • Backups: database backups roll over within 7 days.

9. Sub-processors

The client gives general written authorization for us to use the sub-processors listed here. Each one is bound by data protection terms at least as strict as this agreement, and we remain fully responsible to the client for how they process its data. The AI in Ambition AI runs on AWS, and no other AI service receives the client's data. Before any other service processes the client's personal data, including an AI service, we add it to this list as described below.

Current sub-processors
Sub-processorWhat it doesLocation
Amazon Web Services EMEA SARLHosting of the platform, database, file storage and encryption keysFrankfurt, Germany (eu-central-1)
Two independent software developers (contractors)Building, maintaining and supporting Ambition AI, with remote access to client data only where their work needs itThe Philippines (remote access; the data stays in Frankfurt)

We tell clients at least 30 days before adding or replacing a sub-processor, by email and by updating this page. A client can object on reasonable data protection grounds within that period. If we can't resolve the objection, the client may stop using Ambition AI without penalty.

10. Where data is processed

All platform data is stored in the EU, in AWS's Frankfurt region, and Ambition AI runs there. Our web pages are delivered through AWS CloudFront's global network, but the database, login tokens and processing stay in Frankfurt.

The developers who build and maintain Ambition AI work from the Philippines. They can reach the client's data remotely, only where needed to maintain the platform, fix problems or keep it secure; the data itself stays stored in Frankfurt. This access counts as a transfer of personal data outside the European Economic Area, which we cover with the EU Standard Contractual Clauses signed with each developer. Apart from this, we do not transfer the client's personal data outside the European Economic Area.

What we publish or upload in the client's ad accounts is processed by that platform under the client's own agreement with it (section 1), which may include transfers outside the European Economic Area. If we ever need any other transfer of the client's personal data outside the European Economic Area, we tell the client in advance, as for a new sub-processor, and use a lawful transfer mechanism such as the EU Standard Contractual Clauses.

11. Rules per platform

Each platform sets its own rules for apps that use its data. We follow them for that platform's data, also where they are stricter than this agreement, and we report a security incident to a platform where its terms require it.

  • Google Ads: our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. This agreement is the written contract with the client that the Google Ads API terms require. If the client asks us to end our access to its Google Ads account, we do so within 3 business days, and the client keeps full control of the account.
  • Meta Ads: we process data from Meta only on behalf of and at the direction of the client, keep each client's data separate, and never use one advertiser's data for another. We delete it when the client disconnects, when we no longer need it, or promptly when Meta or the person concerned asks (see deleting your data). Meta may ask us for the list of clients whose Meta data we process, with a contact person for each, and we give it when asked.
  • Microsoft Advertising: Microsoft offers one permission (msads.manage) that allows both reading and changes. We use it only as section 4 describes, request only the data we need, and delete or return Microsoft data when the client ends our access.
  • Shopify: we follow Shopify's protected customer data requirements. The app only reads orders, products and inventory, never makes changes in the shop, and never receives customer names, email addresses, phone numbers or addresses. This agreement is the data protection agreement Shopify requires us to have with each merchant. We act on Shopify's customer data requests, customer redaction requests and shop redaction requests within 30 days, do not use Shopify data to train AI models, and report a breach affecting Shopify data to Shopify within 24 hours.
  • Magento (Adobe Commerce): Magento has no app review or developer terms for this kind of connection. The client creates the integration and its token in its own shop; the token does not expire, and the store setting it needs applies to every integration in the shop, as the Terms of Service explain. Only deleting the integration in Magento ends our access.

12. Helping the client

We help the client, as far as we reasonably can, to:

  • answer requests from data subjects to see, correct, delete or export their data, including requests that reach us through a platform, such as a Shopify customer data request or a Meta data deletion request. If a request reaches us directly, we pass it to the client without undue delay and do not answer it ourselves;
  • keep the processing secure and meet its own duties after a personal data breach (section 13);
  • carry out a data protection impact assessment or consult a supervisory authority, where the client needs one.

13. Personal data breaches

If we become aware of a breach affecting the client's personal data, we tell the client without undue delay and within 48 hours. We share what we know: what happened, which data and people are likely affected, the likely consequences, and what we are doing about it, and we add details as we learn them. We take immediate steps to contain the breach and help the client meet its own duty to notify. Where a platform's terms require it, we also report the breach to that platform.

14. Deletion and return

  • Login tokens are deleted immediately when an account is disconnected.
  • If the client asks us to disconnect an account or end our access, we do so within 3 business days.
  • We delete the client's data from connected accounts within 30 days of a disconnect, the end of the client's service agreement, or a written request. It leaves our backups within 7 days after that.
  • Our copies of the client's ads, ad copy and creatives, the material the client gave us, and the change log are deleted within 30 days of the end of the client's service agreement or a written request, and leave our backups within 7 days after that.
  • When a shop uninstalls the Shopify app, Shopify asks us to delete that shop's data, and we do so within 30 days.
  • Ads, creatives and settings in the client's own ad accounts are not deleted: they stay the client's (section 4).
  • Before deletion, the client can ask for an export of its data in a machine-readable format, including the change log.
  • We keep data longer only where the law requires it, and tell the client if so.

15. Information and audits

On request, we give the client the information it needs to show that this agreement is being complied with. The client, or an independent auditor bound to confidentiality, may audit our compliance, including by inspection, once a year, or after a breach, with at least 30 days' notice and during business hours. Each party bears its own costs.

16. Liability and precedence

Liability under this agreement follows the Terms of Service, except where the GDPR does not allow a limit. On anything to do with personal data, this agreement wins over the terms and the client's service agreement.

17. Changes and versions

Each version of this agreement has a number and an effective date at the top of this page. The platform records which version the client accepted and asks again when it changes. A new version applies to a client once the client accepts it; until then, the version the client accepted last keeps applying. We make changes in a client's ad accounts through Ambition AI only after the client has accepted version 1.1 or later.

  • 13 November 2026: version 1.2. Covers managing the client's ad accounts on its instructions, depending on the features in use and the permissions the client grants, including publishing ads and creating audiences from the platform's own data; the Facebook Pages and Instagram accounts used for Meta ads; and reading Shopify products and inventory for the dashboard and the Brand Brain product import.
  • 10 November 2026: version 1.1. Covers the changes we make in connected ad accounts and how they are approved and logged, the extra ad data we read, how we access accounts, the client's responsibilities, rules per platform, our developers in the Philippines as sub-processors under the EU Standard Contractual Clauses, our responsibility for sub-processors, and transfers.
  • 22 October 2026: version 1.0, first public version, covering Google Ads, Meta Ads, Microsoft Advertising, Shopify and Magento.

18. Contact

Questions about this agreement, data requests and breach contacts: alex@ambition-agency.nl.

Ambition Agency B.V.
Spoorstraat 11 A
1211 EZ Hilversum
the Netherlands
KvK (Dutch Chamber of Commerce) number: 99931052

Ambition logo

Ambition AI

AI platform and senior marketing team for e-commerce brands. Same ad spend, more sales.

© 2026 Ambition · Hilversum, NL · Privacy · Terms · DPA

Platform

What's inside and what it costs.

PlatformTeamHow it worksLog inResultsFAQ

Guides

What we learned running ads for 75+ brands.

What is a good ROAS for an e-commerce brand?How to split your ad budget between Google and MetaCreative fatigue: how often do you need new ads?How to pick an offer that drives repeat purchases

Contact

Talk to a real person.

Try 1 month freeambition-agency.nlLinkedInalex@ambition-agency.nl