Privacy policy

Last updated: 1 October 2026

Who is responsible

AthillyAds is operated by Ampthilly AB, organisationsnummer 559588-0724, with registered office at Bjännberg 121, 905 72 Hörnefors, Sweden. For everything described on this page, Ampthilly AB is the data controller, except for the business content you put into the platform (your pages, campaigns, product feeds), which we process on your instructions, as a processor. Privacy questions go to hello@athillyads.com.

This website

The marketing site you're reading loads no analytics or advertising script until you allow the matching cookie category. Those scripts are not requested before permission. Declining leaves those tracking services off. You can change your choice using Cookie settings in the footer. The support chat described below connects after you allow Chat in cookie choices or choose to open it, separately from analytics and advertising.

Our hosting provider (Cloudflare) processes standard technical request data (IP address, user agent) to serve pages and protect against abuse, as every host does.

Cookies this site can set

Cloudflare's own cookie documentation describes its cookies. Turning off Analytics or Marketing removes the matching tracking cookies accessible to this website and reloads the page when a previously allowed category is withdrawn.

If you allow Chat or open the chat, tawk.to may use cookies or browser storage to keep the conversation working. See the Support chat section below for when it connects and what it receives.

Cookie choices

Support chat

If you allow Chat in cookie choices, we load tawk.to in the background to prepare the connection to our team. You can also start it by opening the support chat. The chat service receives technical connection details, including your IP address and the page you visit, and the messages and contact details you choose to submit. It may use cookies or browser storage to keep the conversation working. No tawk.to resources are requested before you allow Chat or choose to open it. After opening the chat, that choice is remembered for the same browser tab session so it can reconnect on another page.

We use the conversation to answer your enquiry. If you leave an email address, our team can reply after you have left the website. We do not send your chat messages to our analytics or advertising tools. Read tawk.to's privacy policy for information about its processing, including processing in the United States. Contact hello@athillyads.com about your conversation or to request deletion.

The free hint generator

When you use the context hint generator, the page URL you submit (and any optional business context you type in) is sent to our API, which fetches that page and generates the result. We keep a log of these requests: the URL, the context fields, the generated response, and technical details like timing. This log is what lets us find and fix pages the tool handles badly.

The result includes a picture and an icon taken from that page. We don't store the images themselves: resized copies are made when the preview or Ads Manager asks for them, served from app.athillyads.com and cached for about a week. The request log records which images were chosen.

Your IP address is used for rate limiting and stored only in hashed form, and those hashes are deleted after 90 days. The tool is protected by Cloudflare Turnstile, which may set a functional cookie strictly to tell humans from bots; it does not track you across sites.

The AthillyAds platform

When you create an account at app.athillyads.com, we store what the service needs to work: your email and name, your organization and team members, the websites and pages you connect, the content we read from them, the brand books, campaigns and ads we generate, and (if you connect one) your ChatGPT Ads API key, which is encrypted and never leaves our backend. If you connect Google Analytics, we also keep figures read from it, as described below.

Images from your website are only collected and stored if you explicitly confirm the site is yours and grant permission, and that permission can be withdrawn in Settings, which deletes every image we collected.

Google sign-in and Google Analytics

Signing in with Google. If you sign in to app.athillyads.com with your Google account, Google gives us your name, email address and profile picture. We use them to create your account and sign you in, and for nothing else.

Connecting Google Analytics. Separately, you can connect a Google Analytics 4 property to an ad account. You sign in with Google and give us read-only access to Google Analytics (analytics.readonly), plus the email address of the Google account you used, so the app can show which account is connected. We cannot change anything in your Google Analytics.

With that access we:

• list the Google Analytics accounts and properties you can see, so you can pick the one that belongs to the ad account. The list is not stored;
• store the property you pick: its name and ID, its measurement ID, its website address and its currency;
• read reports from it: a year back when you connect, then the last seven days every night. They are daily and weekly totals: visits, engaged visits, key events and other event counts, page views, engagement time, transactions and revenue, and product views, add-to-carts and purchases. They are broken down by date, by the campaign tags on your links, by traffic source, device type, country, event name, landing page and product. They are totals only: Google Analytics gives us no visitor IDs, client IDs or IP addresses, and we do not ask for any.

What we use it for. Only for the features you use in the app, for the ad account you connected it to:

• showing your site's traffic next to your ChatGPT Ads results;
• matching visits, key events and revenue to your campaigns, ads and products, and working out return on ad spend;
• suggesting what to change.

Some suggestions are written by AI models. For those, the relevant figures are sent through OpenRouter to the company running the model (listed below), only over routes where that company does not train on it or use it for purposes of its own.

Who sees it. The people in your organization who have access to that ad account. Nobody at Ampthilly AB looks at your Google data unless you ask us to for support, it is needed to investigate a security problem or abuse, or the law requires it.

Where it is kept. The access Google gives us is a token. We store it encrypted in our database in the EU, and the short-lived tokens used for each read exist only while that read runs. The figures are kept in the same database for as long as the connection exists. The log of which reports we asked Google for is deleted after 90 days. How it is protected is described under How we protect your data.

Taking it back. Disconnect Google Analytics in the app, under Connections › Google Analytics, or delete the ad account. We then delete the stored token and every figure we read, and ask Google to withdraw our access. Google grants access per sign-in, not per ad account, so if another ad account is still connected through the same Google sign-in, the access stays until that one is disconnected too. You can also remove our access yourself at any time at myaccount.google.com/permissions: reads stop straight away, and disconnecting in the app then deletes the figures. Or email hello@athillyads.com and we delete them for you.

