👨‍⚖️ Legal Information

Data Processing Agreement

Last updated: May 28, 2026.

This Data Processing Agreement (“DPA”) is between:

The company (collectively “Customer”) identified by acceptance of the Service Agreement, and Hello Clerk, Inc., a Delaware corporation with its principal place of business at 651 N Broad St, Suite 206, Middletown, DE 19709, USA (“Hello Clerk”).

Together the “Parties” and each a “Party”.

This DPA is incorporated into and supplements the Terms of Services and/or End User License Agreement between the Parties. By using the Services, Customer accepts this DPA. No separate signature is required.

The Parties agree as follows:

1. Subject matter of this DPA

1.1. This DPA applies to the Processing of Personal Data that is subject to the EU General Data Protection Regulation (“GDPR”) (Regulation (EU) 2016/679).

1.2. This DPA supplements the terms of the Terms of Services (“ToS”) and/or the End User License Agreement (“EULA”) (each is a “Service Agreement”), under which Hello Clerk provides certain services (“Services”).

1.3. To the extent Hello Clerk processes Personal Data subject to the GDPR on behalf of Customer in the course of the performance of a Service Agreement, the terms of this DPA shall apply.

1.4. This DPA shall apply for the duration of the Service Agreement and supersedes any prior data processing terms between the Parties.

2. Definitions

2.1. The terms “Processing”, “Personal Data”, “Controller”, “Processor”, “Personal Data Breach”, “Supervisory Authority”, “Commission”, and “Member State” shall have the meanings given in the GDPR, and their cognate terms shall be construed accordingly.

2.2. “Customer Data” means all Personal Data which is provided to Hello Clerk (or to any sub-processor) by the Customer in connection with the Service Agreement.

2.3. “Standard Contractual Clauses” or “SCCs” means the standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679, as set out in Commission Implementing Decision (EU) 2021/914 of 4 June 2021.

2.4. “Sub-processor” means any third party engaged by Hello Clerk to process Customer Data on Hello Clerk’s behalf in the course of providing the Services.

3. Customer and Hello Clerk

3.1. Customer

3.1.1. Customer is the Data Controller. Customer will comply with the applicable GDPR obligations with respect to the processing of Customer Data (Art. 24 GDPR). Customer will not instruct Hello Clerk to process any Customer Data in a manner that would constitute a breach of the GDPR.

3.1.2. Customer warrants that Customer has all the necessary rights, legal bases, and consents required to provide the Customer Data to Hello Clerk for the Processing to be performed in relation to the Services. Customer is solely responsible for the accuracy, quality, and legality of Customer Data and the means by which Customer acquired it. Should a consent be revoked by the data subject, Customer is responsible for promptly communicating such revocation to Hello Clerk.

3.1.3. Customer acknowledges that Hello Clerk’s provision of the Services as an Atlassian Marketplace application requires Customer to maintain its own separate agreements with Atlassian Pty Ltd. Atlassian is not a Sub-processor of Hello Clerk under this DPA. Atlassian acts as an independent data controller (or, as applicable, an independent processor) under its own terms in respect of the Atlassian platform.

3.1.4. The Services may allow Customer to connect, at Customer’s own initiative, third-party services (such as accounting, time-tracking, or invoicing platforms) to which Hello Clerk transmits data on Customer’s documented instruction. When Customer enables any such integration, Customer authorises Hello Clerk to transmit Customer Data to Customer’s own account at the relevant third-party service. Such third-party services are not Sub-processors of Hello Clerk under this DPA; they act as independent data controllers (or, as applicable, independent processors of Customer) under their own terms with Customer. Customer is solely responsible for its agreements with such third-party services and for the lawfulness of any onward processing by them.

3.1.5. Customer shall indemnify and hold harmless Hello Clerk against any claims, damages, fines, penalties, costs (including reasonable legal fees), or losses arising from or in connection with Customer’s breach of its obligations under this DPA, including unlawful or non-compliant instructions to Hello Clerk, failure to obtain necessary consents or legal bases for processing, or submission to the Services of categories of data prohibited under this DPA.

3.2. Hello Clerk

3.2.1. Hello Clerk is the Data Processor. Hello Clerk will comply with the applicable obligations of a Processor under Art. 28 GDPR with respect to the processing of Customer Data.

4. Processing Instructions

4.1. Hello Clerk will process Customer Data only as set forth in Customer’s documented instructions, which are provided through:

  • the Service Agreement;
  • this DPA;
  • Customer’s configuration and use of the Services; and
  • any further instructions agreed in writing by the Parties,

