This Data Processing Agreement (“DPA”) forms part of the Terms of Service between Wipkin and the organization that uses Wipkin Cloud (“Customer”). It applies when Wipkin processes Customer Personal Data on Customer’s behalf and that processing is subject to Data Protection Laws.
The DPA applies automatically when Customer accepts the Terms of Service. No signature is needed. If Customer would like a countersigned copy, email contact@wipkin.com.
01 · Definitions
Terms not defined here have the meanings given in the Terms of Service or in Data Protection Laws.
- “Customer Personal Data” means personal data in the content Customer and its Authorized Users add to Customer’s organization in Wipkin Cloud, together with the membership, invitation, role, project-access and audit records of that organization, that Wipkin processes on Customer’s behalf.
- “Authorized Users” means the people Customer allows to access its organization.
- “Data Protection Laws” means all laws on data protection and privacy that apply to the processing of Customer Personal Data under this DPA, including, where applicable, the EU General Data Protection Regulation 2016/679 (“EU GDPR”), the EU GDPR as it forms part of UK law and the UK Data Protection Act 2018 (“UK GDPR”), the Swiss Federal Act on Data Protection (“FADP”), India’s Digital Personal Data Protection Act 2023 and US state privacy laws.
- “Security Incident” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
- “Sub-processor” means another processor Wipkin engages to process Customer Personal Data.
- “Standard Contractual Clauses” or “SCCs” means the standard contractual clauses approved by the European Commission in Implementing Decision (EU) 2021/914.
- “UK Addendum” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, issued by the UK Information Commissioner under section 119A(1) of the Data Protection Act 2018.
02 · Roles and scope
2.1 Customer is the controller (or, where it acts for another controller, a processor) of Customer Personal Data. Wipkin is Customer’s processor (or sub-processor).
2.2 Wipkin’s own data. Wipkin is an independent controller of the personal data it uses to run accounts, sign people in, send service messages, secure the Service, respond to enquiries and meet legal obligations, as described in the Privacy Policy. This DPA does not apply to that data.
2.3 Details of processing. The subject matter, nature, purpose and duration of the processing, and the types of personal data and data subjects, are described in Annex I.
03 · Customer’s responsibilities
Customer is responsible for:
- the lawfulness of its instructions and of adding Customer Personal Data to Wipkin, including having a legal basis and giving any required notices to data subjects;
- deciding what Customer Personal Data is added and who can access it, using the organization and project permissions in the Service; and
- not adding special categories of personal data, criminal-offence data, government identification numbers, payment card data or other highly sensitive data, which the Service is not designed to protect.
04 · Wipkin’s obligations
4.1 Instructions. Wipkin will process Customer Personal Data only on Customer’s documented instructions, unless the law requires otherwise. In that case, Wipkin will tell Customer before processing unless the law prohibits it. Customer’s instructions are:
- to provide the Service in line with the Terms of Service, the Beta Terms while the Service is in beta, and this DPA;
- as initiated by Customer and its Authorized Users through the Service; and
- any other reasonable written instructions Customer gives that are consistent with the Terms of Service.
Wipkin will tell Customer if it believes an instruction breaks Data Protection Laws.
4.2 Beta deletion is an instruction. While Wipkin Cloud is in beta, Customer instructs Wipkin that Customer Personal Data may be deleted as described in the Beta Terms, for example when the beta environment is reset. When the beta ends, Customer instructs Wipkin to delete the entire beta environment, including all Customer Personal Data in it, and not to transfer it to the generally available service at app.wipkin.com.
4.3 Confidentiality. Wipkin will ensure that anyone it authorizes to process Customer Personal Data is bound by a duty of confidentiality.
4.4 No other use. Wipkin will not sell Customer Personal Data, share it for cross-context behavioural advertising, or use it for any purpose other than providing the Service. Wipkin will not combine it with personal data from other sources except as needed to provide the Service. Wipkin understands and will comply with these restrictions as a “service provider” or “processor” under US state privacy laws.
05 · Security
5.1 Wipkin will implement and maintain appropriate technical and organizational measures to protect Customer Personal Data, taking into account the state of the art, costs, and the nature, scope, context and purposes of the processing and the risks to individuals. The current measures are described in Annex II.
5.2 Wipkin may update these measures as long as the overall level of protection is not reduced.
06 · Sub-processors
6.1 General authorization. Customer gives Wipkin general authorization to engage Sub-processors. The current Sub-processors are listed at /subprocessors, which forms Annex III.
6.2 Sub-processor terms. Wipkin will engage each Sub-processor under a written contract that imposes data-protection obligations providing at least the same level of protection as this DPA. Wipkin remains responsible to Customer for its Sub-processors’ performance of those obligations.
6.3 Changes. Wipkin will tell Customer of any intended addition or replacement of a Sub-processor in advance by updating the list and emailing organization owners: at least 7 days in advance while Wipkin Cloud is in beta, and at least 30 days in advance after the beta.
6.4 Objection. Customer may object on reasonable data-protection grounds by emailing contact@wipkin.com within that notice period. The parties will discuss the concern in good faith. If it cannot be resolved, Customer may stop using the Service and ask Wipkin to delete its organization. Because the Service is free during beta, no fees are due or refundable.
6.5 Emergency replacement. If Wipkin must replace a Sub-processor urgently for security or continuity reasons, it will notify Customer as soon as practicable afterwards and Customer’s objection right will apply from that notice.
07 · Helping Customer
7.1 Data subject requests. Wipkin will tell Customer without undue delay if it receives a request from a data subject about Customer Personal Data, and will not respond to the request itself except to direct the person to Customer, unless Customer authorizes it. Taking into account the nature of the processing, Wipkin will help Customer respond to such requests, mainly through features of the Service that let Customer view, correct, export where available, and delete Customer Personal Data.
7.2 Assessments and consultations. Wipkin will give Customer reasonable information and help, taking into account the information available to Wipkin, so that Customer can carry out data-protection impact assessments and consult supervisory authorities where Data Protection Laws require it.
08 · Security Incidents
8.1 Wipkin will notify Customer without undue delay after becoming aware of a Security Incident affecting Customer Personal Data, and will aim to do so within 72 hours.
8.2 The notice will be sent to the organization owners’ email addresses and will describe, as far as then known, the nature of the incident, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Wipkin may provide information in stages as it becomes available.
8.3 Wipkin will take reasonable steps to contain, investigate and reduce the effects of the incident. Notifying Customer is not an admission of fault or liability.
09 · Deletion and return
9.1 When Customer’s use of the Service ends, or when an organization owner asks Wipkin to delete the organization, Wipkin will delete Customer Personal Data within 30 days, unless the law requires Wipkin to keep it. When the beta ends, Wipkin will delete all Customer Personal Data in the beta environment on the end date, which Wipkin will announce to organization owners at least 14 days in advance, except in an emergency as described in the Beta Terms.
9.2 Before deletion, Customer may copy its data through the features available in the Service. During beta, the Service may not offer a complete export.
9.3 Customer Personal Data in backups will be overwritten in the normal backup cycle, within 7 days, and until then will remain protected under this DPA and will not be actively processed.
10 · Audits
10.1 Wipkin will make available to Customer the information reasonably needed to demonstrate compliance with this DPA and Article 28 of the EU and UK GDPR.
10.2 Customer agrees to exercise its audit rights first by reviewing this DPA, Annex II and Wipkin’s written answers to a reasonable security questionnaire, not more than once a year.
10.3 If that information is not enough to demonstrate compliance, or a supervisory authority requires it, or after a Security Incident, Customer may conduct an audit, or have an independent auditor bound by confidentiality conduct one, on at least 30 days’ notice, during business hours, at Customer’s cost, and in a way that does not disrupt the Service or expose other customers’ data. Audits of a Sub-processor’s facilities will be satisfied by the Sub-processor’s own audit reports and certifications.
11 · International transfers
11.1 Location. Wipkin is based in India and stores Customer Personal Data in Microsoft Azure’s Central India region. Sub-processors may process data in the locations listed at /subprocessors.
11.2 EU transfers. To the extent Wipkin’s processing involves a transfer of Customer Personal Data subject to the EU GDPR to a country without an adequacy decision, the SCCs are incorporated into this DPA as follows:
- Module Two (controller to processor) applies where Customer is a controller, and Module Three (processor to processor) applies where Customer is a processor;
- Customer is the “data exporter” and Wipkin is the “data importer”;
- Clause 7 (docking clause) applies;
- in Clause 9(a), Option 2 (general written authorization) applies, with the notice period in section 6.3 of this DPA;
- in Clause 11(a), the optional language does not apply;
- in Clause 13(a), the competent supervisory authority is determined by the data exporter’s establishment or, if it has none in the EU, by the location of its EU representative or the data subjects concerned, as the clause provides;
- in Clause 17, the SCCs are governed by the law of Ireland;
- in Clause 18(b), disputes will be resolved by the courts of Ireland; and
- Annexes I, II and III of the SCCs are completed by Annexes I, II and III of this DPA.
11.3 UK transfers. For transfers subject to the UK GDPR, the SCCs apply as amended by the UK Addendum. Table 1 is completed with the parties’ details in Annex I; Table 2 refers to the SCC modules and options selected in section 11.2; Table 3 is completed by Annexes I to III; and for Table 4, either party may end the UK Addendum as set out in its Section 19.
11.4 Swiss transfers. For transfers subject to the FADP, the SCCs apply with these changes: references to the EU GDPR are read as references to the FADP; the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner; references to “Member State” do not prevent data subjects in Switzerland from bringing claims in their place of habitual residence; and the SCCs are governed by Swiss law where the FADP requires it.
11.5 Precedence. If the SCCs, as applied above, conflict with this DPA or the Terms of Service, the SCCs prevail.
11.6 Government access. If Wipkin receives a legally binding request from a public authority for access to Customer Personal Data, it will, unless legally prohibited, promptly notify Customer, challenge the request where there are reasonable grounds to consider it unlawful, and disclose only the minimum data required.
12 · Liability
Each party’s liability under this DPA is subject to the limitations in the Terms of Service, and the DPA and the Terms of Service share a single liability cap rather than each having its own. Customer is responsible for claims, fines and losses arising from its unlawful instructions or from personal data it adds in breach of section 3. Those limitations do not limit any party’s liability to data subjects under the SCCs or Data Protection Laws where the law does not permit it.
13 · Term, changes and precedence
13.1 This DPA lasts as long as Wipkin processes Customer Personal Data on Customer’s behalf.
13.2 Wipkin may update this DPA to reflect changes in Data Protection Laws, the Service or its Sub-processors, provided the update does not materially reduce the protection given to Customer Personal Data or change the SCCs. While Wipkin Cloud is in beta, updates take effect when posted, as described in section 11 of the Beta Terms; Wipkin will try to notify organization owners of significant changes. After the beta, Wipkin will notify organization owners of material changes in advance. Sub-processor changes always follow section 6.3.
13.3 If this DPA conflicts with the Terms of Service or Beta Terms about the processing of Customer Personal Data, this DPA prevails, subject to section 11.5.
14 · Contact
Data-protection questions and notices: contact@wipkin.com
Annex I · Description of processing
A. Parties
Data exporter
- Name and address: the Customer organization, as identified in its Wipkin organization settings and by the owner who accepted the Terms of Service
- Contact: the organization owners’ email addresses
- Activities: using Wipkin Cloud to manage work with Scrum or Kanban
- Role: controller (Module Two) or processor (Module Three)
- Signature and date: accepted electronically when the Terms of Service were accepted
Data importer
- Name: Arpitkumar Chaudhari, operating Wipkin
- Address: D-35, Tulsi Park, Vyara, Tapi District, Gujarat 394650, India
- Contact: contact@wipkin.com
- Activities: providing the Wipkin Cloud work-management service
- Role: processor
- Signature and date: accepted electronically by publishing and agreeing to these terms
B. Description of transfer
| Item | Description |
|---|---|
| Categories of data subjects | Customer’s Authorized Users, such as employees and contractors; people invited to Customer’s organization; and people mentioned in Customer’s workspace content |
| Categories of personal data | Names and email addresses; organization roles, project roles and access; invitation records; work-item, goal, policy, comment, feedback and other workspace content; names of people assigned to or mentioned in work; audit records of membership, role and access changes, including who made them and when |
| Sensitive data | None intended. Customer must not add special categories of data or other highly sensitive data (section 3) |
| Frequency | Continuous, for as long as Customer uses the Service |
| Nature of processing | Hosting, storage, retrieval, display, transmission to Authorized Users, sending service emails such as invitations, backup, deletion and support |
| Purpose | To provide, secure and support Wipkin Cloud for Customer |
| Retention | For the duration of the Service, then deleted under section 9; backups overwritten within 7 days; beta data may be deleted earlier under the Beta Terms and is all deleted when the beta ends |
| Transfers to Sub-processors | As listed at /subprocessors, for the purposes and duration stated there |
C. Competent supervisory authority
As determined under Clause 13 of the SCCs (see section 11.2).
Annex II · Technical and organizational measures
These measures describe Wipkin Cloud as configured on 19 November 2026.
| Area | Measures |
|---|---|
| Encryption in transit | HTTPS only, with TLS 1.2 or higher between browsers and the Service and between the application and its database |
| Encryption at rest | Database and storage encrypted at rest by Microsoft Azure with service-managed keys |
| Network isolation | The database accepts connections only through a private network endpoint; public network access is disabled. The key vault accepts access only from Wipkin’s private network |
| Secrets management | Application secrets kept in Azure Key Vault and read by the application’s managed identity; no stored deployment passwords (deployments use short-lived federated identities) |
| Least privilege | The application’s database identity can read and write data only; administrative database access uses Microsoft Entra authentication |
| Authentication | Passwords of 15–128 characters with common passwords rejected; stored only as salted hashes; account lockout after 5 failed attempts; six-digit verification codes valid for 10 minutes with limited attempts; email and IP-based rate limits |
| Session security | Secure, HttpOnly session cookies limited to 8 hours; CSRF protection on state-changing requests; immediate session invalidation after credential changes |
| Access control | Organization and project permissions enforced by the server on every request; private projects visible only to their members; owners and administrators manage access without automatically reading private project work |
| Application security | Content Security Policy, framing protection and other browser security headers; validation of user input and saved links; optimistic version checks against conflicting changes |
| Audit and monitoring | Audit records of membership, role and access changes; server and security logs kept for up to 90 days |
| Availability and backup | Automated database backups with point-in-time restore, kept for 7 days, in the same region |
| Personnel | Access to production systems limited to the operator; confidentiality obligations for anyone given access in future |
| Development | Changes tested with automated backend, frontend and browser tests and security reviews before deployment |
| Incident response | Incidents investigated and notified under section 8 |
| Data minimization | Only data needed for the Service is collected; no advertising or analytics tracking in Wipkin Cloud. The cookieless visit statistics on wipkin.com do not include Customer Personal Data |
Annex III · Sub-processors
The current list of Sub-processors, with their purposes and locations, is published at /subprocessors.