Parent Pulse privacy notice

Effective date: 14 September 2026

This notice explains how Parent Pulse: Progress Rollups for Jira handles information. Parent Pulse is provided by Hendrik Bonthuys trading as Kitawolf Studios, a sole trader based in Scotland ("Kitawolf Studios", "we", "us").

Information the app processes

When a user opens or refreshes Parent Pulse, the app asks Jira for the current parent key and the user's visible direct children. For those children it processes:

• Work-item identifier and summary
• Work type
• Status and status category
• Original estimate
• Remaining estimate
• Time spent

The app uses this information only to calculate and display the rollup requested by the user.

Storage and data transfers

Parent Pulse does not operate an external application server or database. It does not persist Jira issue content, send customer data to third-party analytics, use issue data for advertising, or process issue data with AI or machine-learning services.

App execution and Jira API requests take place on Atlassian's Forge and Jira Cloud services. Parent Pulse declares no external data-egress domains.

The app code does not intentionally write issue content, user content, credentials, or access tokens to application logs. Atlassian may process platform and operational information under its own agreements and privacy documentation.

Permissions

Parent Pulse requests the Jira read:jira-work scope. Requests run in the signed-in user's context, so Jira browse permissions and issue security determine what the app can include. Restricted children are not exposed to unauthorised users.

Retention and deletion

Parent Pulse stores no app-owned customer dataset and therefore has no app-owned issue data to retain or delete when the app is uninstalled. Data retained by Atlassian is governed by the customer's Atlassian agreement and settings.

Support communications

If you contact support, we process the contact details and information you choose to provide so we can respond and investigate. Do not send passwords, API tokens, session cookies, or unnecessary confidential issue content. We keep support records while a request is open and afterwards only where needed to investigate a recurring issue, record support commitments, handle a complaint or security incident, establish or defend legal claims, or meet a legal obligation. Closed correspondence is reviewed against those purposes and deleted when it is no longer needed.

Our role and reasons for using personal information

Your organisation determines the purposes for which its Jira work-item data is collected and used. Parent Pulse processes the Jira data made available through the user’s request to provide the requested rollup; it does not build a separate customer database. Your organisation’s privacy information explains its lawful basis for Jira data.

Hendrik Bonthuys trading as Kitawolf Studios is the controller for personal information supplied directly in support correspondence. We rely on our legitimate interests in answering enquiries, providing and securing the app, and resolving problems. Where you personally are a party to our contract, necessary contractual support is also processed to perform that contract. We rely on legal obligations where we must retain or disclose information to comply with law.

You choose what to send to support. We may be unable to investigate a problem if necessary information is not provided. We do not use support correspondence for unsolicited marketing, sell it, or use it for automated decisions with legal or similarly significant effects.

Support providers and international processing

Our support mailbox uses Namecheap Private Email. Support messages and attachments are therefore processed by that email service separately from the Forge app. Namecheap describes US-hosted Private Email infrastructure and publishes cross-border processing terms in its Data Processing Addendum. You may contact us for information about the safeguards relevant to your correspondence. Do not send live credentials or unnecessary sensitive data.

Information may also be disclosed where necessary to obtain professional advice, establish or defend legal claims, respond lawfully to a public authority, or investigate a security incident with Atlassian. Disclosures are limited to what is needed for the relevant purpose. The app’s lack of external data egress does not mean that separately submitted support email stays within Atlassian or the UK.

Your choices and rights

Your Jira administrator controls installation and Jira access. Requests concerning Jira-hosted personal data should normally be directed to your organisation's Jira administrator. For information supplied directly to Kitawolf Studios through support, contact us using the address below. Depending on the circumstances, you can request access, correction, deletion, restriction or portability of your personal information, and object to processing based on legitimate interests. If processing relies on consent, you may withdraw it without affecting earlier lawful processing. Rights are subject to applicable conditions and exemptions.

You can complain to the Information Commissioner’s Office or another competent data-protection authority. We welcome the opportunity to address your concern first.

Changes

We may update this notice when the app, law, or Marketplace requirements change. We will publish the revised effective date and provide additional notice where required.

Contact

Email: support@kitawolfstudios.com

Hendrik Bonthuys trading as Kitawolf Studios
75 Fairfield Road
Inverness, Highlands IV3 5LJ
United Kingdom