Worklog Ledger data processing
Prepared October 5, 2026. Provider: Alexander Landaverde. This page describes the native Jira launch workflow and the customer DPA process.
Customer DPA
A customer-specific agreement based on the Bonterms Data Protection Addendum v2.0 (Attachment Version) is prepared for execution. Contact support@alexanderlandaverde.com to complete the customer legal name, address, privacy contact, designated administrator, processing role and Marketplace order. Provider address details are supplied privately in the execution copy.
The completed agreement expressly incorporates the standard DPA, its processing details and applicable transfer exhibits into the customer agreement. This information page is not an executed DPA and does not itself establish a completed transfer agreement for a customer.
Processing and suppliers
The app retrieves authorized Jira worklogs, reconciles durations, saves billing-period captures, compares changes and exports on customer instruction. Forge stores account and record identifiers, timestamps, durations, configurations, coverage metadata, pseudonymous action observations and administrator-notice acknowledgements. Tempo connections are disabled for launch.
Atlassian Pty Ltd provides Forge runtime, hosted storage and platform operations under the Forge DPA. Applicable downstream functions and locations are identified in Atlassian’s subprocessor register. Processing is not guaranteed to remain exclusively in the EEA. No provider Data Privacy Framework certification is claimed.
Approved supplier-notice term
New suppliers appointed directly by the provider retain the standard 30-day advance notice requirement. For Atlassian’s downstream Forge supplier changes, the provider forwards available details to the designated customer administrator promptly after receiving Atlassian’s notice. The provider does not promise 30 days’ advance notice for those downstream changes; Forge currently provides subscribed developers at least 14 days. The standard customer objection rights remain unchanged. Applicable Standard Contractual Clauses and mandatory obligations take precedence.
Return, deletion and notices
Authorized operators can export and delete their captures and configurations, including after reporting access becomes inactive. Privacy reporting erases affected stored records. Primary-storage deletion and Atlassian backup disposal are separate stages governed by the Forge hosted-storage lifecycle; deletion confirmations state the scope actually verified.
Customer-specific in-product notices are restricted to the affected site and current Jira administrators. Acknowledgement records show which authenticated administrator viewed a notice; they do not imply every administrator received it. The customer-specific agreement identifies the notification contact and method.