Sub-processors
Last updated 13 October 2026
AdStck is software that marketing agencies use to run enquiry forms for the businesses they work with. When you fill in one of those forms, the business you are contacting is responsible for your data, and AdStck processes it on their instructions. This page lists the providers AdStck in turn relies on, so that a business’s privacy policy can say “AdStck” and you can see what that means.
Providers AdStck uses to process data
These act on AdStck’s instructions, under contracts that require them to protect the data and use it for nothing else.
Database and sign-in. Holds every enquiry: name, phone, email, answers, and the details of any booking. Also holds the agency and business accounts.
Runs the AdStck application. Personal data passes through it while a form is submitted, an email is sent, or a page is served; it is not stored there.
Sends email — booking confirmations, reminders, follow-ups, invoices. Receives the recipient’s name and email address and the content of the message.
Sent data only when a business turns it on
These are not AdStck’s providers. A business chooses to connect them to measure its advertising, and each one decides for itself how it uses what it receives. The business’s own privacy policy says whether it has done so.
Only if a business has connected a Meta pixel. Receives an advertising click identifier and contact details converted to a one-way hash, so it can match an enquiry to an advert. Meta decides how it uses that data under its own policy.
Only if a business has connected Google Ads or Tag Manager. Receives the same: a click identifier and hashed contact details, for the same purpose. Google decides how it uses that data under its own policy.
Domain names
Only when a business uses AdStck to register or move in a domain name. These receive the domain owner’s details because registering any domain requires them.
Only when a business registers or moves in a domain through AdStck. Receives the domain owner’s name, address, email and phone number, which every registration needs, and registers the domain in the owner’s name.
The registry for .uk domains. Receives the same owner details from Openprovider. For an owner who is an individual, it hides their name and address from public lookup.
For endings such as .com, the registry for that ending (Verisign for .com), and the escrow provider ICANN requires, which keeps a copy so the domain survives if a registrar fails.
Contacted, but never with your data
Listed because the application talks to them, so you are not left wondering.
Asked for the centre of a town or city, by name. Never a person’s address.
Serves the background map tiles in the dashboard. Sees which area of the map is being viewed, not who is on it.
Nothing. The GeoLite2 database used to place an IP address is a file inside the application; no lookup leaves it.
Nothing about any enquiry. Used to draft funnel copy and page text for a business; never sent a lead.
The agency’s own account data — reviews, campaign names, click reports — never an enquiry.
Changes
When a provider is added or replaced this page is updated and the date at the top changes. Because every business’s privacy policy links here rather than naming providers itself, their policies stay accurate without being rewritten.
Questions
About a specific enquiry you made: contact the business you made it to — their details are in their privacy policy. About AdStck itself: privacy@adstck.com.