Privacy Policy
Which personal data we process, why, with whom we share it, how long we keep it and which rights you have.
Nederlands (vertaling) · The English version is authoritative. If the language versions differ, the English version prevails.
1. Who we are
GuardMyContract is an online service with which organisations keep track of their contracts, notice periods and renewals (the "service"). In this privacy policy we explain which personal data we process, why, and which rights you have.
GuardMyContract is a product of the business below, a sole proprietorship. Where this policy says "we", it means that business.
- 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
For questions about privacy and to exercise your rights you can reach us at support@guardmycontract.com.
2. Our role
For your account, organisation, support, security and acceptance data we determine the purpose and the means of the processing ourselves. For that data we are the controller.
Contracts that you upload may contain personal data of other people, such as names or contact details of signatories and contact persons. We process that data on behalf of the organisation that uploads the contract, in order to provide the service. See also Personal data in your contracts.
3. Which data we process
Account data
When you create an account we ask for your name, your email address and a password. We never store your password itself: we only keep an irreversible hash (scrypt).
Organisation and membership data
The name of your organisation, who created the organisation and when, and which users are members with which role (owner, admin, editor or reader).
Uploaded contracts and documents
The PDF file that you upload, with its original file name, file size, a technical fingerprint (hash), the number of pages, the processing status and who uploaded the file and when.
Extracted contract information
- The text of each page of the contract.
- The contract data found, such as supplier, type of contract, start and end date, notice period, automatic renewal, renewal period, contract value, payment frequency and price indexation, each with the page number and the quoted passage where the data was found.
- Confirmations and corrections by users, with who made them and when.
- The dates that we calculate from it, such as cancellation deadlines and renewal dates.
- Technical data about the AI analysis: the provider and model used, the status and the number of tokens processed.
- Summaries and analyses of clauses and risks that you (depending on your subscription) have made for a contract: the text of the summary or of the findings, each with the page number and a short verbatim passage from the contract.
- Which notifications you have marked as read.
Support messages
If you use the support form: your name, email address, the subject, your message, your IP address and the time. We ask you not to put passwords or contract content in a support message. We keep the message in our database and forward it to our support mailbox.
Session and security data
- Your session: only a hash of the session code, when the session started, when it was last used and when it expires.
- One-time links for email verification and password reset: we only keep a hash of the one-time code, linked to your account, with its validity and the moment the code was used or revoked. We delete this data 30 days after the code has expired, been used or been revoked.
- Temporary counts to prevent abuse (rate limiting), per IP address, per email address (when logging in and resetting a password) or per user. For this we do not store the IP address or email address itself, but a value derived from it, hashed with a secret key, together with the times of the attempts, in our database. A count applies for at most one hour. Our clean-up runs every hour, so a count can remain in our database for up to about two hours, and longer if the clean-up is temporarily not running.
- Technical application logs with events and error codes. They are designed so that no names, email addresses, IP addresses or contract text end up in them.
- Our web server (Caddy) is not set up to store access logs, with one line per visit. The operating system of the server does record technical messages of the server itself and of the programs running on it, including the web server, such as start-up, errors and connections or login attempts on the server. IP addresses can appear in these system logs. They are meant for security and for resolving faults. No fixed retention period has been set: the operating system keeps them on a rolling basis and deletes the oldest messages as soon as the logs take up a set amount of disk space.
Audit and security log
We record important actions in an audit log: registration, logging in and failed login attempts, changes of name and password, creating an organisation, uploading and viewing documents, confirmations, corrections, deletions and requests for a new analysis. For each action we record who did it, when, and from which IP address.
Acceptance of the terms and conditions
When you create an account we record which version of the terms and conditions you accepted (currently terms-v3), the time, your IP address and your confirmation that you are creating the account on behalf of a business or organisation.
Registration and organisation data
When registering we ask, besides your name, email address and password, for details of your organisation: company name, KvK number, VAT number and registered address (street, house number, postcode, city and country).
Subscription and payment
Payments for subscriptions run through Stripe. You enter your payment details, such as card or bank details, with Stripe and they do not enter our own systems. Per organisation we only keep what is needed to link the subscription: the Stripe customer and subscription number, the chosen subscription and billing period, the status and the end date of the period. In addition, for access codes that you redeem we keep a reference to the code, the subscription it applies to and until when the access runs.
Stripe processes the payment under its own terms and privacy policy. All prices are exclusive of VAT; VAT is calculated at checkout and shown on your invoice. Stripe may also process data outside the European Union; see transfers below.
Email reminders
We keep your choices for reminders (on or off, 90, 30 and 7 days, language) with your account. For each reminder sent or planned we keep a record with only identification numbers, the date on which you have to act and the status, without names or contract text. We delete those records 400 days after that date, or earlier when the contract or your membership is deleted.
Free trial
If your organisation receives a free trial, we record when it started and when it ends and which user account started it, to apply the rule of one trial per organisation and per user account. For the emails about the trial (start, end and deletion reminders) we record which email was sent and when, to how many owners (by internal account number) and the message number of the email provider; never the content of the email.
Mandatory or voluntary
Website statistics (only with your consent)
If you accept analytics cookies, Google Analytics records on our public marketing pages: the pages you visit, how you reached them (the previous website and any campaign tags in the link), the time, your country, general technical details such as your browser language and type of device, and an online identifier stored in a cookie. According to Google, IP addresses of visitors in the European Union are only used to derive a general location and are then discarded. We send Google no names, email addresses, passwords, access codes or contract data. Google Analytics is not loaded on the registration, login, password and email verification pages, or in the application.
If you accepted and then create an account, we use that online identifier for at most 48 hours, so that we can report to Google Analytics that a registration took place and, if it happens within those 48 hours, that an access code was redeemed or a subscription was started, with the plan and billing period concerned. We do not tell Google who you are or which organisation you belong to. If you withdraw your consent while logged in, we delete the identifier straight away.
Providing your name, email address, password and the details of your organisation is necessary to create an account and perform the agreement; without this data we cannot provide the service. Without the data needed for payment and our administration we cannot start or invoice a subscription. Filling in the support form is voluntary; without your name and email address we cannot answer your message.
4. Why we process data
We do not sell personal data and do not use it for advertising.
| Purpose | Data | Legal basis |
|---|---|---|
| Providing the service: storing and analysing contracts and showing deadlines and renewals | Account, organisation, contract and document data | Performance of the agreement (Art. 6(1)(b) GDPR); for personal data in contracts: on behalf of the customer |
| AI analysis of contracts (data extraction, and on request summaries and analyses of clauses and risks) | Page text and original file name of the contract | Performance of the agreement with the customer, on behalf of the customer |
| Account and security: logging in, sessions, preventing abuse, audit log | Account data, session and security data, audit log | Performance of the agreement; legitimate interest in a secure service (Art. 6(1)(f) GDPR) |
| Support: answering your questions | Support messages | Legitimate interest in helping whoever contacts us; for customers also performance of the agreement |
| Contractual and legal administration: being able to show which terms were accepted | Acceptance record | Legitimate interest in being able to show the agreements made |
| Free trial: providing it, applying the one-trial rule, the emails about the trial and the deletion afterwards | Organisation data, the trial record and the records of the trial emails | Performance of the agreement; legitimate interest in preventing abuse of the trial and in being able to show that we warned before deleting data (Art. 6(1)(f) GDPR) |
| Website statistics: understanding how visitors find and use our public pages and which campaigns work | Pages visited, referring website, campaign tags, time, country, general technical details and an online identifier | Your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time through Cookie settings |
We make no decisions with legal effect for you on the basis of this data. The AI only extracts information from contract text; see AI analysis of contracts.
5. Personal data in your contracts
You decide which contracts you upload. As a customer you are responsible for having an appropriate legal basis and the authority to have the personal data in those contracts processed, and for informing the individuals concerned where necessary.
Do not upload documents with more personal data than necessary, and preferably no special categories of personal data.
If we receive a request from someone whose data is in a customer's contract, we put that request to that customer or handle it according to that customer's instructions.
6. AI analysis of contracts
To find the important data in a contract, we send the text of each page and the original file name to the Anthropic API. We also do this when you (depending on your subscription) have a summary or an analysis of clauses and risks made for a contract: we then send the page text and file name of that contract to Anthropic again. Summaries and analyses are only made if you ask for them; we store the result with the contract and it is deleted with the contract. The following applies:
- The original PDF file is not sent to Anthropic.
- Your name, email address and account data are not sent along. The contract text itself may contain personal data.
- When looking for contract data, the AI only extracts factual data from the text, each time with the page number and the verbatim passage. We check that the passage really appears on that page; data that cannot be checked in this way is marked for your review. The points in a summary or analysis are also only shown if their verbatim passage appears on the page mentioned; the wording and the attention level are the AI's.
- Cancellation deadlines and renewal dates are not determined by the AI, but by fixed calculation rules in our own software, based on the data found and confirmed or corrected by you.
- Scanned PDFs without a text layer are not analysed and not sent to Anthropic.
The result of the AI analysis, a summary or a risk analysis may be incomplete or incorrect and is not legally binding or authoritative and is not legal advice. An analysis only points out clauses that are in the contract; that something is not mentioned does not mean it is missing. Always check important data in the original contract. AI analysis is decision support. We make no decisions based solely on automated processing that have legal effects for you or similarly significantly affect you; you decide what to do with a contract.
7. Third parties
We use the following service providers:
| Party | What they do for us | Which data |
|---|---|---|
| Anthropic | AI analysis of contract text via the Anthropic API | Page text and original file name of the contract |
| Resend | Sending email: forwarding support messages to our support mailbox, verification and password reset emails and contract reminders | For the support form: name, email address, subject and message. For emails to you: your name and email address and a link. For reminders also the name and supplier of the contract concerned and the relevant dates, no contract text or document |
| Stripe | Processing payments for subscriptions | Your payment details and the details that you enter at checkout; we receive a customer and subscription number and the status of the subscription |
| TransIP | Our domain name, DNS and mailbox (support@guardmycontract.com) | Support messages that arrive in our mailbox and our replies |
| Hosting provider (TransIP) | Hosting of the application, the database and the files on a server in a Dutch data centre | All data of the service, as described in this policy |
| OVHcloud | Storage of encrypted backups of the service, in a data centre in Paris (France) | All data of the service, in encrypted form only. We encrypt the backups before they leave the server; OVHcloud does not have the key and cannot read the content |
| Website statistics through Google Analytics, on our public marketing pages, only if you accept analytics cookies | The data described under Website statistics. Advertising features, Google signals and data sharing with Google are switched off |
In addition we may disclose data if the law requires us to.
8. Transfers outside the European Union
According to our hosting provider, the application, the database and the uploaded files are on a server in a Dutch data centre. However, not all data stays within the European Union. Below is what the terms of our service providers state; we have not independently verified their data processing agreements, locations and safeguards and give no guarantees about their compliance:
- According to the terms of Anthropic, data is stored in the United States. According to Anthropic, traffic may be processed in selected countries in the United States, Europe, Asia and Australia, and for internal processes such as safety review, support or incident handling also in other countries where Anthropic operates. According to Anthropic's terms, the Standard Contractual Clauses of the European Commission apply to this, as part of Anthropic's commercial terms.
- According to the terms of Resend, data is stored in the United States, including the content of messages and sending logs. According to its processing terms, the Standard Contractual Clauses of the European Commission apply to this.
- Stripe may also process payment data outside the European Union, including in the United States. According to its processing terms, the Standard Contractual Clauses of the European Commission apply to this.
- According to TransIP, email is kept in data centres in the Netherlands.
- We keep the encrypted backups at OVHcloud in the Paris region (France), which we chose ourselves.
- Google may process website statistics outside the European Union, including in the United States. According to Google, data from devices in the European Union is first received on servers in the European Union. Google Analytics falls under Google's data processing terms. For those terms, Google states that it relies on the EU-U.S. Data Privacy Framework to transfer personal data from the European Economic Area to the United States, and that it may rely on the Standard Contractual Clauses of the European Commission for certain transfers where it does not use such a framework. We have not independently verified this. This only applies if you accept analytics cookies.
9. Security
These measures are built into the service today:
- Each uploaded PDF file is encrypted with its own key (AES-256-GCM) before it is stored. A copy moved to another organisation cannot be decrypted.
- The data of each organisation is separated from the others in the database, enforced by the database itself. Membership is checked again with every request.
- Roles determine what someone may do: readers can only view, uploading and editing requires at least the editor role, and only owners and admins can delete contracts.
- Passwords are only stored as a strong hash (scrypt).
- Sessions are kept on the server and end after 12 hours of inactivity or after 7 days at most. After a password change you are logged out on your other devices.
- All 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 add.
- A strict Content Security Policy and other security headers: no third-party scripts in the application or on the registration, login, password and email verification pages, and pages cannot be embedded in other websites. Google Analytics is only loaded on our public marketing pages, and only after you accept it.
What you should also know:
- The page text extracted from your PDFs, the quoted passages and the contract data found are stored in the database without this extra encryption by the application.
- Two-step verification is not yet available.
No system is completely secure. This description is not a certification or guarantee.
10. Retention periods
We do not keep personal data longer than necessary. These are our periods. If a statutory retention obligation prescribes a different period, or if data is needed for ongoing legal proceedings, that takes precedence.
| Data | Retention period |
|---|---|
| Account data (name, email address, password hash) | Until the account is deleted; then they are deleted. |
| Organisation and membership data | Memberships are deleted with the account. Organisation data: kept for 30 calendar days after the organisation is terminated, so that you can ask for it to be returned, then deleted (see below and the terms and conditions). We record the actual end of your access separately. |
| Contracts and document data: PDF file, page text, AI analysis data, contract data and related document data | As long as the organisation exists. An owner or admin can delete a contract earlier; it is then permanently deleted immediately. If your access ends, a period of 30 calendar days begins, once we have established this, in which you can ask for the data to be returned; after that we delete the contract data and the associated data of the organisation. We aim to complete this within 48 hours after that period ends; that is an aim and not a guarantee. We send no automatic warning for this. We handle a request to delete your account manually. |
| Invoice and subscription data | The Stripe customer and subscription number, the subscription and the status remain after the organisation is deleted, without contract data, and invoices and administration according to statutory retention obligations. |
| Record of the accepted terms and conditions | 2 years after the account is deleted. |
| Audit log | 2 years. |
| IP addresses (in audit log, support messages and acceptance record) | 90 days; then deleted or anonymised. |
| Expired sessions | Deleted 30 days after the session expired. |
| One-time links (email verification and password reset) | 30 days after the code has expired, been used or been revoked; then deleted. |
| Support messages | We have no fixed period and do not delete support messages automatically. We keep them as long as necessary to handle your question and to be able to find the conversation again, in the database and in our mailbox. At your request we delete your message, unless we still need it for an ongoing matter. We delete the IP address after 90 days. |
| Counts for rate limiting | A count applies for at most 1 hour; the clean-up runs every hour, so in practice up to about 2 hours, and longer if the clean-up is temporarily not running (hashed, in the database). |
| Website statistics in Google Analytics (only with your consent) | Event data: 2 months. Google Analytics cookies: 6 months. Google may keep aggregated reports for longer; those do not identify you. |
| Online identifier after registration (only with your consent) | It cannot be used after 48 hours; the system then refuses it. It is normally deleted from our database at the next hourly clean-up. If the clean-up is not running, the expired identifier stays in the database, unused, until the clean-up runs again. It is deleted from the database straight away if you withdraw your consent while logged in. A copy can remain in encrypted backups, as described under Backups. |
| Your cookie choice | 6 months, in a cookie in your own browser. |
| Contracts, documents and contract details of an organisation whose only access was a free trial | Kept for 30 days (30 × 24 hours) after the trial ends, then deleted automatically; never earlier, possibly later while a payment is being processed, an export is running or our last reminder could not be sent. Deleted 24 hours after a request by the owner if asked earlier. Copies may remain in encrypted backups for a limited time (see Backups below). |
| Record of a free trial (organisation, the user account that started it, start and end) | Kept with the subscription and access data of the organisation, to apply the rule of one trial per organisation and per user account (see Invoice and subscription data). |
| Records of the trial emails (which email, when it was sent, number of recipients, internal account numbers of the owners and the message number of the email provider; no content) | Normally deleted 2 years after the email was sent, also after the data of the organisation has been deleted, as evidence that we warned before deleting. Records of an email that was not sent (skipped or failed) are normally deleted 2 years after they were last processed. The record of our last reminder before deletion may be kept longer, for as long as the deletion it announced can still take place, and is deleted once that no longer applies. Deletion is done by our regular cleanup, which runs every hour. |
| Backups | 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 our storage provider once it is 30 days old. The provider carries out that deletion with some delay; we check that no backup is kept for longer than 35 days. Data that has been deleted may therefore remain in encrypted backups for up to about 35 days. We use backups only to restore the service. If we have to restore a backup, we keep the service unavailable until we have deleted again the data whose deletion we can establish: deletions that follow from our retention periods are repeated automatically. Deletions made after the backup, whether you asked us for them or carried them out yourself in the service (for example a contract you deleted), are repeated as far as our 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 you may then have to carry it out or request it again. |
| Data received by Anthropic | Anthropic keeps API input and output under its own terms. We have no control over this and cannot guarantee Anthropic's deletion period. |
| Data received by Resend | Resend keeps email and log data under its own terms. We cannot guarantee Resend's retention period. |
11. Your rights
Under the General Data Protection Regulation (GDPR) you have the right to:
- access your personal data (access);
- have incorrect data corrected (rectification);
- have your data deleted;
- have the processing restricted;
- receive data that you have given us and that we process for the agreement in a commonly used format (portability);
- object to processing based on our legitimate interest.
- withdraw your consent for website statistics at any time, through Cookie settings. This does not affect the processing that took place before.
You can change your name and password yourself in Settings. For all other requests, such as changing your email address, receiving a copy of your data or deleting your account, email support@guardmycontract.com. For the time being we handle these requests manually.
We respond without undue delay and at the latest within one month. For complex requests that period can be extended by two months; we will then tell you within the first month. A request is free of charge. We may ask you to confirm your identity, for example by sending the request from the email address of your account.
If your request concerns personal data in a contract uploaded by an organisation, we put it to that organisation or handle it according to its instructions.
You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
13. Changes
We may change this privacy policy if the service or the law changes. Each version has a version number and an effective date, at the top of this page. We announce important changes in advance in the service.
Language. These documents are available in English and Dutch. The English version is authoritative. If the language versions differ, the English version prevails.
See also our terms and conditions.