1. Subject matter, parties and scope
This agreement governs the processing of personal data on behalf of the customer under Art. 28 of the General Data Protection Regulation (GDPR) when Nalqerio is used. The processor is Christof Bartel, Nalqerio, Gooskamp 2, 24598 Boostedt, Germany (“Nalqerio”). The controller is the customer who uses Nalqerio for their commercial or self-employed professional activity (“customer”).
This agreement forms part of the terms of use and is concluded when they are accepted, including for the free trial. No separate signature is required; the electronic form is sufficient (Art. 28(9) GDPR).
It applies where Nalqerio processes personal data on the customer’s behalf. For the account, billing, security and abuse prevention and for its own website analytics, Nalqerio acts as an independent controller; the privacy policy applies to that processing. In the event of a conflict on data protection matters, this agreement takes precedence over the terms of use.
2. Nature, purpose and duration of the processing
Nalqerio provides web-based software that lets the customer measure and monitor how businesses and websites are presented in answers from AI systems. This includes measurements, automatic monitoring, the website audit, recommendations and tasks, reports, exports, private share links, team access and – where the customer adds the counting code to its website – counting visits that reach its website through AI systems (“AI visitors”), and, at the customer’s request, e-mails with reports on the AI visitors to the customer and, with the Pro plan, to recipients it names.
The processing comprises collecting, storing, organising, retrieving, analysing, displaying, transmitting to the services listed in Annex 1 and deleting data. Its purpose is to provide the services the customer selects in Nalqerio. This includes automatically evaluating the stored answers into figures about the customer’s brand and the competitors it has chosen (share of all mentions, position of the mention, trend, classification of the wording and of the traits named based on fixed word lists); no AI is used for this, and no data is passed to further recipients. In addition, the customer instructs Nalqerio to anonymise measurement results and to use them in aggregated form for comparison values, such as the industry comparison. The comparison values identify neither the customer nor individual projects or persons and are only shown once results from at least five businesses in five different accounts are available.
This agreement applies for the term of the contract of use, including the free trial, and beyond until the data has been deleted under Section 9.
3. Types of data and data subjects
The following are processed in particular:
- project details: business and brand names, website addresses, locations, industries, competitors, customer questions, notes and tasks;
- measurement results: answers from AI systems with the businesses and persons named in them, source addresses and map results with publicly listed reviews;
- content of publicly accessible web pages from the website audit, the content check and the sources cited in AI answers, such as titles, headings, text excerpts and businesses named there;
- email addresses and roles of persons the customer invites to a project;
- email addresses of recipients the customer enters for reports on the AI visitors, with the language and the times of the confirmation request, the confirmation and any unsubscription;
- content of reports and private share links;
- where the counting code is installed: for every visit that reaches the customer’s website through an AI system, the name of the AI service, the page visited without parameters and the day, stored only as a daily count. When the code is loaded, the IP address, browser identifier and referring page are also processed for technical reasons in the hosting provider’s server logs; to prevent abuse, the IP address is used briefly as a value derived with a secret key. The counting code uses no cookies or other storage on the device.
Data subjects may include the customer’s employees and contacts; owners, contacts and employees of businesses the customer monitors or records as competitors, such as sole traders whose name is also their business name; the customer’s own clients where an agency sets up projects for them or has reports sent to them; persons named in AI answers or on audited web pages; and, where the counting code is installed, visitors to the customer’s website.
Special categories of personal data under Art. 9 GDPR are not intended to be processed. The customer does not enter confidential personal data, or personal data that the measurement does not need, in customer questions and project details.
4. Customer instructions
Nalqerio processes the data only on documented instructions from the customer, including with regard to transfers to third countries, unless Nalqerio is required to do so by law. In that case Nalqerio informs the customer of that legal requirement before processing, unless the law prohibits such information.
The instructions follow from the terms of use, this agreement and the customer’s settings and actions in Nalqerio, for example creating a project, starting a measurement, switching on monitoring, sharing a report, entering recipients for reports or deleting a project. The customer gives further instructions in text form to support@nalqerio.com.
If Nalqerio considers that an instruction infringes data protection law, Nalqerio informs the customer without undue delay and may suspend carrying it out until it has been clarified.
5. Nalqerio’s obligations
- Confidentiality: only the operator and persons who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality have access to the data, and only to the extent required for the service.
- Security: Nalqerio takes the technical and organisational measures under Art. 32 GDPR set out in Annex 2. Nalqerio may adapt them to technical progress provided the level of protection does not decrease.
- Assistance: Nalqerio assists the customer, using the information available to it, in complying with the obligations under Art. 32 to 36 GDPR, in particular with notifications, data protection impact assessments and prior consultations.
- Place of processing: the application, database and files are hosted by a provider in Germany, backups are stored in an EU storage region. Transfers to third countries take place only through the services listed in Annex 1 and only where the conditions of Art. 44 et seq. GDPR are met, for example through an adequacy decision or the EU standard contractual clauses.
- The contact for data protection is the operator at support@nalqerio.com.
6. Sub-processors
The customer gives general authorisation for the use of the sub-processors listed in Annex 1. Nalqerio contractually obliges them to a level of protection that corresponds to this agreement (Art. 28(4) GDPR); where providers use standard data processing terms, those terms apply.
Nalqerio informs the customer at least 14 days in advance, by email or by a notice in the account, of any intended addition or replacement of a sub-processor. Within that period the customer may object in text form on reasonable data protection grounds. If the parties cannot find a solution, the customer may terminate the contract with effect from the date of the change; Nalqerio refunds on a pro-rata basis any fees already paid for the period after that date.
Services that Nalqerio uses for its own purposes as an independent controller are not sub-processing, for example payment processing through Stripe, Cloudflare Turnstile to protect forms or the optional website analytics. They are described in the privacy policy.
7. Data subject rights and customer obligations
Nalqerio assists the customer with appropriate technical and organisational measures in responding to requests from data subjects under Art. 12 to 23 GDPR. The customer can handle much of this directly: correcting details in the account, deleting projects and exporting evidence. If a data subject contacts Nalqerio directly, Nalqerio refers them to the customer where the request can be attributed and informs the customer without undue delay.
The customer is responsible for the lawfulness of the processing, in particular for choosing the businesses, customer questions and content it has Nalqerio record and measure. If the customer notices errors or irregularities in the processing, it informs Nalqerio without undue delay.
If the customer installs the counting code, it does so only on websites it is responsible for. It obtains the visitors’ consent required under Art. 6(1)(a) GDPR and the applicable rules on access to terminal equipment (in Germany § 25(1) TDDDG), loads the code only after that consent and informs visitors in its privacy policy; Nalqerio provides a suggested text for this.
If the customer enters recipients for reports, it does so only for persons to whom it may send these reports. Nalqerio first sends each recipient a single e-mail asking for confirmation, sends reports only after that confirmation and puts unsubscriptions into effect at once; every e-mail to a recipient contains a link to unsubscribe.
8. Notification of personal data breaches
Nalqerio notifies the customer without undue delay, where possible within 48 hours of becoming aware, of a personal data breach affecting the customer’s data (Art. 33(2) GDPR). As far as known, the notification contains the information under Art. 33(3) GDPR and is supplemented as further information becomes available. Nalqerio takes measures without undue delay to contain the breach and mitigate possible adverse effects.
9. Deletion and return
The customer can export its project evidence at any time within its plan and delete projects itself. After the contract ends, the data remains in the account until the customer deletes projects or the account or instructs Nalqerio in text form to delete it. On request, Nalqerio provides an export of the project data before deletion.
Deleted projects are removed from the interface immediately and finally deleted 30 days later; when an account is deleted, its projects are deleted immediately. The customer may request earlier final deletion at support@nalqerio.com.
Nalqerio automatically deletes the daily counts of visitor counting after 13 months. After the contract ends, Nalqerio no longer counts visits, even if the counting code is still installed; the customer then removes the code from its website.
Nalqerio deletes the addresses of report recipients as soon as the customer removes them and at the latest on the day after the project is deleted, unconfirmed ones 14 days after the last confirmation request and unsubscribed ones 30 days after unsubscribing. Without the Pro plan or while the project is archived, no recipient receives e-mails any more; Nalqerio then deletes the addresses after 30 days.
In backups – encrypted outside the hosting and access-protected on the server before software releases – data remains stored until their regular rotation and is not otherwise processed during that time, except for restoration after a data loss. Cost and usage records without question, business or answer text, and documents that Nalqerio must retain by law, are kept.
10. Evidence and audits
Nalqerio makes available to the customer the information necessary to demonstrate compliance with this agreement, in particular this agreement with its annexes and information in text form. In addition, Nalqerio allows for audits, including inspections, by the customer or by an auditor mandated by the customer who is bound to confidentiality.
Inspections are normally to be announced 30 days in advance, take place during normal business hours, must not unreasonably disrupt operations and must protect the confidentiality of other customers’ data. Audits are primarily carried out by means of information and documents. The customer bears the costs of an inspection unless it reveals a material breach of this agreement by Nalqerio.
11. Liability and final provisions
Art. 82 GDPR applies to liability towards data subjects. Between the customer and Nalqerio, the liability rules of the terms of use otherwise apply.
Nalqerio informs the customer of changes to this agreement in good time in text form; Section 13 of the terms of use applies accordingly to changes. If a provision is invalid, the remainder of the agreement remains valid. German law applies. The German version is binding; this English version is a translation.
Annex 1: Sub-processors
As of 14 November 2026. The privacy policy describes in detail which services are involved in a particular function.
- ALL-INKL.COM – Neue Medien Münnich, Friedersdorf, Germany: hosting of the application, database and files, and sending of service emails. Concerns all project data. Processing in Germany.
- Backblaze, Inc. (Backblaze B2): storage of daily backups that are encrypted before transfer. Concerns all project data in encrypted form. Stored in an EU storage region; provider based in the USA.
- OpenAI: fallback route for ChatGPT measurements during disruptions and, on request, website analysis, question and competitor suggestions and AI text drafts. For measurements only the customer question, language and country are transmitted, for the other functions also business, market and topic details of the project and text excerpts from public pages; in each case with the setting store=false. Processing also outside the EEA, in particular in the USA.
- Google (Gemini API): on request, website analysis and suggestions based on provided public pages. Customer questions, business and topic details and text excerpts from public pages are transmitted. Processing outside the EEA is possible.
- Perplexity: measurements for Perplexity and, as a fallback route, the Gemini measurement, in which a Gemini model answers through the Perplexity Agent API with its web search. The customer question, language and country are transmitted. Processing also outside the EEA, in particular in the USA.
- DataForSEO OÜ, Tallinn, Estonia: measurements for ChatGPT and Gemini (answers from the respective interface), for Claude and of Google AI Overviews and Google AI Mode. Only the customer question and the language, country and – for Google – device type are transmitted. DataForSEO asks the question in ChatGPT (OpenAI), Gemini (Google), Google Search or through Claude’s interface; they receive no account or contact data of the customer. If a customer question contains the name of a business or person, it is part of the question. Established in the EU; according to its own list, DataForSEO also uses infrastructure providers in the USA. Transfers are governed by the EU standard contractual clauses in DataForSEO’s data processing agreement.
- Anthropic PBC, San Francisco, USA (via DataForSEO): produces the Claude answers with web search. Only the customer question and the country of the web search are transmitted; Anthropic receives no account or contact data of the customer. Processing also outside the EEA, in particular in the USA; transfers take place only if the requirements of Art. 44 et seq. GDPR are met, for which Anthropic provides EU standard contractual clauses in the terms for its interface.
Annex 2: Technical and organisational measures (Art. 32 GDPR)
Confidentiality
- Physical access: the servers are located in the hosting provider’s data centre in Germany; physical access follows the provider’s security concept.
- Server access: administrative access to the server and the hosting administration only for the operator; server access encrypted via SSH; directories and configuration files with restricted file permissions.
- Application access: passwords with at least 12 characters, upper- and lower-case letters and a number, stored only as a hash; optional two-factor sign-in; limits on repeated sign-in and form attempts; protection of sessions and forms against forgery.
- Authorisation: project permissions for account owners and invited persons with defined roles; private share links with a random key that can be time-limited and revoked at any time; the operator area is only accessible to confirmed operator accounts.
- Separation: data of different customers is separated by account and project; test and staging environments use their own databases.
- Encryption and pseudonymisation: billing profiles, contract and declaration records, two-factor sign-in secrets, access tokens for Google Analytics and the email addresses of report recipients are stored encrypted; IP addresses for abuse prevention only as a hash.
Integrity
- Transmission: exclusively encrypted via HTTPS with HSTS; unencrypted requests are redirected to HTTPS. Connections to the services in Annex 1 are encrypted as well.
- Data minimisation: AI services receive only the details needed for the respective measurement. An AI request is only made after an explicit start or with monitoring switched on. Visitor counting uses no cookies and no storage on the device, keeps no IP addresses in the statistics and counts only on the website of the respective project, as a daily count per AI service and page.
- Traceability: measurement runs, costs and contract and sharing events are stored with a timestamp. Error logs are closed daily and deleted after 30 days.
- Protection of the web interface: Content Security Policy and further security headers.
Availability and resilience
- Daily backup outside the hosting, encrypted before transfer, with a retention lock for new backups.
- Weekly automatic restore test in a separate test area.
- Before every software release an additional backup with a restore test, access-protected on the server (the five most recent are kept); failed releases are rolled back automatically.
- Independent monitoring of availability and backup status with alerts to the operator.
Regular review
- Several thousand automated tests run before every release.
- Security updates of the software used are applied promptly.
- A public security contact is published in accordance with RFC 9116 (security.txt).
- Privacy-friendly defaults: website analytics and ad measurement only after consent.
- Processor control: sub-processors only as listed in Annex 1; processing only on the instructions under Section 4.
Version 2026-11-17-1 · Last updated: 17 November 2026