OneTaskList logoOneTaskList

Legal

Data Processing Agreement

How OneTaskList processes personal data on behalf of organisations that use it.

Last updated: 22 October 2026

Overview

This Data Processing Agreement (“DPA”) forms part of the agreement between the customer named below (“Customer”) and OneTaskList Pty Ltd (ACN 698 036 798), Level 15, 461 Bourke Street, Melbourne VIC 3000, Australia (“OneTaskList”) for the OneTaskList service (the “Agreement”). It applies when OneTaskList processes personal data on the Customer’s behalf.

In short: the Customer decides how its people’s data is used; OneTaskList processes it only to provide the service, keeps it secure, uses only the sub-processors listed in Annex III, tells the Customer about a breach within 48 hours, helps with requests from individuals, and deletes the data when the Agreement ends. Transfers out of the EU, UK and Switzerland are covered by the Standard Contractual Clauses.

1. Definitions

Terms used in data protection law, such as “controller”, “processor”, “personal data”, “processing”, “data subject”, “personal data breach” and “supervisory authority”, have the meaning given in the GDPR. In addition:

  • Data Protection Law: the GDPR (Regulation (EU) 2016/679), the UK GDPR and the Data Protection Act 2018, the Swiss Federal Act on Data Protection, the Australian Privacy Act 1988, and any other data protection law that applies to the processing.
  • Customer Personal Data: personal data that OneTaskList processes on the Customer’s behalf in providing the service, as described in Annex I.
  • Sub-processor: another processor that OneTaskList engages to process Customer Personal Data.
  • SCCs: the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914.
  • UK Addendum: the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner (version B1.0).

2. Roles and scope

  • The Customer is the controller of Customer Personal Data, and OneTaskList is its processor.
  • OneTaskList is a controller, not a processor, for the personal data it needs to run its own business: billing and account administration with the Customer, and keeping the service secure. Its privacy policy covers that data.
  • Connected tools (for example Jira or Microsoft 365) and AI providers that the Customer’s users choose are not OneTaskList’s sub-processors. They act under the Customer’s or the user’s own agreements with them.

3. Instructions

  • OneTaskList processes Customer Personal Data only on the Customer’s documented instructions. The Agreement, this DPA, the Customer’s configuration of the service, and its users’ actions in the service are those instructions.
  • OneTaskList processes Customer Personal Data otherwise only where the law requires it, and tells the Customer first unless that law forbids it.
  • OneTaskList tells the Customer straight away if it believes an instruction breaks Data Protection Law.
  • OneTaskList never sells Customer Personal Data, never uses it for advertising, and never uses it to train AI models.

4. Confidentiality

OneTaskList ensures that everyone it authorises to process Customer Personal Data is bound by confidentiality, and has access only as far as their work requires.

5. Security

OneTaskList implements the technical and organisational measures in Annex II, taking into account the state of the art, the cost, and the nature, scope, context and purposes of the processing, as well as the risk to people (Art. 32 GDPR). OneTaskList may change those measures as long as the overall level of protection doesn’t go down.

6. Sub-processors

  • The Customer authorises OneTaskList to engage the sub-processors in Annex III.
  • OneTaskList gives the Customer at least 30 days’ notice before adding or replacing a sub-processor, by [email to the Customer’s contact and an update to onetasklist.com/subprocessors].
  • The Customer may object on reasonable data protection grounds within that 30 days. If the parties can’t resolve the objection, the Customer may end the affected part of the service, and OneTaskList refunds any prepaid fees for the unused period.
  • OneTaskList puts data protection obligations on each sub-processor that are no less protective than this DPA, and stays responsible to the Customer for its sub-processors’ performance.

7. Requests from individuals

  • The service lets the Customer’s users download their data (Account settings › Download My Data) and delete their accounts (Delete My Account). Disconnecting a tool deletes the tasks copied from it.
  • If OneTaskList receives a request from one of the Customer’s users about Customer Personal Data, it passes the request to the Customer without undue delay and doesn’t answer it unless the Customer asks.
  • OneTaskList otherwise helps the Customer, by appropriate technical and organisational measures, to respond to requests from individuals exercising their rights (GDPR Chapter III).

8. Other assistance

Taking into account the nature of the processing and the information available to it, OneTaskList helps the Customer meet its obligations on security (Art. 32), breach notification (Art. 33–34), data protection impact assessments and prior consultation (Art. 35–36). OneTaskList may charge reasonable costs for help beyond what the service and this DPA provide, if it says so in advance.

