Close Reviewfor Jira

Data Processing Addendum

Version: 20 September 2026, v1.

Upon incorporation through the provider-specific customer terms, the parties adopt the unmodified Bonterms Data Protection Addendum Version 2.0, Attachment Version, including its Exhibits A and B, with the completed details below. The base DPA and these details together constitute the Data Processing Addendum. A later change to the source website's standard version does not change the agreed version.

Key terms

Field Agreed detail
Main Agreement The Bonterms Standard End User Agreement 1.0 and Close Review provider-specific terms incorporated in the customer's Marketplace order for Close Review for Jira
DPA effective date The effective date of that Main Agreement; applies while Provider processes customer personal data under it
Subprocessor list The list in this document below
Designated EU Governing Law Ireland, for the EU Standard Contractual Clauses where applicable
Designated EU Member State Ireland, for disputes under those EU clauses

Parties and processing details

Customer / data exporter: the organization or individual business placing the Marketplace order. Its name, main address and billing/administrative contact in that order are incorporated here. Customer may designate a different privacy contact by written notice to Provider. Its activities are the business activities for which it uses Jira and Close Review. Its role is controller or, when processing for another controller, processor; the corresponding SCC module applies.

Provider / data importer: Tan Oguz, an individual trading as TanSolutions. Main address: Sukhumvit 34, Khlong Toei, Bangkok 10110, Thailand. Data protection contact: oguztan48@proton.me. Provider supplies and supports the Close Review Jira worklog comparison service. Its role for customer personal data is processor.

Subject matter and purpose: operating and supporting the selected Jira worklog capture, comparison, review and export workflow under customer instructions; protecting access; handling customer-directed erasure and applicable privacy requests.

Data subjects: customer users, employees and contractors whose Jira worklogs or review activity are included. Other persons may be mentioned in customer-entered text; customers should keep such text minimal and avoid unnecessary personal data.

Personal-data categories: Jira account identifiers needed for privacy handling; installation, project, issue and worklog identifiers; worklog dates and durations; review decisions, timestamps, period names and free-text notes; and business contact details and messages voluntarily supplied for support. The app does not retain Jira profile names, email addresses, worklog comments or issue descriptions in its review snapshots. Names or other information typed by a customer into notes remain customer content. Customer credentials, bank details and special-category data are not requested for the product workflow.

Sensitive or special-category data: not permitted or needed for the intended service. Customers must not submit it. If inadvertently supplied, it is restricted to handling the affected request and erasure as instructed or required by law.

Frequency: whenever an authorized customer starts a check or review action and, if enabled, during scheduled checks. Account privacy reporting is periodic. Support processing occurs when a customer contacts support.

Nature: retrieval, selection, normalization, storage, comparison, access checks, review annotation, export, privacy reporting, restriction and erasure. No sale, advertising use or AI training on customer data is authorized.

Duration and retention: period records are retained for up to 90 days after creation, subject to earlier customer erasure, applicable privacy instructions or account erasure handling. Physical Forge deletion and uninstall retention follow the current privacy disclosure. Limited post-subscription export/erasure access does not extend the period's retention. Support messages are deleted within 90 days after resolution unless a shorter valid instruction or legal retention requirement applies. Retained legal records are restricted to that purpose. Return and deletion otherwise follow section 8 of the DPA; a customer may request a deletion confirmation.

Transfers to subprocessors: limited to the functions below. The customer retains control of any files it exports or voluntarily sends to its own providers.

Competent EU supervisory authority: the authority determined under clause 13 of the applicable EU SCCs for the customer's establishment or representative. A customer may identify the specific authority in its written order or privacy notice to Provider.

Subprocessors

Provider Function and data Location and safeguards
Atlassian, through the entity providing Forge under Provider's Forge agreement Forge compute, installation-scoped storage, queues, Jira API access and privacy-reporting infrastructure Platform regions and operational locations described in Forge's DPA and Atlassian's applicable subprocessor disclosures; processing follows the installation's supported platform residency configuration. No separate TanSolutions worklog database or external app backend.
Proton AG Email support: business contact information and customer-supplied messages/attachments only Switzerland and locations disclosed by Proton for its service. Proton DPA and privacy policy. The app does not automatically forward Jira worklog evidence to email.

Cloudflare delivers the public documentation website and may process ordinary web request information. It receives no worklog data from the installed app. Website request processing is described in the privacy disclosure; it is separate from the customer-instructed Jira processing covered by this DPA. No AI provider receives customer data from the app.

Provider will give at least 30 days' advance notice by email or in-product notice to an administrator before a new subprocessor processes customer personal data. The objection procedure in section 4.4 of the base DPA applies. No subcontractor is appointed merely by being suggested in a future product plan.

Technical and organizational measures

The security page is incorporated as Security Measures. In addition:

No independent audit certification, penetration-test certification, zero-incident guarantee or contractual uptime commitment is asserted. Audit and assistance rights are those in the base DPA. Mandatory data-subject and regulator rights are preserved.

Additional terms

None. The completed details describe the service and do not amend the unmodified Bonterms DPA. The DPA's precedence rules, mandatory transfer clauses and region-specific terms control in the event of a conflict with the Main Agreement.

Bonterms Data Protection Addendum 2.0 © 2026 Bonterms, Inc., used under CC BY 4.0. Bonterms is not a party and does not provide a guarantee that this arrangement meets the parties' legal needs.