and only to the extent that the processing is appropriate for the provision of the Services. Hello Clerk shall not be required to comply with instructions that, in Hello Clerk’s reasonable opinion, conflict with the GDPR or fall outside the scope of the Services.

4.2. Hello Clerk may process Customer Data where required by applicable law to which Hello Clerk is subject (Art. 28(3)(a) GDPR). In such a case, Hello Clerk shall notify Customer of that legal obligation before processing, unless that law explicitly prohibits such notification on important grounds of public interest.

4.3. The details of the processing are described in Exhibit 2 (Description of Processing) and, where applicable, Annex I to the Standard Contractual Clauses incorporated into this DPA.

4.4. If Hello Clerk reasonably believes that an instruction from Customer violates the GDPR or falls outside the scope of the Services, Hello Clerk may, without liability to Customer, suspend the performance of such instruction until the matter is resolved between the Parties.

5. Confidentiality (Art. 28(3)(b) GDPR)

Hello Clerk shall treat all Customer Data as confidential and shall ensure that all of its personnel, agents, and Sub-processors engaged in the processing of Customer Data are bound by written confidentiality obligations or are under an appropriate statutory obligation of confidentiality.

6. Security (Art. 28(3)(c) and Art. 32 GDPR)

6.1. Hello Clerk shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, in accordance with Art. 32 GDPR. The current security measures are described in Annex II (Technical and Organisational Measures).

6.2. The Parties acknowledge that security requirements are constantly changing and that effective security requires frequent evaluation and improvement. Accordingly, Hello Clerk may update or modify the measures set out in Annex II from time to time, provided that such updates and modifications do not result in a material degradation of the protection offered by such measures.

6.3. Customer is solely responsible for: (a) determining what Customer Data is submitted to the Services and ensuring that such data falls within the categories described in Exhibit 2; (b) properly configuring the Services and using the security features made available by the Services; (c) managing access permissions of Customer’s end users; and (d) taking such steps as Customer considers adequate to maintain appropriate security, protection, deletion, and backup of Customer Data on Customer’s own systems. Hello Clerk shall have no liability for Customer Data submitted to the Services in violation of this DPA, including any special categories of data prohibited under Exhibit 2.

7. Sub-processing (Art. 28(2) and Art. 28(4) GDPR)

7.1. Customer provides Hello Clerk with a general written authorisation to engage Sub-processors to process Customer Data in connection with the provision of the Services.

7.2. A current list of Sub-processors engaged by Hello Clerk is set out in Annex III (List of Sub-processors) and is published at https://helloclerk.io/legal/sub-processors/.

7.3. Hello Clerk shall notify Customer of any intended changes concerning the addition or replacement of Sub-processors at least thirty (30) days in advance by updating the published list of Sub-processors.

7.4. Customer may object to the engagement of a new Sub-processor within fifteen (15) days of such notification on reasonable data protection grounds, by providing written notice with a description of the grounds for objection to legal@helloclerk.io. If Customer objects, the Parties shall discuss the objection in good faith. If the Parties cannot reach a mutually acceptable resolution within thirty (30) days, Customer’s sole and exclusive remedy shall be to terminate the affected Services without penalty by providing written notice to Hello Clerk. Termination shall not entitle Customer to any refund of pre-paid fees beyond the unused portion of the then-current subscription term.

7.5. With respect to each Sub-processor, Hello Clerk shall:

  • carry out adequate due diligence before the Sub-processor first processes any Customer Data to ensure that the Sub-processor is capable of providing the level of protection for Customer Data required by this DPA;
  • ensure that the arrangement is governed by a written contract including terms that offer at least the same level of protection for Personal Data as those set out in this DPA and that meet the requirements of Art. 28(3) GDPR; and
  • remain liable to Customer for the acts and omissions of its Sub-processors to the same extent Hello Clerk would be liable if performing the services of each Sub-processor directly under the terms of this DPA, subject to the limitations of liability set out in Section 13 and the Service Agreement.

8. International Data Transfers (Art. 44–46 GDPR)

8.1. Customer Data is stored and processed within the European Union (Germany) by Hello Clerk’s hosting Sub-processor. Hello Clerk does not routinely transfer Customer Data outside the European Economic Area for storage or primary processing purposes.

