Tables, Charts & Reporting Workbench | HTF
Product privacy notice
Effective 31 October 2026. Updated 2 November 2026. Fred Jones trading as Howth Technology Factory, 3 Balglass Road, Howth, Dublin D13 R960, Ireland, provides this app. Contact support@howthtechnologyfactory.pro.
What the app processes
The app reads the selected Confluence page's metadata and the current user's permissions. It requests page body content when the user chooses to discover or import native page tables. The signed-in editor's account identifier is used for authorization. Separately, when a native table contains an Atlassian account mention, or an editor explicitly attributes imported content to a known Atlassian account, the app saves that subject's account identifier and observation time for privacy reporting.
Saved records include report datasets, formulas, notes, display settings, source page and report identifiers, source versions, timestamps, up to five report releases and known-account privacy provenance. Names, contact information or other personal data may occur in content users deliberately import. Customers decide which data to include and who may access the owning pages. The app does not infer account identifiers from names or email addresses, or assume that the editor is the person described by a report. Do not store passwords or authentication secrets in report cells.
Where processing happens
Imported local files are parsed in the browser. Saved reports and privacy tracking records use Atlassian Forge's Custom Entity Store. A scheduled privacy function sends known Atlassian account identifiers and their oldest retained observation times to Atlassian's Personal Data Reporting API. It does not send report cell contents to that API. The app has no external backend, external AI processor, app-authored analytics SDK or web trigger, and declares no external network destination. Its permissions are read:page:confluence, storage:app and report:personal-data. Privacy cleanup can continue after a subscription expires.
Unexpected errors log only bounded operation-stage and error-name, code or status metadata. The app excludes report content, page and account identifiers, request payloads, provider messages and stack traces from those diagnostic messages. Atlassian separately processes hosting and operational data under its own policies.
Atlassian provides the runtime, storage and platform operations. Forge scopes hosted storage by installation. See Atlassian's storage documentation for current encryption, location and retention details. HTF does not claim its own independent security certification or a Marketplace trust badge.
Access and copies
The backend checks the requesting user's access to the owning page on every operation and requires page update permission to change a report. It checks referenced source pages before returning source data. All report fields share page-level access. Exported files remain under the recipient's control and are not governed by later changes to Confluence page permissions.
The app does not read Jira issues, attachments or user directories. It does not automatically upload report data or chart images as page attachments. Native PDF and Word report-table output and the supported browser-download formats have passed content checks. Exported copies remain outside later app permission changes.
Retention and deletion
Saved records persist until a user deletes the report, automated privacy erasure applies, or a platform lifecycle event removes the installation data. The app keeps at most five releases and removes older app-managed snapshots when a new release exceeds that limit. Confirmed report deletion removes the current report and its retained app-managed releases.
If Atlassian reports that a known account is closed or that the app's copy of that account's data needs updating, the app permanently deletes each affected app-managed report, all its retained releases and tracked materialized copies. This deletes the whole report, including unrelated information mixed into it. There is no undo. The original Confluence pages and unrelated reports are preserved. A report that depends on an erased source becomes unavailable rather than returning that source's data. The app cannot recall files already downloaded or content already viewed in a browser.
Known-account provenance is retained conservatively through edits, saved releases, restores, source reuse and materialized transformations. Removing a cell or source reference does not remove its historical attribution. A later account update can therefore require deletion of a report even if the currently visible output no longer shows that person's information.
The app retains a small reporting and status record under a SHA-256 hash of the account identifier while the installation's app storage is retained. It records reporting times and, when applicable, the account's closed or updated status and an invalidation cutoff. It contains no raw account identifier, name, email address or report content. Its purpose is to prevent an old draft or retained copy from restoring erased data and to prevent reintroduction of a closed account's data. This marker can be linked to an account by someone who supplies its original identifier; it is not anonymous. Its retention follows the installation's Forge storage lifecycle, including Atlassian's applicable uninstall and backup retention. Deleting an individual report does not remove this protective marker. Data invalidated by an update may be imported again only from a genuinely newer observation; changing a timestamp alone is not a valid refresh.
Atlassian currently documents a 28-day retention period for Forge hosted data after uninstallation. Reinstallation does not automatically restore it. A customer-authorized recovery request must reach Atlassian through the developer within 21 days; recovery is not guaranteed. Platform backups and retention remain governed by Atlassian. Export needed data before uninstalling. See Forge's data lifecycle.
Privacy requests and support
Automated account-based reporting covers tracked content associated with a known Atlassian account identifier. The app cannot identify every person mentioned in arbitrary uploaded or pasted content. For content without a known account mapping, your organization must identify and delete affected reports and any separate copies through its own privacy-request process. Editing a current cell alone does not erase that information from retained releases. Original Confluence pages, downloaded files and other copies outside the app need to be handled separately.
For report data controlled by your organization, contact your Confluence administrator first. HTF handles product-support contact information and ordinary correspondence as an independent controller to answer requests and operate the business. Use fictional reproductions; do not send organization-controlled report data by email. Our support address forwards through Namecheap to the HTF Gmail inbox. Email is separate from the app's Forge data path. Do not send confidential datasets when reporting a defect; use redacted or fictional examples.
Contact support for access, correction or deletion assistance, or to report a privacy concern. Applicable legal rights are not limited by this notice. The website and fictional demo are separate from the installed app; see the website privacy notice. The customer terms and Data Processing Addendum describe the app's processing commitments.