Data processing agreement
The arrangements under Article 28 GDPR for the personal data in the contracts that you upload. This agreement is an annex to, and forms part of, the terms and conditions.
Nederlands (vertaling) · The English version is authoritative. If the language versions differ, the English version prevails.
1. Parties
This data processing agreement (the "data processing agreement") is an annex to, and forms part of, the terms and conditions of GuardMyContract. It is concluded between:
- the business or organisation on whose behalf the account was created (the "customer" or "controller"); and
- the business below (the "processor"), which offers the GuardMyContract service:
- Business: VD Graaf, a sole proprietorship (eenmanszaak)
- Trade name of the service: GuardMyContract
- Registered address: Schouwstraat 16, 4844 VP Terheijden, Nederland
- Chamber of Commerce (KvK) number: 69950105
- VAT identification number: NL002425870B03
- Email: support@guardmycontract.com
This data processing agreement takes effect at the moment the customer accepts the terms and conditions.
2. Definitions
"GDPR" is Regulation (EU) 2016/679. "Personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "subprocessor" have the meaning given in the GDPR. "Contract data" are the documents that the customer uploads (PDF files), the text extracted from them, the contract details found and the confirmations and corrections of the customer's users. "Service" is the GuardMyContract service as described in the terms and conditions.
3. Subject matter and allocation of roles
- This data processing agreement applies to the personal data that the processor processes on behalf of the customer when providing the service. For that processing the customer is the controller and the processor is the processor.
- The processor is itself the controller for the processing it carries out for its own purposes: managing accounts, securing the service (sessions, audit log, abuse prevention), answering support questions, being able to demonstrate accepted terms, and the administration and invoicing of the subscription. The privacy statement applies to that, not this data processing agreement.
- If the customer itself processes the contract data as a processor for its own principals, for example a property manager or owners' association (VvE) manager who manages contracts of third parties, then the processor is a subprocessor of the customer and this data processing agreement applies by analogy. The customer warrants that it is authorised to do so.
- The data of the customer's users (name, email address, role) are at the same time account data of the processor and data over which the customer decides who has access. The privacy statement applies to that data.
- For payments for the subscription, Stripe is independently responsible for what Stripe does for its own purposes and a processor for the rest, according to Stripe's terms. Stripe is not a subprocessor for contract data.
4. Duration
This data processing agreement lasts for as long as the processor processes personal data for the customer, also when the subscription has ended but the data is still being kept (see "Deletion and return").
5. Nature and purpose of the processing
The processor processes the personal data solely to provide the service to the customer: storing the uploads, extracting contract details from the text with the help of AI and, at the request of the customer's users, making summaries and analyses of clauses and risks, calculating cancellation deadlines and renewal dates, showing the data to the customer's users, sending reminders by email and making backups. The details are in Annex 1.
6. Instructions of the customer
- The processor processes the personal data only on the basis of documented instructions from the customer. Instructions are: the terms and conditions, this data processing agreement, the use of the service by the customer's users and written requests via support@guardmycontract.com.
- If the processor is required to carry out a processing by Union or Member State law, it informs the customer of that beforehand, unless the law prohibits this.
- If, in the processor's opinion, an instruction infringes the GDPR, the processor informs the customer without delay.
- The processor does not use the contract data for its own purposes and does not use it to train AI models itself. The terms of the AI provider apply to the AI provider (Annex 2).
7. Confidentiality
- The processor and everyone who has access to the personal data under its authority is bound by confidentiality.
- Access to production data is limited to those who need it for the service. The internal administration console for account and subscription management is used only locally by the operator and is not publicly reachable; it shows organisation name, KvK and VAT number, address and member details (name, email address, role), but no contract content.
8. Security
The processor takes appropriate technical and organisational measures as referred to in Article 32 GDPR. The measures that are currently in place are in Annex 3, including the known limitations. No system is completely secure; Annex 3 is a description and not a certification or guarantee.
9. Subprocessors
- The customer gives the processor general authorisation to engage the subprocessors in Annex 2.
- The processor announces an intended addition or replacement of a subprocessor at least 30 days in advance, by email to the email address of the account. The customer may object in writing, with reasons, within 14 days. If the parties do not reach agreement, the customer may cancel the subscription effective at the end of the current paid period.
- The processor imposes on each subprocessor, by way of a contract or other legal act under Union or Member State law, the same data protection obligations as set out in this data processing agreement, as Article 28(4) GDPR requires; this includes the duty to provide sufficient guarantees for appropriate technical and organisational measures. Many subprocessors work with fixed standard terms that the processor cannot unilaterally change; the processor relies on those terms. The processor has not independently verified for each subprocessor in Annex 2 that those terms contain all the obligations of this data processing agreement and gives no guarantee in that respect.
- The processor remains liable to the customer for the performance by its subprocessors (Article 28(4) GDPR), with application of the "Liability" article to the extent the law allows and without prejudice to Article 82 GDPR.
10. Transfers outside the European Economic Area
- The processor transfers personal data outside the EEA only to the extent necessary for the subprocessors in Annex 2 and with an appropriate safeguard under Chapter V GDPR.
- This concerns the AI provider (page text and original file name of a contract) and the email provider, who may process data in the United States. According to the processing terms of those parties, the safeguards are the standard contractual clauses of the European Commission. The processor has not independently verified this and gives no guarantees about those parties' compliance.
- The processor does not itself conclude additional standard contractual clauses with the customer and does not rely on an adequacy decision.
11. Rights of data subjects
- The processor assists the customer, taking into account the nature of the processing, in responding to requests from data subjects (access, rectification, erasure, restriction, portability, objection).
- If the processor receives a request directly from a data subject about contract data, it refers the data subject to the customer and reports the request to the customer, to the extent the data subject can be identified. The processor does not respond to the request itself.
- An owner or administrator of the customer can export the contract data in the service at any time (Settings, Your data). The service has no self-service function for deleting an account. The customer makes other requests via support@guardmycontract.com; the processor handles them manually. An owner or administrator can, however, permanently delete a contract within the service.
12. Personal data breaches
- If the processor establishes a personal data breach that concerns the customer's personal data, it notifies the customer without undue delay. As an internal target, the processor informs the customer within 48 hours after it has established the breach.
- The notification contains, to the extent known: the nature of the breach, the categories and approximate numbers concerned, the likely consequences, the measures taken or proposed and a contact person. Missing information is sent as soon as it is available.
- The customer, as controller, assesses whether it must report the breach to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) or to data subjects; the processor gives the cooperation that is reasonably requested.
13. Assistance
The processor assists the customer, taking into account the nature of the processing and the information available, with the obligations under Articles 32 to 36 GDPR (security, notifications, data protection impact assessment and prior consultation). The reasonable costs of assistance that goes beyond the service itself may be charged after prior notice.
14. Information and audits
- The processor makes available the information necessary to demonstrate that it complies with Article 28 GDPR, and cooperates with audits, including inspections, by the customer or an auditor appointed by it.
- An audit takes place at most once a year, after at least 30 days' written notice, under confidentiality, without unreasonable disruption of the service and at the customer's expense. The processor's documentation is assessed first.
- The processor runs on the server of a hosting provider and stores backups with another provider. The processor cannot enforce an audit at those subprocessors themselves; it provides the reports and certifications that the subprocessors make available to it.
15. Deletion and return
- The customer can at any time ask via support@guardmycontract.com for the return or deletion of the contract data. Return is done manually, in a commonly used format (the original PDF files and the details found).
- The processor handles a request from the customer to delete the account or the organisation manually. An owner or administrator can delete a contract earlier; it is then permanently deleted immediately.
- The processor records the actual end of the customer's access (the end of the paid period, of the payment period after a failed payment, or of an access code) separately. As soon as the processor establishes that the access has ended and therefore terminates the organisation, a period of 30 calendar days begins in which the customer can ask for the return of the contract data. The processor normally checks this every hour; after an outage or a later activation of this procedure, the period of 30 days always begins only at the moment the organisation is terminated.
- After that period the processor deletes the contract data and the associated data of the organisation with the deletion procedure. The processor aims to complete this within 48 hours after the period ends; that is an aim and not a guarantee. If the deletion cannot be completed in time because of a technical fault, a controlled manual procedure follows. The processor does not send an automatic warning or reminder beforehand. If the customer takes out a new subscription before the deletion and the deletion has not yet started, the organisation is restored; once the deletion has started, that is no longer possible.
- For an organisation whose only access was a free trial, the processor deletes the contract data automatically 30 days after the trial ends, never earlier and possibly later, as described in the terms and conditions (Free trial, under Subscription, payment and access). The owner can ask for earlier deletion in the service.
- Encrypted backups are kept at OVHcloud. Newly uploaded backup files normally carry an Object Lock in governance mode of 30 days; this protects them against deletion or modification during that period, except by an authorised user who deliberately bypasses it. It is an additional safeguard and not an absolute guarantee, and not every earlier backup file necessarily has the same retention. Each backup is deleted automatically by a rule at the storage provider once it is 30 days old. The provider carries out that deletion with some delay; the processor checks that no backup is kept for longer than 35 days. The data may therefore remain in encrypted backups for up to about 35 days after deletion. Backups are used only to restore the service. If the processor has to restore a backup, it keeps the service unavailable until it has deleted again the data whose deletion it can establish: deletions that follow from the retention periods are repeated automatically. Deletions made after the backup, whether requested by the customer or carried out by the customer's users in the service (for example a deleted contract), are repeated as far as the processor's server records and stored files show them. If those are lost as well, for example when the whole server is lost, changes made since the most recent backup cannot always be reconstructed automatically: such a deletion may not be repeated automatically, and the customer may then have to carry it out or request it again. The AI provider keeps API input and output according to its own terms; the processor cannot guarantee the AI provider's deletion period.
- User accounts, audit data and invoice and subscription data have their own retention periods (see the privacy statement).
- Statutory retention obligations take precedence.
16. Liability
The processor's liability towards the customer under this data processing agreement follows the Liability article of the terms and conditions, to the extent the law permits. Liability that cannot be limited under mandatory law, and the rights of data subjects under the GDPR (including the right to compensation under Article 82 GDPR), remain unaffected.
17. Final provisions
- In the event of a conflict between this data processing agreement and the terms and conditions, this data processing agreement prevails, in so far as it concerns the processing of personal data.
- Changes to this data processing agreement follow the rules for changes to the terms and conditions, except that a change of subprocessors follows from "Subprocessors".
- Dutch law applies to this data processing agreement; disputes follow the Governing law and disputes article of the terms and conditions.
- These documents are available in English and Dutch. The English version is authoritative. If the language versions differ, the English version prevails.
- Contact about privacy: support@guardmycontract.com.
18. Annex 1. Details of the processing
| Item | Description |
|---|---|
| Subject matter | Providing the service: uploading contracts, extracting details, calculating deadlines, reminders and overviews |
| Duration | For as long as the processor keeps personal data for the customer (see "Duration" and "Deletion and return") |
| Nature of the processing | Storing (encrypted file and database), text extraction from PDF, AI analysis by a subprocessor (extraction of details and, on request, summaries and analyses of clauses and risks), calculation of dates, display, email, backup, deletion |
| Purpose | Performing the service for the customer and in accordance with its instructions |
| Categories of data subjects | Persons named in uploaded contracts, such as signatories, representatives and contact persons of counterparties and suppliers; and the customer's users (employees with an account) |
| Categories of personal data | From contracts: names, job titles, addresses, email addresses and telephone numbers to the extent included in the text of the contract; contract details (supplier, type, start and end date, notice period, renewal, value), the quoted passages, summaries and findings of analyses with short verbatim passages, and the original file name. From users: name, email address and role |
| Special categories | The service is not intended for special categories of personal data (Article 9 GDPR) or criminal data and does not ask for them. The text of uploaded contracts is not filtered for such data. |
| Storage location | Application, database and files on a server of the hosting provider (according to its statement in a Dutch data centre); encrypted backups with OVHcloud in the Paris region (France), which the processor chose itself |
| Retention periods | See "Deletion and return" and the privacy statement |
19. Annex 2. Subprocessors
A party is not a subprocessor for every processing activity; the role is stated per party. The safeguards for transfers are those in the processing terms of the party concerned. Locations and safeguards are the statements of those parties and the processor's configuration; the processor has not independently verified the processing agreements, locations, retention periods and certifications of these parties and gives no guarantees about them.
| Party | Activity for the customer | Personal data | Role and location |
|---|---|---|---|
| Anthropic | AI analysis of contract text via the Anthropic API (extraction of details and, on request, summaries and analyses of clauses and risks) | Page text of the contract and the original file name | Subprocessor; United States and possibly other countries; standard contractual clauses according to Anthropic's processing terms |
| Resend | Sending email: verification, password reset, support forwarding and contract reminders | Name and email address of the user; for reminders also the name and supplier of the contract and the relevant dates, no contract text or document | Subprocessor; United States; standard contractual clauses according to Resend's processing terms |
| TransIP (hosting provider) | Hosting of the server with application, database and encrypted files | All data of the service | Subprocessor; Netherlands |
| TransIP (domain and email) | Domain name, DNS and the mailbox for support messages | Support messages, also if a customer includes data in them | Processor for the processor's own administration; subprocessor to the extent customer data is in support messages; Netherlands |
| OVHcloud | Storage of encrypted backups | All data of the service, solely in encrypted form; OVHcloud does not have the key | Subprocessor; Paris, France |
| Stripe | Payments for the subscription | Invoicing and payment data of the customer; no contract data | Not a subprocessor for contract data; independently responsible and a processor for payments according to Stripe's terms |
20. Annex 3. Technical and organisational measures
Only what is currently built in or set up.
Access and confidentiality
- The data of each organisation is separated from the others in the database (row-level security), enforced by the database; membership is checked on every request.
- Roles (reader, editor, administrator, owner) determine what a user may do; only an owner or administrator can delete contracts.
- Passwords are stored only as a scrypt hash. Sessions are kept on the server and end after 12 hours of inactivity or after 7 days at the latest; after a password change other sessions are ended.
- Forms are protected against cross-site request forgery (CSRF); login attempts and other sensitive actions are limited (rate limiting).
- Important actions are recorded in an audit log to which the application can only append.
Encryption
- Each uploaded PDF file is encrypted with its own key (AES-256-GCM) before it is stored; the key is bound to the organisation and the document.
- The web server runs behind a reverse proxy with HTTPS; the application listens only on the server's local address.
- Backups are encrypted before they leave the server; the storage provider does not have the key.
Logging
- Application logs contain events and error codes and are set up so that no names, email addresses, IP addresses or contract text appear in them.
- The web server writes no access log. The operating system keeps system logs on a rolling basis; IP addresses may appear in them and no fixed retention period has been set.
Known limitations
- The page text extracted from PDFs, the quoted passages and the contract details found are stored in the database without additional encryption by the application.
- Two-step verification is not yet available and self-service for deleting an account is missing.
- There is no independent certification of the security.