8.2. To the extent Hello Clerk, Inc. (as a U.S. entity) accesses Customer Data from a country outside the European Economic Area in connection with the provision of administrative, support, or development activities, such access constitutes an international transfer of Personal Data for the purposes of the GDPR. The Parties agree that any such transfer shall be governed by the Standard Contractual Clauses (Module Two: Controller-to-Processor), which are hereby incorporated into this DPA by reference and shall apply as if set out in full herein.

8.3. The Standard Contractual Clauses shall be deemed completed as follows:

  • Module Two (Controller-to-Processor) applies;
  • Clause 7 (Docking Clause) does not apply;
  • Clause 9 — Option 2 (general written authorisation) applies, with the time period set out in Section 7.3 of this DPA;
  • Clause 11(a) — the optional redress provision does not apply;
  • Clause 13 — the supervisory authority is the supervisory authority competent for the data exporter under applicable law;
  • Clause 17 (Governing Law) — the Clauses shall be governed by the law of Ireland;
  • Clause 18 (Choice of forum and jurisdiction) — the courts of Ireland;
  • Annex I, Annex II, and Annex III of the Clauses are completed by the corresponding Annexes to this DPA.

8.4. If, in the future, Hello Clerk relies on an adequacy decision of the European Commission as a basis for the transfer, such adequacy decision shall serve as the basis for the transfer, and the Standard Contractual Clauses shall apply only to the extent the adequacy decision does not cover such transfer.

8.5. If a basis for international data transfers is subsequently modified, revoked, or held by a court of competent jurisdiction to be invalid, the Parties agree to cooperate in good faith to identify and implement an alternative lawful transfer mechanism without undue delay.

9. Data Subject Rights (Art. 28(3)(e) GDPR)

9.1. Taking into account the nature of the processing, Hello Clerk shall use commercially reasonable endeavours to assist Customer, by appropriate technical and organisational measures and insofar as this is possible, in fulfilling Customer’s obligations to respond to requests by data subjects exercising their rights under Chapter III of the GDPR.

9.2. Customer shall make any such request for assistance in writing to legal@helloclerk.io. Hello Clerk shall respond within fourteen (14) days for routine requests. For requests that are complex, voluminous, or that require Hello Clerk to develop new technical functionality, Hello Clerk may extend this period by up to thirty (30) additional days upon written notice to Customer, in accordance with Art. 12(3) GDPR.

9.3. Hello Clerk shall not charge Customer for reasonable assistance with data subject requests within the scope of the subscription. Hello Clerk reserves the right to charge a reasonable fee for requests that are manifestly unfounded, excessive, repetitive, or that require the development of bespoke technical solutions, in each case after prior written notice to Customer.

9.4. Hello Clerk shall not disclose Customer Data directly to any data subject or to any third party. Responsibility for responding to requests from data subjects shall remain with Customer.

10. Cooperation and Audits (Art. 28(3)(f) and (3)(h) GDPR)

10.1. Hello Clerk shall, taking into account the nature of the processing and the information available to Hello Clerk, provide reasonable assistance to Customer in ensuring compliance with Customer’s obligations under Articles 32 to 36 GDPR (security, breach notification, data protection impact assessments, and prior consultation with supervisory authorities).

10.2. Hello Clerk shall make available to Customer all information reasonably necessary to demonstrate compliance with the obligations laid down in Art. 28 GDPR. Customer shall submit requests for such information in writing to legal@helloclerk.io, and Hello Clerk shall respond within thirty (30) days of receiving the request.

10.3. The Parties agree that Hello Clerk’s obligation to allow for and contribute to audits under Art. 28(3)(h) GDPR shall be satisfied through the following documentation-based mechanisms, which the Parties acknowledge are appropriate and proportionate to the nature, scope, context, and purposes of the processing and the risks to data subjects:

  • Hello Clerk shall respond in writing to Customer’s reasonable written requests for information regarding Hello Clerk’s compliance with this DPA;
  • Hello Clerk shall complete a reasonable industry-standard security questionnaire submitted in writing by Customer, at a frequency not to exceed once in any twelve (12) month period;
  • Hello Clerk shall, upon written request and subject to applicable confidentiality obligations, make available any then-current third-party certifications, audit reports, or attestations that Hello Clerk has obtained.

10.4. Customer shall not have the right to conduct, and Hello Clerk shall not be required to permit, on-site audits, inspections, or remote technical access to Hello Clerk’s systems, premises, or personnel. Customer acknowledges that the documentation-based mechanisms in Section 10.3 are designed to satisfy Customer’s audit rights under Art. 28(3)(h) GDPR without exposing Hello Clerk’s systems, other customers’ data, or confidential business information to undue risk.

