Data processing agreement
Version dated 15 October 2026 · annex to the QRelay terms
1. Parties and scope
The controller of entrusted data is the QRelay user determining its processing purposes and means, identified through their account details, referred to as the Controller. The processor is Sebastian Kula, Wólka Zdunkówka 60, 21-310 Wohyń, Poland, operator of QRelay, referred to as the Processor. The parties communicate through the Controller’s account email and the Processor’s sebastian.kula.24.12@gmail.com.
This agreement and its annexes form part of the accepted terms for processing on the Controller’s behalf under GDPR Article 28(3) and (9). No separate paper signature is required. It does not alter QRelay’s controller role for its own account, billing, correspondence and security data, or Stripe/Link’s payment role. If the user is itself a processor, it confirms authority to engage a subprocessor and supplies the instructions binding it.
2. Purpose, instructions and Controller duties
The Processor processes data solely to host and publish QR codes and menus, provide requested statistics, deliver technical support and carry out Controller-requested operations. Documented instructions comprise account settings and actions, this agreement and verified email requests, including instructions on transfers outside the EEA. The Processor does not use entrusted data for its own marketing, model training or other self-determined purposes.
The Controller ensures a legal basis, accurate data, required privacy notices and lawful instructions. Publishing a menu or setting a QR destination instructs the Processor to disclose that content to people opening the link. Confidential information should not be included. Only ordinary data necessary for the service is covered, as set out in Annex A; GDPR Article 9 or 10 data must not be entrusted without separate agreement.
If EU or Member State law requires processing, the Processor informs the Controller before acting unless that law prohibits it. The Processor promptly notifies the Controller of instructions it considers to infringe data protection law and suspends the unlawful part pending clarification.
3. Confidentiality and security
The Processor grants access only to authorised persons within their duties who are bound by confidentiality or an appropriate statutory obligation. Confidentiality continues after access ends. It selects risk-appropriate technical and organisational measures under GDPR Article 32 and maintains their effectiveness; current measures are described in Annex B.
Security changes must not lower protection of entrusted data. The Processor cooperates in assessing whether planned processing fits the available safeguards. If the Controller requires additional measures based on its risk assessment, the parties agree them before that processing starts.
4. Assistance and data subject rights
Taking account of the nature of processing, the Processor assists through appropriate measures with GDPR Chapter III requests, including locating, providing, correcting, restricting and deleting entrusted data. Requests received directly from individuals are forwarded to the Controller without undue delay and are not decided independently unless authorised or legally required.
Taking account of available information, the Processor assists with GDPR Articles 32–36: security, breach assessments, notifications to authorities and individuals, impact assessments and prior consultation. It provides necessary information and technical assistance without taking over the Controller’s decisions or obligations.
5. Personal data breaches
On becoming aware of a breach of entrusted personal data, the Processor notifies the Controller without undue delay at the account email, without waiting for complete information. The notice includes available details of the nature of the breach, affected categories and approximate numbers of people and records, likely consequences, measures taken or planned and a contact point. Further information is provided in stages. The Processor records the incident and takes mitigating action.
The Controller keeps its contact address current and assesses its own obligation to notify the competent authority, including the GDPR Article 33 72-hour deadline, and affected individuals. The Processor’s notice does not replace these actions.
6. Subprocessors and transfers
The Controller grants general written authorisation for subprocessors necessary to provide the service, with the current list in Annex C. The Processor binds each subprocessor to at least equivalent data protection obligations and remains liable to the Controller for that subprocessor’s performance.
The Processor emails at least 14 days before adding or replacing a subprocessor, providing identity, country, scope and safeguards to allow a reasoned objection. The parties seek a secure solution; if none is possible, the Controller may end the affected service before entrustment, with unused fees settled and data returned or deleted. Publishing a new name on a webpage alone does not replace notice.
Transfers of entrusted data outside the EEA require a documented instruction and a valid GDPR Chapter V basis, such as an applicable adequacy decision or standard clauses with necessary safeguards. The Processor provides transfer and safeguard information. Subprocessor authorisation is not unlimited transfer authorisation.
7. Information and audit
The Processor makes available information needed to demonstrate GDPR Article 28 compliance and allows and contributes to audits, including inspections by the Controller or its authorised auditor. Routine audits are arranged with reasonable notice while protecting confidentiality and other customers’ data. This does not restrict supervisory powers or urgent post-incident checks. Organisational arrangements must not prevent effective verification.
8. Duration, return and deletion
Processing lasts while data is retained on the Controller’s instructions under the account contract, including Free after Pro ends. When the relevant service ends, the Controller chooses return in a commonly used format or deletion, through the panel where available or by email. The Processor fulfils that choice without undue delay, normally within 30 days, and deletes existing copies unless the law requires retention.
Until technical copies are overwritten in the hosting cycle, data is isolated from ordinary use and is not republished; completed deletions are reapplied after restoration. On request, the Processor explains the cycle and confirms fulfilment of instructions. The SEOHOST agreement provides for deletion of the last backup no later than 6 months after hosting ends. This is not an extra period of ordinary data use after an account closes.
Annex A. Processing details
Subject and purpose: storing, organising, displaying, modifying and deleting QR-code and menu content, operating statistics and necessary technical copies to provide QRelay. Individuals: the Controller’s representatives, staff and contacts, others it names in content, and exceptionally scanners only where the Controller itself gives an event identifying context.
Data types: names, job titles, work emails, phone numbers or other ordinary contact data if added by the Controller to names, descriptions, public menus or destinations; potentially identifying code-and-time context. Duration: as stated in section 8. QRelay statistics do not collect guests’ locations, card data, restaurant orders or behavioural profiles.
Annex B. Safeguards
HTTPS transport; password hashing; session cookies with HttpOnly, SameSite and Secure under HTTPS; CSRF tokens for changes; code and menu account-ownership checks; parameterised database queries and output encoding; login, registration and password-reset rate limits; administrative access limited to service maintenance; backups and infrastructure protection at the hosting provider.
The service includes public display of selected content. Account safeguards do not make a published menu confidential. The Processor reviews safeguards according to risk and updates them when threats or functions change. Detailed information needed for a security assessment is provided to the Controller under confidentiality.
Annex C. Subprocessors
SEOHOST sp. z o.o., ul. Obornicka 330, 60-689 Poznań, Poland — hosting, database, backups, technical mail and infrastructure. Its infrastructure chain may involve DATASPACE P.S.A., EXEA S.A. and OVH sp. z o.o. in Poland; SEOHOST support cases may involve Quality Unit, s. r. o. in Slovakia. Participation and access depend on the service and support case. Contact for this chain: bok@seohost.pl, or the QRelay Processor contact in section 1.
Google Ads and Stripe/Link described in the Privacy Policy handle optional QRelay advertising and its customers’ transactions respectively. That does not make them subprocessors for publishing entrusted menu data. Current recipient, scope and safeguard details are available on request; changes follow section 6.