QuoteDrive Data Processing Agreement
Part of the QuoteDrive terms of service. Last updated: October 23, 2026.
Parties and scope
This Data Processing Agreement ("DPA") forms part of the QuoteDrive terms of service ("Agreement") between the customer that accepted the Agreement ("Customer", "Controller") and Modernaus ugdymo centras, UAB, Lithuania ("Provider", "Processor"). It applies whenever the Provider processes personal data on behalf of the Customer in the course of providing the QuoteDrive service ("Service").
1. Definitions
"GDPR" means Regulation (EU) 2016/679. "Personal Data", "Processing", "Controller", "Processor", "Data Subject", "Personal Data Breach" and "Supervisory Authority" have the meanings given in the GDPR. "Customer Data" means the documents the Customer submits to the Service (through its Google Drive folder, by email or otherwise), the data the Service extracts from them, and the Customer's account data. "Sub-processor" means any third party engaged by the Provider to process Customer Data. "Applicable Data Protection Law" means the GDPR and the Law on Legal Protection of Personal Data of the Republic of Lithuania and, where applicable, the UK GDPR.
2. Roles and scope
2.1 The Customer is the Controller of Customer Data and the Provider is its Processor. The Customer determines the purposes and means of the Processing; the Provider processes Customer Data only to provide the Service.
2.2 The Customer warrants that it has a lawful basis to collect the Customer Data and to have it processed by the Provider as described in Annex I, and that it has given any notices required by Applicable Data Protection Law to the Data Subjects, including persons named in supplier and client documents.
2.3 Where the Provider processes personal data for its own purposes (the Customer's account, billing, security logs, product analytics), it acts as an independent Controller under its privacy policy; this DPA does not apply to that processing.
3. Instructions
3.1 The Provider processes Customer Data only on documented instructions from the Customer. The Agreement, this DPA and the Customer's use of the Service (placing a document in the intake folder, forwarding an email, choosing settings) are the Customer's complete instructions.
3.2 The Provider will inform the Customer without delay if, in its opinion, an instruction infringes Applicable Data Protection Law, and may suspend the instruction until it is confirmed or withdrawn.
3.3 The Provider will not process Customer Data for its own purposes, will not sell it, and will not use it to train or improve machine-learning models. The AI models used to read documents are accessed under enterprise terms under which the model provider does not use Customer Data for training (Annex III).
4. Confidentiality
The Provider ensures that persons authorised to process Customer Data are bound by confidentiality obligations (contract or statute) and receive appropriate data-protection training. Access to Customer Data by Provider staff is limited to what is needed to operate the Service, to fix a problem the Customer reported or to investigate security incidents, and such access is logged.
5. Security
5.1 The Provider implements the technical and organisational measures described in Annex II, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the Processing, as well as the risks for Data Subjects.
5.2 The Provider may update the measures from time to time, provided the updates do not reduce the overall level of protection.
5.3 The Customer is responsible for the security of its own Google account, its Drive folders and sheets, the people it shares them with, and the content it submits.
6. Sub-processors
6.1 The Customer gives general authorisation to the Provider to engage the Sub-processors listed in Annex III.
6.2 The Provider will give the Customer at least 14 days' notice before adding or replacing a Sub-processor, by email to the account's address or by a notice in the Service, during which the Customer may object on reasonable data-protection grounds. If the parties cannot resolve the objection in good faith, the Customer may terminate the Agreement for the affected Service and receive a refund of unused purchased credits.
6.3 The Provider imposes on each Sub-processor, by written contract, data-protection obligations no less protective than those in this DPA, and remains fully liable to the Customer for the Sub-processor's performance.
7. International transfers
7.1 The Provider stores Customer Data in the European Union (Annex III lists the locations).
7.2 Where a Sub-processor processes Customer Data outside the EU/EEA, the Provider ensures an adequate safeguard under Chapter V of the GDPR: an adequacy decision (including the EU–US Data Privacy Framework for certified US providers) or the EU Standard Contractual Clauses (Commission Decision 2021/914), together with any supplementary measures needed.
7.3 For Customers subject to the UK GDPR, the UK International Data Transfer Addendum applies to such transfers.
8. Assistance to the Customer
8.1 Data-subject requests. The Provider will forward to the Customer without undue delay any request from a Data Subject that it receives concerning Customer Data, and will not answer it itself except to direct the Data Subject to the Customer. Taking into account the nature of the Processing, the Provider will assist the Customer with appropriate technical and organisational measures: the Customer's sheets, Drive folders and the export of extracted data give the Customer direct access to, and the ability to correct or delete, most Customer Data itself.
8.2 Compliance assistance. The Provider will assist the Customer, on request, with data-protection impact assessments and prior consultations with a Supervisory Authority insofar as they concern the Service, and with the Customer's security obligations.
8.3 Charges. Assistance that goes beyond the self-service features of the Service and the Provider's standard documentation is charged at EUR 200 per hour, unless the request results from the Provider's breach of this DPA.
9. Personal Data Breach
9.1 The Provider will notify the Customer without undue delay, and in any case within 72 hours, after becoming aware of a Personal Data Breach affecting Customer Data, by email to the account's address.
9.2 The notice will describe, as far as known at the time and supplemented as information becomes available, the nature of the breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point.
9.3 The Provider will cooperate with the Customer in investigating, mitigating and remedying the breach. Notifying Supervisory Authorities and Data Subjects remains the Customer's responsibility as Controller; the Provider will not notify them on the Customer's behalf unless required by law or agreed.
10. Deletion and return
10.1 The Customer's documents, sheets and folders in Google Drive belong to the Customer and remain in its own Google account; the Provider holds only working copies.
10.2 During the term, the Provider holds a working copy of a submitted file and the data extracted from it only until the file, its detail sheet and the register row are confirmed written to the Customer's Google Drive; at that moment the copy, the extracted data and the extracted values in the processing logs are deleted. A document that could not be processed keeps its working copy until the Customer resolves or deletes it. The activity record of each document (file name, Drive file id, times, outcome, credits used), without document content, is kept for 12 months as billing evidence.
10.3 On termination, on the Customer's deletion of its account in the Service, or on its written request, the Provider deletes all remaining Customer Data within 30 days, unless retention is required by EU or Member State law (in which case the data is kept only for that purpose and for that period). Backups are overwritten in the ordinary backup cycle, not later than 30 days after deletion.
10.4 The extracted data is in the Customer's own Google Sheets at all times; no export from the Provider is needed.
10.5 On request the Provider confirms deletion in writing.
11. Audits and information
11.1 The Provider makes available to the Customer all information reasonably necessary to demonstrate compliance with Article 28 of the GDPR: this DPA, its security overview, the Sub-processor list, and summaries of relevant third-party audit reports of its hosting providers.
11.2 Where that information is not sufficient to satisfy a legal requirement of the Customer, the Customer or an independent auditor bound by confidentiality may audit the Provider's processing of Customer Data, at most once in any 12 months (unless required by a Supervisory Authority or following a breach), on at least 30 days' written notice, during business hours, in a manner that does not disrupt the Provider's business or expose other customers' data. Audit rights belong to customers with an active account and concern their own data only. The Provider's reasonable costs of supporting an audit are charged at the rate in clause 8.3.
11.3 Audit results are confidential and shared with the Provider.
12. Liability
12.1 The liability of each party under this DPA is subject to the exclusions and limitations of liability in the Agreement, including the exclusion of liability for the accuracy and completeness of data extracted by the Service's automated reading, except that nothing limits a party's liability for a Data Subject's claim under Article 82 of the GDPR to the extent such limitation is not permitted by Applicable Data Protection Law.
12.2 Each party is liable only for the damage caused by processing that does not comply with its own obligations under the GDPR or this DPA.
12.3 For clarity: an error in extracted data (a misread field, amount, date or counterparty) is not a Personal Data Breach and not a breach of this DPA; the Customer checks extracted data before use, as the Agreement provides.
13. General
13.1 This DPA takes effect when the Customer accepts the Agreement and lasts as long as the Provider processes Customer Data. Clauses 4, 10 and 12 survive termination.
13.2 In case of conflict between this DPA and the Agreement, this DPA prevails for the Processing of personal data.
13.3 The Provider may update this DPA to reflect changes in law or in the Service by publishing the new version at this address with 30 days' notice; changes that materially reduce the Customer's protection require its consent.
13.4 This DPA is governed by the laws of the Republic of Lithuania; disputes are subject to the courts of Vilnius, without prejudice to the rights of Data Subjects and Supervisory Authorities under the GDPR.
13.5 The English version prevails over any translation. A signed copy of this DPA is available on request from support@quote.lt.
Annex I — Description of the Processing
Subject matter: reading business documents (invoices, receipts, statements, order confirmations and similar) that the Customer submits, extracting their data into spreadsheets in the Customer's Google Drive, and keeping those spreadsheets in sync.
Duration: for the term of the Agreement, plus the deletion period in clause 10.
Nature and purpose: receiving files from the Customer's Drive folder and intake email address; converting and reading them with automated text recognition and AI models; extracting structured fields; writing the results to sheets; moving processed files between the Customer's folders; reporting issues to the Customer's Issues sheet; billing by document.
Categories of Data Subjects: the Customer's staff who use the Service; the Customer's suppliers, clients and their contact persons; other persons named in the submitted documents (for example a delivery contact or a bank account holder).
Categories of Personal Data: names, job titles, business contact details (email, phone, address), registration and VAT numbers of sole traders, bank account numbers, invoice and payment details, order contents; for Customer staff: name, email address, Google account identifier, usage records.
Special categories: none intended. The Customer agrees not to submit documents containing special-category data (Article 9 of the GDPR, for example health data on medical or pharmacy invoices) or criminal-offence data; the Provider's security measures are not designed for them.
Frequency: continuous; documents are processed as the Customer submits them, usually within minutes.
Annex II — Technical and organisational measures
Access control: Customer accounts sign in with Google (OAuth 2.0, non-sensitive scopes: profile, email, drive.file). The Service reaches the Customer's Drive only through the folders it created and any folder the Customer explicitly shares with the Service's named processing account. Provider staff access to production is limited to named administrators with multi-factor authentication, and is logged.
Encryption: all connections use TLS 1.2 or higher. Data at rest is encrypted by the hosting providers (AES-256). Credentials stored for integrations are encrypted at the application level (AES-256-GCM) with keys held separately from the database.
Separation: every record carries the Customer's organisation identifier and queries are scoped to it. Production and development environments are separate; development uses synthetic or anonymised data.
Data minimisation and retention: a document's working copy, extracted data and log values are deleted the moment it is confirmed in the Customer's Drive (clause 10); activity records without document content are kept for 12 months.
AI processing: documents are read by models accessed under enterprise terms (Google Cloud Vertex AI) that prohibit the model provider from using inputs or outputs to train models and from retaining them beyond the request.
Availability: hosting on providers with redundant infrastructure; a database with point-in-time recovery; processing is idempotent, so a failed run can be repeated without duplicate results.
Monitoring and incident response: error and security monitoring on the application and hosting; a documented incident procedure with the notification window of clause 9.
Staff: confidentiality clauses in contracts; access revoked on departure; least-privilege roles.
Sub-processors: chosen for their certifications (ISO 27001, SOC 2) and bound by their data-processing terms (Annex III).
Secure development: code review, dependency updates, secrets kept in a secrets manager (never in code), automated checks before deployment.
Annex III — Sub-processors
Current as of the date at the top of this page. Changes are notified as set out in clause 6.
| Sub-processor | Role | Data | Location | Safeguard |
|---|---|---|---|---|
| Vercel Inc. | Application hosting, serverless functions, file storage | Customer Data in transit; working copies of files until they are in the Customer's Drive | Frankfurt, EU | Data processing agreement with SCCs; EU–US DPF certified |
| Neon Inc. | Database | Account data, extracted data, logs | Frankfurt, EU (AWS eu-central-1) | Data processing agreement with SCCs |
| Google Cloud EMEA Ltd (Vertex AI) | AI document reading | File contents during a request; not retained | Global (a request may be handled outside the EU) | Google Cloud Data Processing Addendum; no training on inputs; SCCs / EU–US DPF |
| Google LLC (Drive, Sheets, Workspace) | The Customer's own Drive and sheets; intake mailbox; outbound email | Files, sheets, emails | EU / US per Google Workspace terms | Google Workspace Data Processing Amendment; EU–US DPF |
| Stripe Payments Europe Ltd | Payments and invoicing | Customer billing data only; no documents | EU / US | Stripe Data Processing Agreement; SCCs |
| Upstash Inc. | Short-lived processing locks | No personal data (identifiers only) | EU | Data processing agreement |
| Vercel Analytics / Google Analytics | Product analytics | Pseudonymous usage data; no document data | EU / US | Data processing agreements; cookieless (Vercel) / consent (Google Analytics) |