10.5. Notwithstanding Section 10.4, where a supervisory authority of competent jurisdiction issues a binding legal order specifically directed at Hello Clerk and requiring an on-site inspection in connection with Customer’s processing activities, the Parties shall cooperate in good faith to facilitate such inspection in a manner consistent with applicable law, the protection of other customers’ data, and Hello Clerk’s confidentiality obligations. Customer shall promptly notify Hello Clerk in writing of any such order upon becoming aware of it, and shall provide Hello Clerk with a copy of the order to the extent permitted by law. Any costs incurred by Hello Clerk in connection with such inspection shall be borne by Customer, except to the extent the inspection is the direct result of Hello Clerk’s confirmed material breach of this DPA.

10.6. All information and documentation provided by Hello Clerk under this Section 10 shall be deemed Hello Clerk’s confidential information, and Customer shall not disclose such information to any third party without Hello Clerk’s prior written consent, except to Customer’s legal advisors and supervisory authorities under a duty of confidentiality.

11. Personal Data Breach (Art. 33–34 GDPR)

11.1. Hello Clerk shall notify Customer without undue delay, and in any event within seventy-two (72) hours, after becoming aware of a Personal Data Breach affecting Customer Data. The Parties acknowledge that the obligation under this Section 11.1 applies only from the time Hello Clerk has confirmed knowledge of a Personal Data Breach. Hello Clerk does not warrant that all Personal Data Breaches will be detected immediately upon their occurrence, particularly where such breaches result from sophisticated, novel, or concealed attack methods. For the avoidance of doubt, temporary unavailability of Customer Data resulting from planned maintenance, scheduled downtime, infrastructure outages, or service interruptions that do not involve unauthorised access to, or loss of, Customer Data shall not constitute a Personal Data Breach for the purposes of this DPA.

11.2. Notifications under this Section shall be delivered to the contact details designated by Customer in Customer’s account settings (or, in the absence thereof, to the email address associated with Customer’s subscription), and shall include, to the extent then known and to the extent permitted by applicable law:

  • a description of the nature of the Personal Data Breach, including, where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of Personal Data records concerned;
  • a contact point where more information can be obtained;
  • a description of the likely consequences of the Personal Data Breach; and
  • a description of the measures taken or proposed to be taken by Hello Clerk to address the Personal Data Breach, including measures to mitigate its possible adverse effects.

11.3. Where, and to the extent that, it is not possible to provide the information at the same time, the information may be provided in phases without further undue delay.

11.4. Hello Clerk shall cooperate with Customer and provide reasonable assistance with respect to the investigation, mitigation, and remediation of any Personal Data Breach.

11.5. Hello Clerk’s notification of, or response to, a Personal Data Breach under this Section shall not be construed as an acknowledgement by Hello Clerk of any fault or liability with respect to the Personal Data Breach.

11.6. Hello Clerk’s obligations and timelines under this Section 11 are subject to circumstances beyond Hello Clerk’s reasonable control, including but not limited to acts of war, armed conflict, civil unrest, acts of terrorism, cyberattacks of nation-state origin, natural disasters, pandemics, governmental orders or restrictions, prolonged network or infrastructure outages, and any other force majeure events. In such circumstances, Hello Clerk shall use commercially reasonable efforts to notify Customer as soon as reasonably practicable.

12. Return or Destruction of Personal Data (Art. 28(3)(g) GDPR)

12.1. Following the termination or expiry of the Service Agreement, Hello Clerk shall, upon Customer’s written request, either delete or return all Customer Data to Customer, and delete existing copies, within a reasonable period not exceeding ninety (90) days from the date of the request. Customer acknowledges that any Customer Data that may also reside within Customer’s Atlassian environment is subject to Customer’s separate agreement with Atlassian, and Hello Clerk’s deletion obligations under this Section do not extend to data held by Atlassian or any other third party outside Hello Clerk’s control.

12.1.1. In the absence of a written request from Customer, Hello Clerk may retain Customer Data on the basis of Hello Clerk’s legitimate interest in enabling Customer to seamlessly reinstall and resume use of the Services in the future, without the time and cost of reconfiguration. Such retention is subject to Customer’s right at any time to request deletion of Customer Data in accordance with Section 12.1.

