Effective date: 3 October 2026.
Parties, applicability and precedence#
This DPA states the binding processor terms to be incorporated into a Quire customer order. The processor is Nuits, a Finnish sole proprietorship operated by Bapusaheb Patil, VAT ID FI35848458 (“Quire”). The customer identified in the accepted order is the controller of the personal data it entrusts to Quire, or a processor acting with its controller’s authority. In the latter case, references to the customer’s instructions mean instructions the customer is authorised to pass on, and Quire acts as a subprocessor. Each party’s contact and authorised instruction channels are recorded in the order and deployment schedule; Quire’s legal, privacy and incident contact is legal@quirelms.com.
This DPA applies when the parties accept an order incorporating it and agree the deployment schedule described below. Publication alone is not a signed customer order, authority to upload learners’ data or evidence that a hosted deployment exists. The current public offering is a waitlist and browser-local demo, not hosted learner processing.
Quire acts as an independent controller for its own waitlist, customer-contact, legitimate billing and business-administration records, as explained in its Privacy Policy. Those separate purposes do not authorise reuse of the customer’s learner records. A self-hosted licence alone does not give Quire access to the customer’s database. Where agreed remote support or a connected service involves processing on the customer’s behalf, its actual scope is covered by this DPA and the schedule before access begins.
Mandatory data-protection law and an executed transfer instrument take precedence for the matters they govern. This DPA and its deployment schedule prevail over general commercial terms on personal-data processing. No commercial term may reduce data-subject rights or the processor obligations set out here. Terms such as “personal data”, “controller”, “processor”, “processing” and “personal data breach” have their GDPR meanings where that law applies.
Deployment schedule required before processing#
Before Quire processes customer personal data, the parties must sign or otherwise accept in writing a completed, deployment-specific schedule. It must identify:
- The customer and any upstream controller, authorised contacts, start date, service and supported modules, processing term and lawful instruction channels.
- The selected hosting, storage, support and backup locations, including remote-access countries, and any customer-imposed residency restriction.
- The actual legal entities engaged as subprocessors, their tasks, data access, processing countries and the applicable authorisation mechanism.
- The data subjects and personal-data categories actually needed, any permitted sensitive data and additional safeguards, and the presence of children and approved authority for their onboarding.
- Enabled optional email, AI, video, payment, analytics and other integrations, their recipients, roles, retention and whether the customer or Quire contracts with them.
- The operational security, backup and restoration arrangements, customer retention instructions, export arrangements and any necessary international-transfer instruments and assessments.
These requirements are a condition of commencement, not an invitation to leave a blank annex or select an unknown provider after processing begins. The substantive baseline below applies in every covered deployment; the schedule narrows the actual scope and records verifiable implementation. Quire must not begin processing where the required supplier, location, security or lawful child-data arrangements are unresolved. A change expanding the scope requires documented agreement and any necessary new authorisation first.
Subject matter, purposes, nature and duration#
The subject matter is operation and support of the contracted learning-management deployment. The purposes are to administer authorised accounts, organisations and courses; deliver teaching and learning activities; record submissions, assessments, progress and credentials; provide authorised communications, accessibility settings and reporting; and secure, maintain, support, export and wind down that service. Optional AI or other integrations are included only if specifically enabled and approved in the schedule. Data must not be used for advertising, sale, unrelated profiling or unrelated model training.
The nature of processing includes receiving and importing data, organising and storing it, authenticating users, retrieving and displaying authorised records, calculating instructed learning results, delivering messages, providing permitted integration transfers, logging necessary actions, backing up, exporting, restricting and deleting data. Processing may occur continuously during the contracted service and only as needed for agreed support and return/deletion afterwards.
Processing lasts for the order’s service term and the limited export, deletion and lawful-retention periods below. Before collection, the customer specifies in the schedule any shorter record-specific retention, academic preservation duty or lawful hold. The existence of a configurable software default does not itself establish the customer’s lawful retention period.
Data subjects and categories#
Data subjects may be learners, educators, assessors, administrative staff, authorised institution contacts and guardians where approved. Public visitors are included only if the contracted deployment needs their data. Children are included only through approved institutional onboarding and the child-data safeguards below.
Depending on the agreed modules, personal data may include:
- Identity and account data: names, contact details, institutional identifiers, roles, language, time zone, authentication and access records, and age or guardian-authority information where needed.
- Educational records: enrolment, courses, attendance, progress, submissions, quiz attempts, grades, feedback, credentials and instructed educational engagement indicators.
- Communications and content: course discussions, messages, authored material, uploads and delivery records.
- Preferences and transaction references: accessibility and account settings, consent and notice evidence, and institution-related orders or payment references where enabled. Payment-card processing is not authorised merely by listing transaction references here.
- Technical and accountability data: IP address, device or user-agent information where collected, session records, security and audit events, and authorised support requests.
- Approved AI inputs and outputs: prompts, selected course context, submissions or other instructed content, responses and review records, only within the approved feature and provider scope.
The schedule identifies which of these categories are actually processed. Free text and uploaded files may contain personal data; a feature label does not automatically redact or anonymise them. Special-category data, criminal-offence records, highly sensitive health records and biometric identification data are excluded unless separately agreed with the customer’s lawful authority, strict minimisation, access restrictions, retention and additional security. Ordinary accessibility settings must not be treated as authority to collect medical diagnoses; where a preference itself reveals protected information, the customer must address the lawful basis and safeguards before collecting it.
Documented instructions and confidentiality#
Quire processes personal data only on the customer’s documented instructions, including instructions about international transfers, unless EU or Member State law binding on Quire requires otherwise. Where law requires other processing, Quire will notify the customer of that requirement before processing unless the law prohibits notice on important public-interest grounds. The order, schedule, authorised configuration and recorded support instructions constitute documented instructions within their agreed scope.
Quire will immediately inform the customer if, in its opinion, an instruction infringes the GDPR or other applicable EU or Member State data-protection law, and suspend the affected instruction while the parties resolve it. The customer remains responsible for its purposes, lawful basis, transparency, authority, accuracy and minimisation, without relieving Quire of its own obligations.
Quire limits personnel access to those who need it to perform the service. Authorised persons must be subject to an appropriate contractual or statutory confidentiality duty, receive appropriate data-protection and security instruction, and retain that duty after their access ends. Support access is limited to the authorised task; unnecessary copies and reuse are prohibited.
Security measures and evidence boundaries#
Quire will implement appropriate technical and organisational measures under Article 32, taking account of the state of the art, implementation cost, processing context and risk to individuals. Measures must be implemented and documented for the chosen deployment before personal data is introduced, maintained during processing and reviewed when risks or services change. Changes must not materially reduce the agreed level of protection.
The application includes tenant-scoped permissions and data access; configurable authentication, session controls and MFA capabilities; encryption mechanisms for stored integration credentials and authentication tokens; security/audit event records; rights and retention workflows; and configurable residency and integration checks. Those capabilities depend on configuration and operation. They do not prove that every deployment has mandatory MFA, encryption of all stored files and databases, malware scanning, a fixed region or functioning backup jobs.
For each contracted deployment Quire must, at minimum:
- Protect public network connections with TLS and isolate untrusted uploaded content from the authenticated application origin.
- Enforce least-privilege tenant and administrative access, protect operator credentials, review authorised access and revoke access when no longer needed.
- Protect integration secrets using the available encryption controls and document protection and key management for the selected data stores and backups.
- Operate proportionate logging, vulnerability and update management, incident handling, backup and restoration procedures, with retention and access controls appropriate to the data.
- Document the actual backup locations, retention and restoration checks, and any scanning or network egress controls needed for the agreed risks.
- Apply configured residency restrictions to approved recipients and remote access, rather than relying solely on application metadata describing a provider’s region.
The deployment schedule supplies the actual storage protections, operational ownership and additional measures for the customer’s risks. Optional scanning, offsite encryption, MFA or a particular recovery target must not be represented as active solely because the software supports it. Quire does not claim an ISO, SOC, FERPA or other certification through this DPA.
Subprocessors, authorisation and objection#
The customer gives general written authorisation only for the actual subprocessors in the agreed deployment schedule and current customer-specific register. No vendor is authorised merely because it appears in documentation or an adapter catalogue. Quire must assess each selected subprocessor’s ability to meet the required safeguards and enter a written agreement imposing substantially the same applicable data-protection obligations. Quire remains responsible to the customer for that subprocessor’s performance of those obligations.
Quire will specifically notify the customer’s designated contact in writing at least 30 days before adding or replacing a subprocessor, identifying its legal entity, role, data access, locations and relevant safeguards. The customer may object within that period on reasonable data-protection grounds. Quire will investigate and seek a suitable alternative or mitigation and will not give the proposed subprocessor access to the objecting customer’s data while the objection is unresolved.
If no lawful, reasonable solution is available, either party may terminate the affected processing or service before that subprocessor receives the customer’s data. Quire will refund prepaid fees for the unused affected service and provide return/deletion assistance. A necessary urgent change is not permission to bypass authorisation; Quire must obtain specific written agreement or suspend the affected processing. Changes that expand a subprocessor’s purpose, countries or data access are subject to the same notice and objection process.
Quire maintains an up-to-date register and, on reasonable request, provides relevant subprocessor terms, allowing redaction only where needed to protect secrets or other individuals, not to conceal the applicable safeguards. See the Subprocessor notice for the distinction between current static-site delivery and future customer deployment suppliers.
International transfers#
Quire will not transfer customer data to, or allow remote access from, a country outside the agreed locations without documented instructions, required subprocessor authorisation and a lawful transfer basis. Where GDPR Chapter V applies, the parties must establish an applicable adequacy decision or other valid safeguard before the transfer, including properly executed standard contractual clauses where appropriate, completed parties and annex information, required transfer assessment and supplementary measures. UK or other transfer rules must also be addressed where applicable.
This published DPA is not an executed set of international-transfer clauses, does not identify an unselected data importer and does not claim that vendor SCCs or transfer assessments already exist. A link to official clauses or an asserted provider region is not a substitute for the required instrument and actual operational controls. Quire will notify the customer of a government request concerning its data where lawful, assess the request, and limit disclosure to what is legally required.
Assistance with rights and regulatory duties#
Taking account of the nature of processing, Quire will assist the customer through appropriate technical and organisational measures with access, correction, erasure, restriction, portability, objection and other applicable data-subject requests. Quire will promptly forward a request it receives about customer-controlled data and will not substantively answer it except on documented authority or where law requires it. The customer verifies identity and decides the lawful response; Quire supplies available records, exports, scoped corrections or restrictions and necessary information without undue delay so the customer can meet its legal deadlines.
Quire will also assist, taking account of the processing and information available to it, with security obligations, breach assessment and notifications, data-protection impact assessments and prior consultation with supervisory authorities under Articles 32 to 36. This includes relevant architecture, processing and recipient information, security evidence, incident facts and risk-mitigation information. Quire will inform the customer without delay if it becomes aware that instructed personal data is inaccurate or outdated.
Self-service tools do not replace this assistance. Quire will explain limits such as lawful academic retention, third-party content, unavailable external copies or device-held offline data and coordinate the appropriate action rather than claim an export or erasure tool covers every system. Any agreed charge for unusually extensive customer-requested work must be reasonable and disclosed in advance; necessary statutory assistance must not be withheld for an unagreed charge, and Quire bears remediation costs attributable to its own breach.
Personal data breaches#
Quire will notify the customer without undue delay after becoming aware of a personal data breach affecting covered data. It will not wait for a complete investigation. Initial notice goes to the customer’s designated incident contact and includes available information about the breach’s nature, affected data and individuals, approximate numbers where possible, likely consequences, containment or proposed mitigation, and a contact for further information. Quire will provide additional information in phases without undue delay as it becomes available.
Quire will contain and investigate the incident, preserve appropriate evidence, document relevant facts and remedial action, and cooperate with the customer’s assessment, authority notification and communications to individuals under Articles 33 and 34. The customer decides and makes its controller notifications unless law independently requires Quire to notify. The controller’s statutory reporting deadline is not a permission for Quire to delay its own notice until that deadline. Quire’s incident contact is legal@quirelms.com.
Information, audits and inspections#
Quire will make available all information necessary to demonstrate its compliance with Article 28 and this DPA, maintain required processing records and permit and contribute to customer or mandated independent-auditor audits, including inspections where appropriate. The parties will ordinarily arrange reasonable advance notice, confidentiality and measures to avoid disrupting other customers or exposing their data. Those arrangements cannot prevent a necessary audit, regulator access or urgent inquiry following a breach or credible non-compliance concern.
Existing relevant evidence may be reviewed first, but a report or questionnaire does not extinguish the customer’s audit right. Quire will answer reasonable processing inquiries promptly, cooperate with competent supervisory authorities and remedy substantiated deficiencies. No nonexistent certification or independent report is offered as proof. Reasonable audit-cost arrangements may be agreed in advance; Quire bears costs of addressing its own non-compliance, and charges must not frustrate statutory audit rights.
Return, deletion and termination#
At the customer’s choice, Quire will return the covered personal data and delete existing copies, or delete the data, after the processing service ends, unless EU or Member State law requires storage. The customer has a 30-day hosted export opportunity after termination; it may instruct earlier return or deletion. Quire will arrange an available structured export and necessary files, identify any format or third-party limitations and provide reasonable transition assistance.
Quire will complete deletion from live hosted systems within 60 days and remaining backups within 90 days after termination, unless a lawful documented instruction or mandatory retention duty requires otherwise. Where backup copies cannot be individually removed earlier, they remain protected and out of normal use until their scheduled deletion; any restoration must reapply pending deletion instructions. Quire will provide written confirmation of completed return or deletion on request and identify the legal basis, retained scope and expected end of any mandatory hold. These are operational commitments, not proof of fully automated deletion. DPA protection continues until all covered data has been returned or deleted.
Self-hosted customer-held copies, local device caches and providers directly engaged by the customer remain under the customer’s control. Quire will assist within its actual access and agreed scope; it cannot claim to delete copies it does not control.
The customer may require suspension of non-compliant processing. Quire will promptly state if it cannot meet this DPA. The customer may terminate affected processing for substantial or persistent breach, failure to comply with a binding data-protection decision, or a suspension whose underlying non-compliance is not cured within a reasonable time and no later than one month. If the customer insists on an unlawful instruction after being informed, Quire may terminate the affected processing. Return/deletion, appropriate unused-fee refunds and mandatory rights are preserved.
Schools and children#
Under-13 data may be processed only after approved institutional onboarding verifies the school’s or parent’s lawful authority and the parties sign a child-data agreement setting the educational purpose, notices, authorised recipients, review/access/deletion routes, retention and safeguards. Where COPPA permits school consent, it is limited to the school-authorised educational context and cannot authorise advertising or unrelated commercial purposes. Quire retains its own operator responsibilities; schools cannot assume them away by accepting terms.
For student education records where FERPA applies, the deployment must establish the relevant lawful basis, including required institutional control, purpose and disclosure limits if relying on the school-official exception. Quire will use records only for the authorised service, follow the institution’s lawful instructions and prohibit unauthorised redisclosure. These commitments are not a FERPA certification or a claim that every school deployment automatically qualifies for an exception.
Quire will not sell or share child data for advertising, build advertising profiles or use it for unrelated model training. AI and optional third-party sharing remain disabled for children until individually assessed and approved in the deployment agreement. Approval cannot waive a legal prohibition or replace required parent consent, school notices, security or retention controls.
Legal framework#
This is an individually stated processor agreement, not a claim to have executed the European Commission’s standard clauses. Its Article 28 obligations can be compared with the Commission’s controller–processor clauses in Decision 2021/915, which themselves do not supply a Chapter V transfer basis. Finnish law and the dispute provisions of the Terms of Service govern the customer contract without limiting mandatory data-protection law, supervisory-authority powers or data subjects’ remedies.