Google's rules. AthillyAds' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In practice:

• We don't sell Google data, and we don't hand it to advertising platforms, data brokers or anyone else. That includes ChatGPT Ads. The only things that reach your ChatGPT Ads account are what you approve there. For example, a campaign you start from one of your top pages carries that page's address.
• We don't use it to target ads at you or at anybody, or to judge anyone's creditworthiness.
• We don't use it to develop, improve or train generalized AI or machine-learning models.
• It is never part of the figures we look at across the platform.
• It only goes to anyone else in four cases:
  • to the subprocessors below, to run the features you use;
  • when the law requires it;
  • to protect against security problems or abuse;
  • as part of a merger or sale of the business, and only with your consent first.

Where your data lives, and who helps us process it

We aim to store and process personal data within the European Economic Area: the database and file storage run in an EU region, and we are a Swedish company, so GDPR is the frame we operate in. Delivering the service also involves a small set of subprocessors, some of which may process data outside the EEA under EU Standard Contractual Clauses:

• Cloudflare: this website, bot protection, DNS
• tawk.to: the support chat connection after you allow Chat or choose to open it, and conversations you submit
• Vercel: application hosting
• Supabase: database, authentication and file storage (EU region)
• Trigger.dev: background jobs (site reads, campaign generation, Google Analytics reads)
• Railway: watching the pages your ads point at, and rendering pages that need a browser
• OpenRouter: routes our requests to the AI models below
• AI models: Anthropic, Google, OpenAI, Microsoft (Azure), Amazon Web Services, xAI, Mistral AI, Cohere and TypeSafe. Any of them may be used for any of the AI work in the platform and the free tool, and which one does what changes as models improve. What goes through OpenRouter goes only over routes where the company running the model does not train on it or use it for purposes of its own
• ScraperAPI: fallback fetching for pages that block ordinary readers
• Stripe and Link: payments. When you buy in the app, Sold through Link, LLC, a Stripe company, sells you the license and handles your payment details under Link's own privacy policy; we never see or store your card number
• Fortnox: invoicing and bookkeeping for customers we invoice ourselves
• Resend: transactional email
• Slack: internal notifications to our team, for example the email address of someone who has just signed up

We send subprocessors only what they need to do their job, and none of them may use your data for their own purposes.

How we protect your data

Security procedures are in place to protect the confidentiality and integrity of your data. That includes the Google user data described above (the token Google gives us and the figures we read with it), which we treat as sensitive. In practice:

• Encrypted on the way. This website and the app at app.athillyads.com only answer over HTTPS, and our own requests (to Google, to ChatGPT Ads and to the AI models) are encrypted with TLS too.
• Encrypted where it is stored. Our database and file storage are encrypted at rest with AES-256.
• Tokens and keys are encrypted twice. The token Google gives us and your ChatGPT Ads API key are encrypted again by us before they are stored, each with a key of its own (AES-256-GCM), and those keys are encrypted with a master key that is never kept in the database. They can only be read on our servers, at the moment a call is made: never shown in the app, never written to a log and never put in a prompt to an AI model.
• Only your organization can read it. The database itself checks every read (row-level security): a signed-in person gets only the ad accounts their organization has given them access to.
• No more than we need. Our access to Google Analytics is read-only, we read totals with no visitor IDs, client IDs or IP addresses, the log of what we asked Google for is deleted after 90 days, and everything we read is deleted when you disconnect.
• Few people, all bound to confidentiality. Only the people who run the service can reach the systems it runs on, each with an account of their own protected by two-step verification, and everybody here is bound to keep what they see to themselves. Your Google data is looked at only in the cases listed above.
• Backed up. The database is backed up every day, so we can restore the service after a failure of ours. Backups expire on their own within 30 days, so what we delete leaves them too.
• If something goes wrong. If your data is reached by somebody who should not have it, you hear it from us without undue delay and within 72 hours of us knowing (what happened, what it touched and what we are doing about it), and we report it to the supervisory authority as GDPR requires.

What we don't do

• We don't sell or rent your data. To anyone, for anything.
• We don't use your private business data to advertise to others.
• We don't train AI models on your data.
• We do look at what happens across the platform as figures (what tends to work, what normal looks like in an industry), so the product gets better for everybody on it. Figures only: never your copy, your product data or anything a visitor left on your site, and nothing we show another customer says whose account a figure came from. Data from Google is never part of it.

Your rights

Under GDPR you can ask for access to your data, have it corrected, exported or deleted, restrict or object to processing, and withdraw any consent you've given. Email hello@athillyads.com and we handle it. You can also lodge a complaint with a supervisory authority: in Sweden, IMY (Integritetsskyddsmyndigheten).

Retention and deletion

Delete your account and we delete the personal data associated with it, keeping only what bookkeeping law requires us to keep (billing records, up to seven years) and anonymous aggregates that identify nobody. Free-tool request logs keep their hashed IP for 90 days, as above. Google Analytics figures are kept while the connection exists and deleted when you disconnect it or delete the ad account; see Google sign-in and Google Analytics.

Changes

If this policy changes in a way that matters, we'll say so visibly on the site, not bury it in a diff.