12.1.2. Notwithstanding Sections 12.1 and 12.1.1, Hello Clerk reserves the right to delete Customer Data of any Customer who has not had an active paid subscription to the Services for more than two (2) consecutive months. Hello Clerk will provide reasonable advance notice to the email address associated with the Customer’s account before deleting Customer Data under this Section 12.1.2.

12.2. Notwithstanding the foregoing, Hello Clerk may retain Customer Data to the extent and for such period as required by applicable law, or where Customer Data is held in routine backup media that is not readily accessible, provided that such retained Customer Data remains subject to the confidentiality and security obligations of this DPA and is not subject to active processing.

12.3. Customer acknowledges that, following deletion, Customer Data may be unrecoverable, and Hello Clerk shall have no obligation to retain or restore Customer Data thereafter.

13. Limitation of Liability

13.1. Each Party’s liability arising out of or related to this DPA, whether in contract, tort, or under any other theory of liability, is subject to the limitations and exclusions of liability set out in the Service Agreement, and any reference to the liability of a Party in the Service Agreement shall be deemed to include the liability of that Party under this DPA.

13.2. In no event shall either Party’s liability to the other under this DPA exceed the lower of (a) the aggregate amount of fees actually paid by Customer to Hello Clerk under the Service Agreement during the six (6) months immediately preceding the event giving rise to the claim, or (b) one thousand United States dollars (USD $1,000).

13.3. Nothing in this DPA limits or excludes either Party’s liability where such limitation or exclusion is prohibited by applicable law.

14. Term and Termination

This DPA shall remain in effect for the duration of the Service Agreement and shall automatically terminate upon the later of (a) the termination or expiry of the Service Agreement, or (b) Hello Clerk ceasing to process any Customer Data.

15. General Terms

15.1. The terms of the Service Agreement shall apply to this DPA, except as expressly modified herein.

15.2. Order of Precedence. In the event of any conflict or inconsistency between the documents governing the relationship between the Parties, the order of precedence shall be:

  1. the Standard Contractual Clauses (where applicable);
  2. this DPA;
  3. the Service Agreement.

15.3. Updates. Hello Clerk may update this DPA from time to time to reflect changes in applicable law, regulatory guidance, the Services, or Hello Clerk’s practices. Material changes will be communicated to Customer at least thirty (30) days in advance of taking effect, by updating the version published at https://helloclerk.io/legal/data-processing-agreement/. Continued use of the Services after the effective date of an updated DPA constitutes acceptance of the updated DPA.

15.4. Contact. All notices, requests, and communications under this DPA shall be sent to legal@helloclerk.io.

Annex I to the Standard Contractual Clauses

A. List of Parties

Data exporter: The Customer, as identified by acceptance of the Service Agreement and use of the Services. Role: Controller.

Data importer: Hello Clerk, Inc., 651 N Broad St, Suite 206, Middletown, DE 19709, USA. Contact: legal@helloclerk.io. Role: Processor. Activities relevant to the data transferred: provision of the Services as described in the Service Agreement.

B. Description of Transfer

  • Categories of data subjects: (a) employees, contractors, and agents of Customer who use or are referenced within the Services; (b) recipients of documents, communications, or records generated or sent through the Services; and (c) any other natural persons referenced in free-text fields of the Services where Customer chooses to include such references.
  • Categories of personal data: name, email address, Atlassian account identifier; time entries, work logs, and task assignments; monetary amounts, prices, rates, budget figures, and line items within documents and records generated through the Services; Jira issue keys, summaries, descriptions, and comments; names and email addresses of recipients; configuration data entered by Customer.
  • Sensitive data: None. Customer shall not submit special categories of personal data (Art. 9 GDPR) or personal data relating to criminal convictions and offences (Art. 10 GDPR) to the Services.
  • Frequency of transfer: Continuous, for the duration of the Service Agreement.
  • Nature of the processing: Storage, retrieval, organisation, and provision of the Services described in the Service Agreement.
  • Purpose of the transfer and further processing: Provision of the Services and related technical support to Customer.
  • Retention period: For the duration of the Service Agreement, and thereafter as set out in Section 12 of this DPA.
  • Sub-processors: As listed in Annex III.

C. Competent Supervisory Authority

The competent supervisory authority shall be the supervisory authority of the Member State in which the Customer (as data exporter) is established, or, where the Customer is established outside the European Union but has appointed a representative pursuant to Art. 27 GDPR, the supervisory authority of the Member State in which such representative is established.

Annex II — Technical and Organisational Measures

