Privacy notice
This notice explains what personal data we process in connection with our brand visibility measurement service for AI answer engines, why we process it, how long we keep it, and what rights you have against us. It is written for people in the United Kingdom and follows the UK GDPR and the Data Protection Act 2018.
Version of 17 November 2026. This page has a permanent address: https://sourcecount.com/en/privacy. A Polish-language version of our privacy information is published at https://sourcecount.com/polityka-prywatnosci; the two documents describe the same processing and are kept in step with each other.
1. Who we are and who is responsible for your data
The controller of your personal data is asperIT.com Sp. z o.o., ul. Hubska 52 lok. 14, 50-502 Wrocław, Poland — a Polish limited liability company (spółka z ograniczoną odpowiedzialnością) entered in the register of entrepreneurs of the National Court Register (KRS) under number 0000800376, Sąd Rejonowy dla Wrocławia-Fabrycznej we Wrocławiu, VI Wydział Gospodarczy Krajowego Rejestru Sądowego, tax identification number (NIP) 8992867254, statistical number (REGON) 384190260.
SourceCount is a trading name of asperIT.com Sp. z o.o.. It is not a separate company and it is not a UK entity. The Polish company is always the controller of your personal data, always the party to any contract with you, and always the issuer of any invoice. There is no UK subsidiary, no UK branch, no UK office and no UK staff.
For anything concerning your personal data — questions, requests, objections, complaints — write to [email protected], or to the postal address above. We have not appointed a Data Protection Officer; none of the conditions in Article 37 UK GDPR applies to us. Correspondence about personal data is handled at the address above.
Because we are established in Poland and also offer services to people in the United Kingdom, both the UK GDPR and the EU GDPR apply to us at the same time — the UK GDPR under its Article 3(2), and the EU GDPR under its Article 3(1). This is not a choice we make; it follows from both regulations. It is also the reason you have two supervisory authorities available to you (section 8).
2. What this notice covers
This notice covers personal data we process when you contact us, when we provide our service to a company you work for, and when we keep records we are required or entitled to keep. It applies to this website, to our email correspondence and to the delivery of our audit and monitoring services.
We sell to businesses only. We do not sell to consumers and we do not knowingly process personal data of people who are not acting in a professional or business capacity.
3. Why we process your data, what we collect, and our legal basis
Each situation is listed separately because the legal basis and the retention period differ.
| Situation | What we collect | Where it comes from | Purpose | Legal basis | How long we keep it |
|---|---|---|---|---|---|
| A. You send us an enquiry — through the contact form or by email | your name, your company, your business email address, optionally the content of your message; where you tick a consent box, also the exact wording of that consent, the version of that wording, a server timestamp and your IP address | from you | to read your enquiry and reply to it, and to prepare a quotation if you ask for one | Article 6(1)(b) UK GDPR (steps taken at your request before entering into a contract) and Article 6(1)(f) UK GDPR (our legitimate interest in answering business correspondence addressed to us). We do not need your consent to reply to you, and we do not ask for it — you contacted us, so our reply is a solicited communication | 12 months from our last contact with you about the enquiry, then deletion or full anonymisation. The form submission record held by our hosting provider is additionally deleted automatically 360 days after it is submitted, by an expiry set on the record itself |
| B. You tick a consent box — marketing by email | your business email address, plus the record of consent described in A | from you | to send you commercial information about our services, and — for the second box — our newsletter and research materials such as category visibility reports | Article 6(1)(a) UK GDPR (your consent), and for the sending itself regulation 22 PECR | until you withdraw your consent or object. The record proving the consent is kept for as long as we rely on the consent and for 5 years after it is withdrawn (see section 6) |
| C. Contact people at a client — after a contract is signed | name, job title, business email address, business telephone number | from the client | performing the contract, day-to-day correspondence, delivering reports, invoicing | Article 6(1)(b) UK GDPR (performance of the contract) and Article 6(1)(f) UK GDPR (operational contact; establishing, exercising or defending legal claims) | the term of the contract and 3 years after it ends |
| D. Invoicing and accounting data | the buyer's details; where the buyer is a sole trader, those details are personal data | from the client | issuing invoices, keeping books and accounts, tax settlement | Article 6(1)(c) UK GDPR — compliance with a legal obligation to which we are subject under Polish tax and accounting law | 5 years counted from the end of the tax year in which the tax obligation arose |
| E. Content of measurement queries sent to AI providers | as a rule no personal data; the exception is a client brand that is a natural person's name | from the client and from the client's public website | running the visibility measurement that the client ordered | Article 6(1)(b) UK GDPR, and only where the client has confirmed in the order that the name is the client's own brand | measurement records for the term of the engagement and until claims under the contract are time-barred |
| F. Public pages of a client's website fetched during a technical audit | incidentally: names of team members, content authors or people quoted in testimonials — only to the extent the client has published them itself | the client's public website, without logging in | assessing content structure and how readable the site is for AI crawlers | Article 6(1)(b) and Article 6(1)(f) UK GDPR | we process the content only to produce the report and do not archive it afterwards. Our reports do not name people from a client's website |
| G. Defending ourselves against claims and demonstrating compliance | correspondence, consent records, evidence that a service was performed | from the situations above | establishing, exercising or defending legal claims, and demonstrating compliance with data protection law | Article 6(1)(f) UK GDPR (our legitimate interest in defending claims) and Articles 5(2) and 7(1) UK GDPR (accountability; the burden of proving consent is on us) | until the relevant claims are time-barred; consent records as stated in B |
| H. Submission rate counter on the contact form — abuse protection | the IP address the form was submitted from — as part of the name of the record — and the number of submissions made from that address within the current hour. Nothing else: the record holds no message content, no name and no email address, and it is not linked to the record of your submission | from you — your browser sends the IP address automatically when you submit the form; you do not type it into any field | limiting submissions from a single address to five per hour, so that the form cannot be flooded with automated submissions. No person reads this record — only the code that handles the form reads it, in order to count submissions. We use it for nothing else, we do not analyse behaviour with it and we build no statistics from it | Article 6(1)(f) UK GDPR — our legitimate interest in keeping this form available and secure, and in protecting the data of people who have already sent it to us through that form. Keeping our processing secure is an obligation on us under Article 32 UK GDPR; this counter is one of the measures we use to meet it | 1 hour from the last submission from that address — after that the record deletes itself, automatically and without any action by us. We make no copy of it and we move it nowhere else |
What we do not do when collecting data
- We do not buy contact lists and we do not obtain data from data brokers.
- We do not use bulk automated sending tools and we do not use automated calling systems.
- We do not send marketing text messages and we do not make marketing telephone calls.
- We do not ask for and do not accept access to client systems that contain personal data (CRM, Google Search Console, GA4, server logs). Extending our service to any such access would require a data processing agreement signed in advance.
- In a technical audit we analyse structure, not people: structured data, headings,
robots.txt, content coverage and how completely the offer is described. We do not fetch pages behind a login, we do not keep lists of people from a client's site, we do not name them in reports, and we never move their details into our own contact list. - We do not send AI providers queries containing the names of natural persons other than the client's own brand as confirmed in the order — this also applies to competitor measurement.
- We do not currently send unsolicited marketing email to UK recipients. If that changes, this notice will be updated before the first message is sent, because we would then be processing your data without having obtained it from you, and Article 14 UK GDPR requires us to tell you so.
4. Who we share your data with
Your data may reach only the following categories of recipients, and only to the extent necessary for the purpose for which we collected it:
- Cloudflare, Inc. (and its group companies) — our hosting provider and our processor within the meaning of Article 28 UK GDPR. This website runs on Cloudflare Pages; the contact form is handled by our own code running on Cloudflare Workers, and form submissions — including the record of any consent you give — are stored in Cloudflare's key-value storage. The rate-counter record described in situation H is held in the same storage. Cloudflare also processes technical server logs and security data for us.
- our email provider — for correspondence.
- providers of AI model interfaces: OpenAI, Perplexity and Google — solely for the content of measurement queries, which as a rule contains no personal data (situation E above).
- our accountants and the Polish National e-Invoicing System (KSeF) — for invoicing and accounting data. Polish law requires us to issue invoices through KSeF; where you are a UK buyer we additionally send you a PDF invoice by email, because a UK company has no access to KSeF.
- public authorities — where we are required by law to disclose data.
We do not sell personal data, we do not make it available for other organisations' marketing, and we do not use third-party subcontractors to deliver the service itself.
5. Transfers of your data outside the United Kingdom
We are open about this because our whole structure involves data leaving the UK: we are a Polish company, so if you contact us your data reaches Poland.
- Your data coming to us in Poland. When you send us an enquiry you transmit your data to us directly. In addition, the United Kingdom recognises the European Economic Area, including Poland, as providing an adequate level of protection, under adequacy regulations made for the purposes of Chapter V (Article 45) of the UK GDPR. So this part of the journey is covered by adequacy, and no further safeguard is needed.
- Data processed for us in the United States — Cloudflare. Cloudflare, Inc. is established in the United States, and form submissions, consent records, rate-counter records and technical logs may be processed there. This transfer takes place under the appropriate safeguards in Article 46 UK GDPR: the European Commission's standard contractual clauses together with the UK International Data Transfer Addendum to those clauses, as set out in our data processing agreement with the provider. Where a provider is certified under the UK Extension to the EU–US Data Privacy Framework, that transfer is instead covered by the corresponding adequacy decision („data bridge”).
- Data sent to AI providers in the United States — OpenAI, Perplexity, Google. Our measurement queries are designed not to contain personal data, and in the ordinary case they do not. Where a query does contain personal data — the single case being a client brand that is a natural person's name, which we accept only on the client's written confirmation — the transfer relies on the same mechanisms as above: Article 46 UK GDPR safeguards (the UK International Data Transfer Agreement, or standard contractual clauses with the UK Addendum) or, for a provider certified under the UK Extension to the EU–US Data Privacy Framework, adequacy.
We keep a record of which mechanism applies to which provider and we will tell you which one applies in your case if you ask at [email protected]. We reduce this risk at source rather than only on paper: by default we measure queries about product categories and about brands as business identifiers, not queries containing people's names.
6. How long we keep your data
The retention period for each situation is in the table in section 3. In short:
- enquiries sent through the form or by email — 12 months from our last contact with you about the enquiry, after which we delete or fully anonymise them. The submission record held in our hosting provider's storage carries an expiry set when it is written and deletes itself 360 days after submission, so the promised period is enforced by the system and not only by us remembering;
- the submission rate counter on the contact form — 1 hour from the last submission from your IP address. A one-hour expiry is set on that record when it is written, so it deletes itself; we keep no copy of it (situation H in the table in section 3);
- records proving a consent you gave — for as long as we rely on that consent and for 5 years after you withdraw it. We keep these because Articles 5(2) and 7(1) UK GDPR place the burden of demonstrating consent on us: without the record we could not show what exactly you agreed to and when;
- contract and contact data — 3 years after the contract ends;
- invoicing and accounting data — 5 years from the end of the tax year in which the tax obligation arose, as required by Polish tax and accounting law.
We review these periods once a quarter, so that they are enforced rather than merely published.
7. Your rights
In relation to the personal data we process about you, you have the following rights under the UK GDPR:
- the right of access to your data and to a copy of it (Article 15);
- the right to rectification of inaccurate data and completion of incomplete data (Article 16);
- the right to erasure (Article 17);
- the right to restriction of processing (Article 18);
- the right to data portability, for data processed by automated means on the basis of consent or a contract (Article 20);
- the right to object to processing based on our legitimate interests, including an absolute right to object to direct marketing (Article 21) — we act on a marketing objection immediately and we do not ask you why;
- the right not to be subject to a decision based solely on automated processing, including profiling (Article 22) — we take no such decisions about anyone;
- the right to withdraw consent at any time where processing is based on consent (Article 7(3)). Withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal.
How to exercise them and how quickly we answer. Send your request to [email protected] — a single sentence is enough, and you do not need to use any particular form or wording. We reply without undue delay and in any event within one month of receiving your request, as required by Article 12(3) UK GDPR. If your request is complex or you have made a number of requests, we may extend that period by a further two months; if we do, we will tell you within the first month and explain why. Exercising these rights is free of charge.
The fastest way to stop hearing from us: reply to any message from us with the word „unsubscribe” or „object”. That is enough. We do not ask for a reason, we do not ask you to confirm, and we do not contact you again. If you object, we stop contacting you immediately; we keep your email address (or a cryptographic hash of it) with the date and channel of your objection on a suppression list, for as long as we operate that contact channel — without that list we would contact you again, which is exactly what you asked us not to do. The suppression list holds nothing else: no name, no company, no job title, no notes, no contact history.
8. How to complain — and why there are two authorities
You have the right to lodge a complaint with a supervisory authority. In our case there are two, and both are genuinely available to you. This is not a translation error and you do not have to choose „the right one”:
- the Information Commissioner's Office (ICO) — the UK supervisory authority, because the UK GDPR applies to us under its Article 3(2): we offer our services to people in the United Kingdom even though we are not established there. Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, United Kingdom — ico.org.uk;
- the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych) — the Polish supervisory authority, because we are established in Poland and the EU GDPR applies to us under its Article 3(1), which makes the Polish authority the supervisory authority of our establishment. ul. Stawki 2, 00-193 Warsaw, Poland — uodo.gov.pl.
You can also complain directly to us first at [email protected], but you do not have to, and nothing in this notice requires you to come to us before going to a regulator.
9. Cookies, local storage and third-party content
This website stores nothing on your device and reads nothing from it. We set no cookies, we do not use localStorage or sessionStorage, we use no tracking pixels, no social network plugins, no device fingerprinting and no analytics tools of any kind — we do not even count visits. We also load no resources from third-party servers: no web fonts, no scripts, no images and no embedded content from anywhere other than this site. For the same reason there is no CAPTCHA on our contact form: the usual CAPTCHA services are third-party scripts, and we have chosen not to load them. Our form is protected by our own code instead.
Because nothing is stored on or read from your device, regulation 6 of the Privacy and Electronic Communications (EC Directive) Regulations 2003 does not require your consent for anything on this site — and that is why you are not seeing a cookie banner. There is nothing to consent to. Regulation 6 is wider than „cookies”: it covers any storage of, or access to, information on your terminal equipment. Our statement above is deliberately written to that wider standard, not just to cookies.
Three things do still happen on the server side, and we would rather say so than let you discover them:
- our hosting provider processes technical server logs (IP address, time of the request, requested address, browser type) in order to keep the service available and secure. This is not storage on your device and it is not covered by regulation 6, but it is personal data, and we process it under Article 6(1)(f) UK GDPR. We do not combine these logs with any other data and we do not use them to analyse your behaviour;
- where you tick a consent box, our contact form records your IP address and a server timestamp together with your submission. That is there to prove when and to what exactly you consented, and it is the only thing we use it for. Where you tick no consent box, no IP address is stored with your submission at all (situation A in the table in section 3);
- our contact form counts submissions per IP address, up to five per hour, so that it cannot be flooded with automated submissions. That count lives in a separate record named after your IP address; it holds nothing but a number, no person reads it, it is not linked to your submission, and it deletes itself one hour after your last submission (situation H in the table in section 3). This is storage on our side, not on your device, so regulation 6 PECR does not require your consent for it either — and it is the reason our form needs no third-party CAPTCHA.
We profile no one and we take no automated decisions producing legal effects for anyone.
10. Is providing your data mandatory?
Providing data through the contact form is voluntary, but without an email address we cannot reply to your enquiry. Neither consent box on the form is required, neither of them is ticked in advance, and ticking or not ticking them has no effect on whether we answer you. Providing the data needed for a contract and an invoice is a condition of entering into and settling that contract — without it we cannot deliver the service or issue an invoice.
11. Security and automation on our side
We deliver the service using our own tools and largely automated processes, under human supervision. We say this plainly because it is part of describing the service honestly, not a technical detail: measurement, metric calculation and report assembly are performed by software, while interpretation and quality control are performed by a person. This automation does not involve any decision-making that produces legal effects for anyone.
Access to data is limited to the people and processes that need it. We do not keep contact data in tools whose providers are not listed in section 4.
12. UK representative (Article 27 UK GDPR)
We have not appointed a representative in the United Kingdom, and we are relying on the exception in Article 27(2)(a) UK GDPR. Our processing of personal data relating to people in the United Kingdom is occasional: it arises only when someone contacts us first, through this website or by email. We do not run outbound marketing campaigns to UK recipients, we process no special category data, we do no profiling, we take no automated decisions, we keep enquiries for 12 months, and we act on an objection or a withdrawal of consent immediately. On that basis the processing is unlikely to result in a risk to the rights and freedoms of natural persons.
If that changes — in particular if we start contacting UK recipients who have not contacted us first — we will reassess this and update this notice before doing so. Until then, [email protected] is the single point of contact for everything in this notice, and the ICO remains available to you under section 8 regardless of whether we have a representative.
13. Trade marks
ChatGPT and OpenAI are trademarks of OpenAI OpCo, LLC. Google and Gemini are trademarks of Google LLC. Perplexity is a trademark of Perplexity AI, Inc. We use these names solely to identify the systems our measurement covers, as permitted by Article 156(1)(3) of the Polish Industrial Property Law. asperIT.com Sp. z o.o. is not a partner, reseller, affiliate or authorised representative of any of these providers, does not act on their behalf and is neither certified nor endorsed by them. Our services are not products of these providers.
14. Changes to this notice
If we change the scope of our service, our contact channels or our providers, we will update this document and change the version date at the top of it. The address of this page stays the same, so that links in earlier messages keep working. Earlier versions are available on request at [email protected].