Privacy notice
Last updated 27 October 2026
This notice explains what personal data ADUNIT Kft. collects when you visit this website, email us, or use the adstack inspector, why we collect it, how long we keep it, and what rights you have over it.
Who we are
The controller of your personal data is ADUNIT Kft., Fő utca 61, 6640 Csongrád, Hungary (company registration number 06-09-027372). For anything about your data, write to info@adunittech.com.
This website
adunittech.com sets no cookies and runs no analytics, advertising or tracking scripts. Cloudflare delivers the site for us. To do that and to protect it from attacks, Cloudflare processes your IP address and the technical details of each request, such as the browser and the page asked for. We do not keep or analyse this data ourselves.
When you email us
If you write to us, we receive your name, email address and whatever your message contains. We use it to reply and, if we go on to work together, to run that relationship. Our email is hosted by Zoho in its EU data centres.
We keep correspondence for as long as the conversation or business relationship lasts. Anything that becomes part of a contract or accounting record is kept for as long as Hungarian law requires.
Legal basis: our legitimate interest in answering enquiries and running our business (Article 6(1)(f) GDPR), and taking steps towards a contract you ask about (Article 6(1)(b)).
The adstack inspector
The inspector, at inspector.adunittech.com and inspector-staging.adunittech.com, is where publishers' staff and our own team review and change how a publisher's advertising is set up. You can only sign in if an administrator has added you, either at your organisation or at ADUNIT.
Signing in
You sign in with your Google account. Google confirms who you are and sends us your email address, the fact that Google has verified it, and your name. We do not receive your Google password or anything else from your Google account. Google's own privacy policy applies to your Google account.
Administrators are also asked for a passkey. We store only the passkey's identifier and its public key, plus whether your device syncs it. The private key stays on your device and never reaches us.
What we keep, and for how long
| Data | Why | How long |
|---|---|---|
| Your email address and name, and the sites and roles an administrator gave you | To recognise you and decide what you may see and change | While you have access. Deleted within 30 days of your access ending |
| Your passkeys (identifier and public key) | To confirm it is an administrator signing in | Until you or an administrator remove them, or your access ends |
| Audit log: which change was made, to which site, when, and by whom (your email address) | So publishers and we can see who changed what, and to investigate problems and misuse | 24 months |
| Configuration history: your name and email address recorded as the author of each change you save | So every version of a publisher's setup shows who made it and can be restored | As long as we host that publisher's configuration. Deleted with it |
| Service logs: requests to the inspector (method and address within the inspector) and errors | To keep the service running and fix faults | 30 days |
| Firewall samples: a small sample of requests, including IP address | To block attacks on the inspector | Up to 3 hours, held by AWS |
Cookies
The inspector uses only cookies that are needed for signing in, so it does not ask for consent:
adstack_sessionkeeps you signed in. It lasts 8 hours.adstack_loginprotects the Google sign-in against forgery. It lasts 10 minutes and is removed once you are signed in.adstack_passkeycarries a passkey check. It lasts 5 minutes and is removed once the check is done.
Legal basis
Our legitimate interest, and your organisation's, in running the inspector securely and keeping a reliable record of changes (Article 6(1)(f) GDPR). Where you use the inspector under a contract with us yourself, performing that contract (Article 6(1)(b)).
Readers of publishers' websites
adstack also runs on publishers' websites to show advertising. There, the publisher decides how readers' data is used and asks for their consent through its own consent tool. We handle that data only on the publisher's behalf and under its instructions. The measurement data adstack collects about ad performance carries no identifier for the reader. If you are a reader, the publisher's privacy notice explains your choices, and the publisher is the right place for requests about your data. We will help them answer.
Who handles data for us
We use these providers, each under a contract that limits what they may do with the data:
- Amazon Web Services runs the inspector and stores its data, in its London region (United Kingdom).
- GitHub stores publishers' configuration history, including the author details described above (United States).
- Google handles signing in (see above).
- Cloudflare delivers this website and runs our domain's DNS.
- Zoho hosts our email (European Union).
We do not sell personal data, and we do not use it for advertising.
Transfers outside the EU
The United Kingdom is covered by a European Commission adequacy decision. For the United States, we rely on the provider's certification under the EU–US Data Privacy Framework, or on the European Commission's standard contractual clauses.
Your rights
Under the GDPR you can ask us to:
- tell you what personal data we hold about you and give you a copy;
- correct data that is wrong or incomplete;
- delete your data, or restrict how we use it;
- give you the data you provided in a machine-readable form.
You can also object to any processing based on our legitimate interest. Write to info@adunittech.com. We reply within one month, and we may ask you to confirm your identity first.
If you think we have handled your data wrongly, you can complain to the Hungarian data protection authority, the Nemzeti Adatvédelmi és Információszabadság Hatóság (naih.hu), or to the authority in the country where you live or work.
Changes to this notice
If what we do with personal data changes, we update this page and the date at the top. If the change affects inspector users, we also tell them in the inspector.