Hello Clerk implements and maintains the following technical and organisational measures to ensure the security of Customer Data, in accordance with Art. 32 GDPR. Hello Clerk may update these measures from time to time, provided that the level of security is not materially degraded.

1. Physical access control

Customer Data is hosted in data centres operated by Hello Clerk’s hosting Sub-processor (Hetzner Online GmbH) located in Germany. The data centres implement industry-standard physical access controls, including 24/7 access monitoring, video surveillance, and access restricted to authorised personnel.

2. Logical access control

Access to production systems is restricted to authorised Hello Clerk personnel on a need-to-know basis. Multi-factor authentication is enforced for all administrative access to production systems. Access rights are reviewed periodically and revoked promptly upon termination of personnel.

3. Data segregation

Customer Data is logically segregated such that each Customer’s data is accessible only in the context of that Customer’s use of the Services.

4. Encryption in transit

Customer Data is encrypted in transit over public networks using industry-standard Transport Layer Security (TLS) protocols.

5. Backup and recovery

Hello Clerk maintains regular automated backups of Customer Data. Backup and restoration procedures are tested periodically.

6. Logging and monitoring

Hello Clerk maintains logs of access to production systems and material changes to production environments. Logs are reviewed periodically and as part of incident response.

7. Personnel

All Hello Clerk personnel with access to Customer Data are bound by written confidentiality obligations. Personnel are required to follow Hello Clerk’s internal security policies and receive guidance on data protection appropriate to their role.

8. Incident response

Hello Clerk maintains internal procedures for the identification, escalation, investigation, and remediation of security incidents and Personal Data Breaches, including the notification obligations set out in Section 11 of this DPA.

9. Vendor management

Hello Clerk performs due diligence on Sub-processors before engagement, including assessment of their security practices and contractual commitments to data protection.

Annex III — List of Sub-processors

The current list of Sub-processors engaged by Hello Clerk for the processing of Customer Data is maintained and published at https://helloclerk.io/legal/sub-processors/.

The list as published at the time of acceptance of this DPA forms part of this Annex III. Hello Clerk shall notify Customer of any intended changes by updating the published list in accordance with Section 7.3 of this DPA.

Exhibit 1 — Contact

All notices, requests, and communications under this DPA shall be sent to legal@helloclerk.io.

Exhibit 2 — Description of Processing (Art. 28(3) GDPR)

Subject matter of processing

Hello Clerk’s provision of the Services to Customer, and related technical support.

Duration of processing

The personal data will be processed in connection with the Services for the duration of the Service Agreement, or such shorter period where the processing is no longer authorised, and in respect of any post-termination processing activities permitted by the Customer or required by applicable law.

Nature and purpose of the processing

Hello Clerk will process Customer Data submitted to, stored on, or sent via the Services for the purpose of providing the Services and related technical support.

Categories of data subjects

The Services may process Personal Data relating to the following categories of data subjects:

  • Employees, contractors, and agents of Customer who use or are referenced within the Services (including users of Customer’s Atlassian Jira instance whose data is synchronised to the Services);
  • Recipients of documents, communications, or records generated or sent through the Services (typically employees or representatives of Customer’s own clients, counterparties, or other business contacts);
  • Any other natural persons referenced in free-text fields of the Services (such as descriptions, comments, line items, or notes), where Customer chooses to include such references.

Type of personal data

The Services may process the following categories of Personal Data:

  • Identification data: name, email address, and Atlassian account identifier of users referenced within Customer’s Atlassian Jira instance;
  • Work activity data: time entries, work logs, task assignments, and similar records of user activity;
  • Financial and commercial data relating to Customer’s business operations: monetary amounts, prices, rates, budget figures, line items, and similar entries within documents and records generated through the Services;
  • Jira issue data: issue keys, summaries, descriptions, comments, and other content from Customer’s Jira instance, to the extent included by Customer;
  • Communication and recipient data: names and email addresses of recipients of documents, communications, or records generated or sent through the Services;
  • Configuration data entered by Customer through the Services.

Hello Clerk does not require, and Customer shall not submit through the Services, special categories of personal data within the meaning of Art. 9 GDPR or personal data relating to criminal convictions and offences within the meaning of Art. 10 GDPR. Customer is solely responsible for the content of any free-text fields and for ensuring that such fields do not contain prohibited categories of data.

Have question? ✉️ Contact us. We are ❤️ happy to talk!

Hello Clerk, Inc.
651 N Broad St, Suite 206, Middletown, DE 19709, USA