9. Personal data breaches

  • OneTaskList tells the Customer about a personal data breach affecting Customer Personal Data without undue delay, and in any event within 48 hours of becoming aware of it.
  • The notice describes, as far as then known, the nature of the breach, the categories and approximate numbers of people and records affected, the likely consequences, the measures taken or proposed, and a contact point. OneTaskList adds information as it becomes available.
  • OneTaskList doesn’t notify the Customer’s supervisory authorities or users on the Customer’s behalf, unless the Customer asks or the law requires it.
  • A notice is not an admission of fault or liability.

10. Where data is processed, and transfers

  • The Customer chooses the region where its Customer Personal Data is stored: the EU (Netherlands), the UK (London), the US (Virginia) or Australia (Melbourne). Sign-in runs in the EU for every region. Annex I lists where each part of the processing happens.
  • OneTaskList is established in Australia and its staff support the service from there. Where Customer Personal Data subject to the GDPR is transferred to OneTaskList (including remote access from Australia), the SCCs apply as follows, and are incorporated into this DPA by reference:
SCC choiceApplies as
ModuleModule Two (controller to processor)
Clause 7 (docking clause)Included
Clause 9(a) (sub-processors)Option 2, general written authorisation, with 30 days’ notice (clause 6 of this DPA)
Clause 11(a) (independent dispute resolution)The optional wording does not apply
Clause 13 (supervisory authority)As set out in Annex I.C
Clause 17 (governing law)The law of [Ireland]
Clause 18 (courts)The courts of [Ireland]
AnnexesAnnex I, II and III of this DPA complete the SCC Annexes
  • UK: for data subject to the UK GDPR, the UK Addendum applies. Its tables are completed with the information in this DPA and its Annexes, and either party may end it as Section 19 of the UK Addendum allows.
  • Switzerland: for data subject to the Swiss Federal Act on Data Protection, the SCCs apply with these changes: the FDPIC is the competent supervisory authority; references to the GDPR include the Swiss Act; “member state” includes Switzerland, so Swiss data subjects can enforce their rights there.
  • OneTaskList transfers Customer Personal Data to sub-processors outside the region only as Annex III describes, with appropriate safeguards.

11. Information and audits

  • OneTaskList makes available the information needed to show it meets this DPA and Art. 28 GDPR.
  • The Customer, or an independent auditor bound by confidentiality, may audit OneTaskList’s compliance once in any 12 months, with at least 30 days’ written notice, during business hours, and at the Customer’s cost. An extra audit is allowed after a personal data breach or when a supervisory authority requires it.
  • Audits must not give access to other customers’ data or breach OneTaskList’s security.

12. Return and deletion

  • During the Agreement, the Customer and its users can export their data at any time.
  • When the Agreement ends, OneTaskList deletes Customer Personal Data within 30 days, unless the law requires it to keep some. Copies in backups are deleted within a further 30 days as the backups expire.
  • On request, OneTaskList confirms the deletion in writing.

13. Liability

Each party’s liability under this DPA is subject to the limits in the Agreement, except where Data Protection Law or the SCCs don’t allow liability to be limited.

14. Order of precedence and term

  • If documents conflict, the SCCs (and the UK Addendum) win, then this DPA, then the Agreement.
  • This DPA lasts as long as OneTaskList processes Customer Personal Data.
  • This DPA is governed by the law that governs the Agreement, except that the SCCs and UK Addendum are governed by the law they name.

Signatures

CustomerOneTaskList Pty Ltd
Name: [name]Name: [name]
Title: [title]Title: [title]
Date: [date]Date: [date]
Signature:Signature:

Annex I: The parties and the processing

A. Parties

Data exporter (controller)Data importer (processor)
Name[Customer legal name]OneTaskList Pty Ltd (ACN 698 036 798)
Address[Customer address]Level 15, 461 Bourke Street, Melbourne VIC 3000, Australia
Contact[Customer privacy contact]Silke McManus, privacy contact, privacy@onetasklist.com
EU / UK representative[if any][Altus EU entity] / [Altus UK entity]
ActivitiesUses OneTaskList for its peopleProvides the OneTaskList service

B. Description of the processing

People whose data is processed

The Customer’s authorised users.

