Tables, Charts & Reporting Workbench | HTF
Effective 31 October 2026; service description updated 2 November 2026
These terms apply to Marketplace orders for Tables, Charts & Reporting Workbench | HTF. Product availability is shown on the product page.
The Marketplace customer agreement uses the Bonterms Standard End User Agreement, version 1.0, with the Provider-Specific Terms below. The standard agreement remains unmodified. Provider is Fred Jones trading as Howth Technology Factory, 3 Balglass Road, Howth, Dublin D13 R960, Ireland. Customer is the ordering party identified in the Marketplace order.
This attachment incorporates the Bonterms Data Protection Addendum, version 2.0, Attachment Version, including its Exhibits A and B, together with the following DPA Details. It takes effect when the customer enters the Marketplace agreement that expressly includes this attachment.
| Main agreement and effective date | The Marketplace customer agreement for this product, effective on the date the customer accepts that agreement. |
|---|---|
| Customer | The ordering party in the Marketplace order. Name, main address and privacy contact are supplied in the order or separately to support. Role: controller, or processor acting for its own controller where applicable. Activity: preparing and sharing business reports using Confluence. |
| Provider | Fred Jones trading as Howth Technology Factory, 3 Balglass Road, Howth, Dublin D13 R960, Ireland. Privacy contact: support@howthtechnologyfactory.pro. Role: processor. Activity: providing the reporting app and its support. |
| EU law and member state | Ireland for both, where the standard cross-border transfer clauses apply. |
| Purpose and operations | At the customer's instruction and as described in the product privacy notice: read selected page metadata and tables, check access, import and validate report data, calculate and display reports, store releases, retrieve, export and delete them. The app also records known Atlassian account subject provenance, reports account identifiers and their oldest retained observation times to Atlassian's Personal Data Reporting API, and applies the disclosed whole-report, retained-release and tracked materialized-copy erasure policy to returned account updates or closures. Report cell contents are not sent to that API. Business contact details and ordinary support correspondence handled by HTF as an independent controller are described separately in the privacy notice. Customers must not send report datasets or other organization-controlled personal data by email; use fictional reproductions. |
| Data subjects and categories | Customer users, personnel, customers and business contacts whose information the customer chooses to include. Data can include business identifiers, names, contact details and operational or financial report content. The invoking account identifier is used for authorization. Separately, actual known subject account identifiers from native-table mentions or explicit customer attribution are stored with observation times and report provenance. A minimal reporting/status/cutoff record is kept under a SHA-256 hash of the subject identifier as disclosed in the product privacy notice. That marker is linkable using the original identifier and is not anonymous. No special-category or criminal-offence data is required; customers should not submit it. |
| Frequency and duration | User-initiated report processing occurs when a user invokes the app; saved reports remain stored between uses. A scheduled Forge privacy worker periodically reports known account identifiers and oldest retained observation times to Atlassian and processes returned account updates or closures. No scheduled collection of Confluence page or table content is configured. Privacy cleanup can continue without an active paid licence during the applicable installation-storage lifecycle, as described in the product privacy notice. Processing continues for the subscription and applicable retention period. |
| Retention and deletion | Up to five report releases are retained. Confirmed deletion removes current and retained app-managed report records. Customers should export needed data before deletion or uninstallation. Forge currently retains hosted installation data for 28 days after uninstall; a new installation does not automatically restore it. Backup, recovery and residual retention follow Atlassian's documented lifecycle. No shorter erasure or automatic recovery guarantee is made. |
| Subprocessors and locations | Atlassian Pty Ltd (Australia) provides Forge hosting, storage and platform operations under the Forge Data Processing Addendum. Hosting and operational locations depend on the customer site and Atlassian services. Atlassian's onward processors and their locations are published in its subprocessor list. App report data is not routed through HTF's website, Namecheap forwarding or Gmail. Those email providers handle the separate controller-side support correspondence described in the privacy notice. No other app-data subprocessor is configured. |
| Security measures | Those stated in Provider-Specific Terms above and the product privacy notice. Atlassian handles platform transport and storage encryption and installation separation. The v4 service permissions are read:page:confluence for current-user page access, storage:app for app-owned records and report:personal-data for Atlassian privacy reporting. User report operations retain their page authorization and update-permission checks. Scheduled privacy processing is limited to installation-local app records under the disclosed policy. Inputs are bounded and report content is excluded from diagnostics. These measures do not assert that all platform data is confined to one jurisdiction. |
The incorporated standard agreement contains commercial warranties, remedies, liability limits, intellectual-property provisions and confidentiality obligations. The DPA contains data-protection assistance and audit obligations, notification of a relevant security incident within 48 hours of awareness, and at least 30 days' notice before a new subprocessor processes customer personal data.
The agreement takes effect on the customer's first Marketplace order, as provided in the standard agreement. Contact support@howthtechnologyfactory.pro about these terms.
Bonterms publishes the referenced standard documents. Attribution and licensing remain with their linked originals; the HTF processing details and Provider-Specific Terms are additions prepared for this product.