Skip to content
Querora

Data Processing Agreement

When does Querora process data on a client's behalf?

When we work on your website and accounts, for example in your CMS or Google Analytics 4, we can access data about your customers and site visitors. We process it only to perform the subscription, on your instructions and in line with Article 28 GDPR. You enter into the DPA by accepting the terms at sign-up.

1.Parties and conclusion

1.1.

This Data Processing Agreement ("DPA") is made between the Client as the data controller ("Controller") and Michał Fox, doing business under the Querora brand, in Kraków, Poland, email: hello@querora.com, as the processor ("Querora").

1.2.

The DPA is concluded electronically when the Client accepts the Terms of Service on entering into the Contract, and meets the requirements of Article 28(3) and 28(9) GDPR. GDPR means Regulation (EU) 2016/679 of the European Parliament and of the Council.

1.3.

The DPA applies for as long as the Contract runs and until the data is deleted or returned under Section 10. On personal data it prevails over the Terms, and a separate data processing agreement signed by the parties prevails over this template.

1.4.

Capitalized terms have the meaning given in the Terms.

2.Subject matter, nature and purpose

2.1.

The Controller entrusts Querora with processing the personal data Querora can access in the Client Accounts and on the Client Website, solely to perform the Subscription.

2.2.

Processing includes, in particular: reading and viewing data in the CMS, on the server and in the Google Business Profile while shipping fixes and content; analyzing data from Google Search Console, Bing Webmaster Tools and Google Analytics 4 in aggregated form; and storing in the Panel the content of Tickets and the attachments the Controller adds to them.

2.3.

Querora does not use the entrusted data for its own purposes, does not combine it with other clients' data and does not pass it to AI Engines. We send AI Engines only the Questions from the Measurement list.

3.Types of data and categories of data subjects

3.1.

The entrusted processing may cover the following categories of data subjects and data:

Data subjectsTypes of dataWhere the data is
Visitors of the Client Websiteonline identifiers, IP address, device and usage dataGoogle Analytics 4, Client Website server logs
The Controller's customers and contactsname, email address, phone number, message content, order detailsCMS, forms and database of the Client Website
Authors of reviews and commentsauthor name, review text and dateGoogle Business Profile, CMS
The Controller's staff and contractorsname, email address, roleCMS accounts, Tickets, correspondence
3.2.

Google Search Console and Bing Webmaster Tools provide aggregated search data, which as a rule is not personal data.

3.3.

The Controller does not entrust special categories of data (Article 9 GDPR) or data on criminal convictions. If such data exists in the systems of the Client Website, for example health data in a clinic's forms, the Controller says so before granting access, and Querora does not view that data and uses only the parts of the system needed for the work.

4.Querora's obligations

4.1.

Querora:

  1. processes the data only on documented instructions from the Controller, which are the Contract, the DPA and instructions given in Tickets, including with regard to transfers outside the European Economic Area;
  2. informs the Controller immediately if in its opinion an instruction infringes the GDPR or other law;
  3. gives access to the data only to authorized people who have committed to confidentiality;
  4. applies the security measures in Section 5;
  5. uses sub-processors only under Section 6;
  6. assists the Controller in responding to requests from data subjects (Section 8);
  7. assists the Controller in meeting its obligations under Articles 32 to 36 GDPR, taking into account the nature of processing and the information available;
  8. deletes or returns the data after the Contract ends under Section 10;
  9. makes available the information needed to demonstrate compliance with Article 28 GDPR and allows audits (Section 9).

5.Security measures

5.1.

Querora applies technical and organizational measures appropriate to the risk, in particular:

  1. encrypted connections when working with the Client Accounts and the Client Website;
  2. separate accounts and roles instead of shared passwords where the Controller's system allows it, and two-factor authentication on Querora's accounts;
  3. the least privileges needed for the work, including read-only access to Google Search Console, Bing Webmaster Tools and Google Analytics 4;
  4. not copying personal data from the Controller's systems to Querora's devices or into the Panel, other than the content of Tickets and the attachments added by the Controller;
  5. keeping login details in an encrypted password manager;
  6. the ability to roll back every change shipped on the Client Website;
  7. removing access within 7 days of the end of the Contract.

6.Sub-processors

6.1.

The Controller gives Querora general authorization to use sub-processors from the following categories:

CategoryScopeLocation
Server providerstoring Panel data, including Tickets with attachments, and Querora's email serverPoland
Browser push services: Google, Mozilla, Apple, Microsoftdelivering a notification, for example with a Ticket subject, only when a User turns notifications onalso outside the EEA
6.2.

Email runs on Querora's own server at the server provider listed above, without a third-party email service.

6.3.

We give at least 14 days' notice by email before adding or replacing a sub-processor. During that time the Controller may object, and if we do not reach an agreement, terminate the Contract effective on the date of the change, at no extra cost.

6.4.

A sub-processor is bound by data protection obligations no weaker than those in the DPA, and Querora is liable for its actions as for its own.

6.5.

Data is transferred outside the EEA only on the basis of a European Commission adequacy decision or standard contractual clauses.

6.6.

Google, Microsoft, the CMS provider and the hosting of the Client Website are not Querora's sub-processors. The Controller uses them under its own agreements.

7.Personal data breaches

7.1.

Querora notifies the Controller of a breach involving the entrusted data without undue delay and no later than 48 hours after becoming aware of it, by email to the account owner.

7.2.

The notification includes the information listed in Article 33(3) GDPR, to the extent available. Anything else is sent as soon as it is known.

7.3.

Querora takes steps to limit the effects of the breach and documents them.

8.Data subject rights

8.1.

A request from a data subject sent to Querora about the entrusted data is passed on to the Controller within 3 Business Days, and we do not answer it ourselves unless the Controller asks us to.

8.2.

On the Controller's instruction we help carry out the request, in particular by finding, correcting or deleting data in the systems of the Client Website.

9.Audits

9.1.

At the Controller's request we provide information about the processing and the security measures within 14 days.

9.2.

The Controller may carry out an audit once a year, and also after a personal data breach, with at least 14 days' notice. The audit takes place in support hours, without access to other clients' data, and is paid for by the Controller unless it shows a breach of the DPA.

10.End of processing

10.1.

Within 30 days of the end of the Contract, Querora deletes the entrusted data, and on a request made by the Controller before the Contract ends returns it in an agreed format. It also removes its access to the Client Accounts within the time in clause 5.1.

10.2.

We confirm the deletion by email. This does not apply to data we must keep under the law.

11.Liability and final provisions

11.1.

The parties are liable for damage caused by an infringement of the GDPR under Article 82 GDPR. The limitation of liability in clause 13.2 of the Terms applies to the extent the law allows.

11.2.

Matters not covered here are governed by the Terms, the GDPR and Polish law.

11.3.

This DPA is effective from 24 October 2026.