Data processing agreement
The article 28 processor agreement for the personal data inside the websites you connect, with a changes clause and version history.
Published 2.0 · 2026-10-18
Effective date: 18 October 2026 · Replaces: version 1.0 of 18 September 2026 (archived copy) · Changes: see Annex E
*In short: when WebCrew handles personal data inside the websites you connect, we act only on your instructions, keep it secure, tell you about a breach within 48 hours, use only the subprocessors on our public list, and delete the data when you leave. This summary and the other In short lines help you read the agreement; they are not part of it.*
1. Parties and how this agreement applies
1.1 This Data Processing Agreement ("DPA") is between the customer named in the WebCrew account ("Customer") and JKC Software B.V., High Tech Campus 32, 5656 AE Eindhoven, the Netherlands, Chamber of Commerce number 42082783 ("WebCrew").
1.2 This DPA forms part of the Terms of Service ("Terms"). It is concluded when the Customer accepts the Terms or signs an order form that refers to them, and applies automatically whenever WebCrew processes personal data on the Customer's behalf.
1.3 The version of this DPA in force is the one published at webcrew.ai/legal/dpa. Each version keeps its own permanent address (for example webcrew.ai/legal/dpa/v2.0) and is never changed after its effective date.
2. Definitions
2.1 Terms such as personal data, processing, controller, processor, data subject, personal data breach and supervisory authority have the meaning given in the GDPR (Regulation (EU) 2016/679).
2.2 In this DPA:
- Customer Personal Data means personal data in Connected Sites and in the Customer's Account that WebCrew processes on the Customer's behalf while providing the Services, including personal data of a kind that Annex A does not list.
- Account, Connected Site, Connection, Connector, SSH Connection, Command Log, End Client, Policy and Approval have the meaning given in the Terms.
- Services means the WebCrew services under the Terms.
- Subprocessor means a third party that WebCrew engages to process Customer Personal Data.
- Subprocessor List means the list at webcrew.ai/legal/subprocessors, which has its own version number and date.
- Business Day means a weekday that is not a public holiday in the Netherlands.
3. Roles
In short: usually you are the controller and we are your processor. If you manage websites for your own clients, we are their subprocessor through you. For our own account and billing data we are the controller.
3.1 Where the Customer determines the purposes and means of the processing, the Customer is the controller and WebCrew is the processor.
3.2 Where the Customer processes the personal data on behalf of an End Client (for example an agency that manages a client's website), the Customer is the processor, the End Client is the controller, and WebCrew is a subprocessor of the Customer. In that case:
- the Customer confirms that the End Client has authorised it to use WebCrew under the terms of this DPA, including the Subprocessor List;
- the Customer passes on instructions from the End Client and is WebCrew's only point of contact; WebCrew has no direct contractual relationship with the End Client;
- notices and assistance under this DPA go to the Customer, which informs the End Client within the time its own agreement requires.
3.3 WebCrew is the controller for the personal data it processes for its own purposes, such as user accounts, sign-in and security data, billing, support, marketing to business contacts and aggregated statistics about use of the Services. WebCrew is also the controller for the Command Log and the other security and accountability records of actions in the Services. If content of a Connected Site appears in those records, WebCrew processes that content as processor and keeps it out of the record where technically feasible. The WebCrew privacy notice covers WebCrew's processing as controller, not this DPA.
4. Instructions and purpose
4.1 WebCrew processes Customer Personal Data only on the Customer's documented instructions and only to provide the Services. The instructions are: the Terms, this DPA, the settings, Policies and Approvals the Customer's authorised users configure in the Services, and any further written instruction the Customer sends to privacy@webcrew.ai. An action by a visitor or user of a Connected Site is not an instruction.
4.2 WebCrew may process Customer Personal Data otherwise only where Union or Member State law requires it. WebCrew informs the Customer of that legal requirement beforehand, unless the law prohibits this.
4.3 WebCrew informs the Customer without delay if, in its opinion, an instruction infringes the GDPR or other data protection law. WebCrew may suspend that instruction until the Customer confirms or changes it.
4.4 An instruction that goes beyond the Services as described may be refused, or carried out at WebCrew's reasonable charges agreed in advance.
4.5 Actions that WebCrew performs automatically within the Policies and Approvals configured by the Customer's authorised users are performed on the Customer's instructions.
4.6 WebCrew does not sell Customer Personal Data, does not use it for its own purposes and does not use it to train AI models. WebCrew uses AI model providers only under terms that exclude training on Customer Personal Data.
5. Customer responsibilities
5.1 The Customer is responsible for having a lawful basis for each processing, for informing data subjects, and for the lawfulness of the personal data held by its Connected Sites. This includes the privacy notice and cookie consent on its own websites.
5.2 The Customer does not use the Services to process special categories of personal data or criminal-offence data, except to the extent such data is incidentally contained in a Connected Site. WebCrew then applies the measures of Annex B to that data without distinction.
5.3 The Customer carries out a data protection impact assessment where the law requires one.
5.4 The Customer indemnifies WebCrew against claims of data subjects and supervisory authorities, including fines, to the extent they result from the Customer's own breach of the GDPR or of this DPA. Where this clause and the indemnity in the Terms both apply, WebCrew may recover under either, but only once for the same loss.
6. Confidentiality and security
6.1 WebCrew grants access to Customer Personal Data only to persons who need it for the Services and who are bound by a written or statutory duty of confidentiality, which continues after their involvement ends.
6.2 WebCrew implements the technical and organisational measures in Annex B, taking into account the state of the art, the costs, and the nature, scope, context, purposes and risks of the processing, as required by article 32 GDPR.
6.3 WebCrew reviews these measures at least once a year and after a material change to the Services. It may change them, provided the overall level of protection does not decrease. Security of the Customer's own systems, hosting, accounts and Connected Sites remains the Customer's responsibility.
7. Subprocessors
In short: you approve the subprocessors on our public list. We tell you 30 days before we add or replace one. If you object and we cannot solve it, you may end the affected service without cost.
7.1 The Customer gives WebCrew general written authorisation to engage the Subprocessors on the Subprocessor List. The Subprocessor List states, for each Subprocessor, the processing, the location and the safeguard for any transfer outside the European Economic Area (EEA).
7.2 WebCrew notifies the Customer at least thirty (30) days before it adds or replaces a Subprocessor, to the administrative contact on the Customer's Account, through the product's notification channel and on the changes page at webcrew.ai/legal/changes. A change to the Subprocessor List is not a change to this DPA or the Terms.
7.3 Where a change is needed sooner to address an acute security or continuity risk, WebCrew may make it earlier and notifies the Customer as soon as possible with its reasons.
7.4 The Customer may object to a change on reasonable data protection grounds within the notice period, or within thirty (30) days of a notice under 7.3. The parties then look for a solution in good faith. If they find none within thirty (30) days, the Customer may terminate the affected Services without charge, with a refund of prepaid fees for the period not yet provided. This is the Customer's only remedy for the objection.
7.5 WebCrew imposes on each Subprocessor, by contract, data protection obligations that offer at least the protection required by article 28(4) GDPR. WebCrew remains liable to the Customer for its Subprocessors, within the limits of clause 13.
7.6 A third party that the Customer selects and contracts with itself, such as its hosting provider, a plugin vendor or a messaging service, is not a Subprocessor.
8. Transfers outside the EEA
8.1 WebCrew transfers Customer Personal Data outside the EEA only to recipients on the Subprocessor List and only with a safeguard under Chapter V GDPR, such as an adequacy decision (including the EU-US Data Privacy Framework for certified recipients) or the EU Standard Contractual Clauses ("SCCs", Commission Implementing Decision (EU) 2021/914), with supplementary measures where needed.
8.2 Where the Customer is established outside the EEA and its processing is not subject to the GDPR, Module Four of the SCCs (processor to controller) applies to the transfer of Customer Personal Data from WebCrew to the Customer. Annex A of this DPA is their Annex I, the competent supervisory authority is the Dutch Data Protection Authority (Autoriteit Persoonsgegevens), clause 7 of the SCCs does not apply, and clauses 17 and 18(b) designate Dutch law and the courts of the Netherlands. Transfers to a Customer in the United Kingdom rely on the adequacy decision for the United Kingdom for as long as it is in force.
8.3 If a safeguard ceases to apply, WebCrew suspends the transfer or moves the processing to the EEA and informs the Customer. If no lawful solution is available, either party may terminate the affected Services, with a refund of prepaid fees for the period not yet provided. A suspension or move under this clause is not a breach of the Terms.
8.4 The Customer chooses per Account whether website backups are stored in the European Union or in the United States. Choosing the United States is the Customer's documented instruction for that transfer, which relies on the safeguard stated in the Subprocessor List. The Customer confirms that this choice is lawful for the personal data in its Connected Sites.
9. Personal data breaches
In short: we tell you within 48 hours of learning about a breach and keep you updated. You decide whether to notify the authority or the people affected.
9.1 WebCrew notifies the Customer of a personal data breach affecting Customer Personal Data without undue delay and no later than forty-eight (48) hours after becoming aware of it. WebCrew becomes aware when it has a reasonable degree of certainty that a security incident has led to Customer Personal Data being compromised.
9.2 The notification contains, as far as known: 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. WebCrew supplements the notification as more becomes known.
9.3 The Customer decides whether to notify the supervisory authority and data subjects. WebCrew does not do so on the Customer's behalf unless the Customer asks in writing, and does not make a public statement that identifies the Customer without its consent, unless the law requires it.
9.4 WebCrew documents each breach affecting Customer Personal Data, including the facts, the effects and the remedial action, and shares that record with the Customer on request.
9.5 Where the breach results from WebCrew's attributable failure, WebCrew bears its own costs of investigation and remediation and the Customer's reasonable and documented costs, within the limits of clause 13. In all other cases each party bears its own costs.
10. Assistance
10.1 If a data subject contacts WebCrew about Customer Personal Data, WebCrew does not answer the substance. It forwards the request to the Customer within five (5) Business Days and tells the data subject it has done so.
10.2 WebCrew assists the Customer with data subject requests through the functions of the Services and, where these are not sufficient, with reasonable additional help.
10.3 WebCrew gives the Customer the information it reasonably needs for its obligations under articles 32 to 36 GDPR, including a data protection impact assessment and prior consultation. Annex A, Annex B and the Subprocessor List are the standard form of that assistance.
10.4 Assistance that goes materially beyond the functions of the Services or beyond occasional help is charged at WebCrew's standard rates, notified in advance. Assistance needed because of WebCrew's own failure is free of charge.
11. Information and audits
11.1 WebCrew makes available the information needed to demonstrate compliance with this DPA, in the first place Annex B, summaries of its security policies and, when available, independent reports or certificates.
11.2 If that information does not answer a specific, reasoned concern, the Customer may have an audit carried out once per calendar year, and more often after a personal data breach or a request from a supervisory authority. The Customer gives at least thirty (30) days' written notice.
11.3 The audit is performed by the Customer or an independent auditor bound by confidentiality who does not work for a competitor of WebCrew, during Business Days, without disrupting the Services and without access to data of other customers. Where the Customer acts for its own client under clause 3.2, the client exercises audit rights through the Customer.
11.4 Each party bears its own costs. The Customer pays WebCrew's reasonable costs for time spent beyond one (1) Business Day, unless the audit shows a material breach of this DPA by WebCrew, in which case WebCrew remedies it at its own cost.
11.5 These limits do not restrict a supervisory authority exercising its statutory powers.
12. Return and deletion
12.1 Until the Services end, the Customer can export its Account data through the Services and restore the backups of its Connected Sites. At the Customer's choice, made in writing before the end of the deletion period in Annex D, WebCrew provides the latest backup of each Connected Site and returns other Customer Personal Data in a structured, commonly used, machine-readable format, or deletes it. Without a choice, WebCrew deletes it.
12.2 After the Services end, or when the Customer deletes its Account, WebCrew deletes Customer Personal Data in line with Annex D, unless Union or Member State law requires storage. WebCrew confirms deletion in writing on request.
13. Liability
13.1 The liability provisions of the Terms, including the limitation of liability, apply to all claims under or in connection with this DPA. A fine imposed on the Customer, or a claim of a data subject paid by the Customer, that results from WebCrew's attributable failure under this DPA counts as direct damage within that limitation. The limitation applies once, to all claims under the Terms and this DPA together.
13.2 This clause does not affect the liability of either party towards data subjects under article 82 GDPR. Recourse between the parties under article 82(5) GDPR is subject to clause 13.1.
14. Changes to this DPA
In short: we can update this DPA. Material changes come with 30 days' notice and you may leave before they apply. Changes never apply retroactively and never lower the protection of data we already hold.
14.1 WebCrew may change this DPA as follows:
| Type of change | Example | Notice | Customer's right |
|---|---|---|---|
| Subprocessor List | a new hosting or AI provider | clause 7 | clause 7.4 |
| Annex B (security measures) | a different backup technique | none; recorded in Annex E | only allowed if the level of protection does not decrease |
| Required by law, a court or a supervisory authority | new Standard Contractual Clauses | as soon as possible, with reasons | none additional |
| Other material change | a new processing activity or a longer retention period | at least thirty (30) days | terminate the affected Services before the change takes effect, with a refund of prepaid fees for the period not yet provided |
| Editorial change | correcting a typo or clarifying wording without changing its meaning | publication with an entry in Annex E | none |
14.2 WebCrew sends notices under this clause to the administrative contact on the Customer's Account and through the product's notification channel, and publishes them on webcrew.ai/legal/changes, stating the new version number, the effective date and a summary of the change.
14.3 A change never applies retroactively and never reduces the protection of Customer Personal Data processed before the change takes effect.
14.4 A change to this DPA is not a change to the Terms, and a change to the Terms does not change this DPA, unless the notice says so expressly.
14.5 A signed addendum or order form that deviates from this DPA continues to apply in its agreed form until it expires or the parties agree otherwise.
14.6 Version numbers follow the pattern major.minor. A major number marks a material change under 14.1; a minor number marks an editorial change or a change to Annex B. Every version stays available at its own address, and the Customer may request a copy of the version that applied to it at any time.
14.7 Continued use of the Services after the effective date of a change under clause 14.1 is acceptance of that change.
15. Term, precedence and governing law
15.1 This DPA applies until all Customer Personal Data, including copies in backups under Annex D, has been deleted or returned, and then ends automatically. Clauses 5.4, 13 and 15 continue to apply after that, and the duty of confidentiality in 6.1 continues without limit in time.
15.2 If this DPA conflicts with the Terms on the processing of personal data, this DPA prevails, except for liability, which is governed by clause 13 and the Terms. If the SCCs apply and conflict with this DPA, the SCCs prevail.
15.3 A data processing agreement proposed by the Customer applies only if WebCrew agrees to it in a written amendment signed by both parties. Matters it does not cover remain governed by this DPA, and liability remains governed by clause 13 unless the accepted agreement expressly provides otherwise.
15.4 This DPA replaces version 1.0 for all customers from its effective date.
15.5 This DPA is governed by Dutch law. Clause 14.1 of the Terms applies to disputes.
Annex A · Processing details
Nature and purpose. Operating, maintaining, protecting and reporting on the Customer's websites on its instructions, through the Connector and, where the Customer grants one, an SSH Connection: inventory and health monitoring, updates and rollbacks, backups and restores, audits, uptime and performance checks, commands that the Customer's Policies and Approvals permit, and the optional AI features. This involves collection, storage, retrieval, consultation, transmission, alteration, restriction and erasure.
Duration. For the duration of the Services, plus the deletion period and backup expiry in Annex D.
Frequency. Continuous, for as long as Connected Sites are linked to the Account.
| Activity | Data subjects | Personal data | Retention |
|---|---|---|---|
| Site inventory and health checks | Administrators of Connected Sites | Login name, display name, email address and registration date of up to 25 administrator accounts per website; technical error messages, which may contain personal data | While the website is connected; error records up to 90 days |
| Live views (users, comments, logs) | Users and commenters of Connected Sites | User list with login, email address and role; comments with author name, email address and text | Not stored; shown live and discarded |
| Website backups and restores | Everyone whose data is stored in a Connected Site, such as visitors, customers and account holders | All data in the website database and media files, including account and order data; stored in the region the Customer chooses (clause 8.4) | Rolling schedule: all backups for 24 hours, daily for 7 days, weekly for 28 days, monthly for about 92 days; the newest complete backup is kept while the website is connected |
| Uptime and performance monitoring | None directly | Website address, response status and timing | Per plan, up to 90 days |
| Commands on Connected Sites (Connector or SSH Connection) | Anyone whose data is stored in a Connected Site | Content of the Connected Site that a command reads or changes while it runs; file contents and database rows are not kept afterwards | Only for the duration of the command |
| Command Log and activity log (WebCrew's own record, see clause 3.3; listed here for site content that appears in it) | The Customer's users and administrators of Connected Sites | Command or call, target path or object, outcome, error output of failed commands, authorisation, user identifier, IP address, time; secrets are redacted | Per plan: 7, 30 or 90 days |
| End-client AI chat (optional, switched on per website) | Users of a Connected Site who use the chat | Questions, answers, chat history, language, and technical website information used to answer | Per website setting between 1 and 365 days, default 30 days |
| AI website audit (runs when the Customer starts an audit that includes the AI review) | People who appear in images or text on a Connected Site | Images and page text sent for review; WebCrew stores the conclusion and suggested alternative text, not the prompt | Results until the Connected Site is removed from the Account |
| Notifications and reports by email | The Customer's users and recipients the Customer chooses | Email address, name, message content | Until the Account is deleted |
Special categories. Not intended. Where a Connected Site contains them, they can be present in backups, in live views and in content sent to the optional AI features, and Annex B applies.
Annex B · Technical and organisational measures (article 32 GDPR)
These measures are in place on the effective date of this version. Planned measures are not listed here; they are added through a minor version when they are live.
Encryption and pseudonymisation
- All traffic to and from the Services and between the Services and Connected Sites is encrypted in transit (TLS), with HTTP Strict Transport Security and a restrictive content security policy on the application.
- Website database backups are encrypted (AES-256-GCM) with a separate key for each customer organisation, derived from a master key that is kept outside the stored backups.
- Passwords are stored only as Argon2id hashes; other secrets the Services hold are encrypted.
Confidentiality and integrity
- Every request between the Services and a Connected Site through the Connector is signed (HMAC-SHA256), time-limited and protected against replay. An SSH Connection uses a key that the Customer grants for a system user it chooses and can revoke at any time.
- Customer data is separated per organisation: every data query is bound to the organisation of the signed-in user.
- Access is role-based within each organisation. Two-factor authentication is available to every user and can be made mandatory by the organisation.
- Workers that call AI services are separated from workers that change websites.
- Actions and commands on Connected Sites are recorded in the Command Log with target, outcome and authorisation; secrets are redacted before an entry is written.
- Staff access to production systems is limited to named people who need it, with individual accounts.
Availability and resilience
- Website backups follow a rolling retention schedule and can be restored by the Customer from the Services.
- The platform database is hosted in the EEA, encrypted at rest and backed up daily by the database provider.
- The Services are monitored continuously, with central logging kept for 30 days.
Testing and organisation
- Changes go through code review and automated tests before release; dependencies are monitored for known vulnerabilities.
- A written incident response procedure covers detection, classification, the 48-hour notification under clause 9 and a review after each incident.
- Subprocessors are engaged only under written terms that meet article 28(4) GDPR.
- These measures are reviewed at least once a year.
Annex C · Subprocessors
The Subprocessor List at webcrew.ai/legal/subprocessors forms part of this DPA. It has its own version number and date; each version stays available at its own address. Changes follow clause 7.
Annex D · Deletion
- When the Customer deletes its Account, or no later than thirty (30) days after the Services end, the Account enters a 30-day deletion period. During that period the Customer can still export its data and restore the organisation.
- After the deletion period, WebCrew deletes Customer Personal Data from its active systems, including all website backups. Activity log entries expire at the end of their retention period of at most 90 days.
- Copies in backups of the platform database expire through rotation within the retention period of those backups, which does not exceed ninety (90) days ("backup expiry"). Until then they are not used for any purpose other than disaster recovery and remain subject to this DPA.
- Records WebCrew must keep by law, such as invoices, are kept for the statutory period only and are not covered by this DPA.
Annex E · Version history
| Version | Effective date | Change |
|---|---|---|
| 2.0 | 18 October 2026 | Full revision: definitions; roles when the Customer acts for End Clients; processing details per activity, including the SSH Connection and the Command Log; choice of backup region; security measures; changes clause and versioning; transfer clause with Module Four; deletion schedule. |
| 1.0 | 18 September 2026 | First version (archived copy). |