People named in the users’ tasks, such as colleagues, customers and the senders of emails.

Categories of personal data

Account data: name, email address, profile picture, sign-in provider ID, chosen region.

Sign-in record: IP address, browser, time, acceptance of terms.

Connections: access tokens issued by connected tools, and the connected account’s name.

Task content copied from connected tools: title, notes, tags, link, status and dates.

Boards, columns, membership and settings.

Browser push subscriptions, if users turn notifications on.

Technical logs: IP address, requests, errors, user ID.

Sensitive dataNone is intended. Tasks copied from the Customer’s tools may contain it incidentally; the Customer decides which tools its users connect.
FrequencyContinuous, for the term of the Agreement.
Nature of the processingHosting and storage; copying items from connected tools and showing them on boards; writing changes back to those tools at users’ direction; sending notifications and service emails; backup; support.
PurposeProviding the OneTaskList service under the Agreement.
How longFor the term of the Agreement, then deleted within 30 days (backups within a further 30 days). Technical logs: 90 days. Sign-in record: 3 years after the user’s last sign-in, or on account deletion.
WhereStored in the Customer’s chosen region (EU, UK, US or Australia), with backup copies in Azure’s paired region. Sign-in in the EU. Alerts about new sign-ups in Australia. Support access from Australia.

C. Competent supervisory authority

The supervisory authority of the EU member state where the Customer’s EU representative is established or, if the Customer is established in the EU, the authority competent for the Customer. For UK data: the Information Commissioner. For Swiss data: the FDPIC.

Annex II: Security measures

Measures in place on [date]. OneTaskList keeps this list current.

AreaMeasures
EncryptionAll traffic over HTTPS. Data encrypted at rest by Azure. On top of that, access tokens, names, task titles, notes and tags are encrypted by the application, with keys stored in Azure Blob Storage and wrapped by a key in Azure Key Vault.
SeparationEach region has its own databases and storage. Customers can have a region of their own, in our Azure subscription or theirs.
Sign-inUsers sign in through Microsoft, Google or GitHub; OneTaskList stores no user passwords. Sign-in pages load no third-party scripts or fonts.
Staff accessProduction access limited to [n] named people, with multi-factor authentication, through Azure role-based access control. Access reviewed [quarterly].
Application securityContent Security Policy, anti-forgery tokens, and no third-party analytics or advertising scripts. Changes go through code review and automated tests before release.
Backups and recoveryCosmos DB continuous backup (30 days). Geo-redundant storage with read access in Azure’s paired region. Blob soft delete (30 days).
Logging and monitoringApplication Insights and Azure Monitor logs in each region, kept 90 days.
IncidentsA written personal data breach procedure: customers are told within 48 hours.
DeletionSelf-service export and account deletion; deletion of a customer’s data within 30 days of the Agreement ending.
PeopleStaff and contractors bound by confidentiality, and briefed on the breach procedure.
TestingAutomated test suites on every change. [External penetration test: none yet].

Annex III: Sub-processors

Sub-processorWhat it doesWhere
Microsoft (Azure)Hosting, databases, storage, logs, encryption keys, and sending service emails (Azure Communication Services)The Customer’s chosen region; sign-in in the EU; backups in the paired region
Microsoft (Microsoft 365)Internal alerts to the OneTaskList team about new sign-ups and feedback (name, email address, region)Australia
Browser push services (Google, Mozilla, Apple, Microsoft)Delivering notifications, only for users who turn them on. The user’s browser picks the serviceTheir own infrastructure

Not sub-processors: the tools the Customer’s users connect, and AI providers users choose with their own keys. They act under the Customer’s or user’s own agreements. When the Customer runs OneTaskList in its own Azure subscription, Microsoft is the Customer’s processor for that hosting, not ours.

Annex IV: Article 28(3) checklist

Art. 28(3)RequirementClause
PreambleSubject matter, duration, nature, purpose, data types, data subjectsAnnex I
(a)Process only on documented instructions, including for transfers3, 10
(b)Confidentiality of authorised persons4
(c)Security measures (Art. 32)5, Annex II
(d)Conditions for engaging sub-processors6, Annex III
(e)Help with data subject requests7
(f)Help with Art. 32–36 obligations8, 9
(g)Deletion or return at the end12
(h)Information and audits; tell the controller about unlawful instructions3, 11

Questions about this page? Contact us at legal@onetasklist.com.