Skip to content
claused

Data Processing Agreement

last updated 2026-09-03

This Data Processing Agreement (the “DPA”) is between Claused, an independent software vendor established in Georgia (the “Processor”, “we”, “us”), and the customer identified in the applicable marketplace order (the “Controller”, “you”). It forms part of the End User License Agreement and applies to personal data processed by our applications on your behalf. The terms below are the same for every app we publish; what differs from one app to the next — the categories of data it holds and how long it keeps them — is set out in a per-app annex at the end. Like the rest of our legal pages, it is written to be read.

The short version: our apps keep your data inside your own platform installation, we send it nowhere, and the only way we can see any of it is in the app’s own diagnostic logs on the platform. Section 4 says so plainly rather than burying it.

1. Roles

You are the controller of the personal data your platform instance contains. We are a processor, acting only on your instructions as expressed through your configuration of the app and its documented functionality. We do not determine the purposes of the processing, and we do not process your data for any purpose of our own — no profiling, no analytics, no training, no marketing.

2. What is processed

Purpose and duration. To provide the documented functionality of the app, for as long as the app is installed in your instance.

Data subjects. Users of your platform instance, and any other person whose personal data your users have entered into the free-text fields the app reads.

Categories of data. These depend on the app, so they are listed app by app in the annexes below — for the app you have installed, read its annex together with its security documentation, which states the same list against the code.

We store no passwords, no tokens, no account identifiers, and no user profile data in any app.

3. Where the data lives

The app runs on Atlassian’s Forge platform. Its stored copy lives in Forge storage inside your own Atlassian installation, in the region Atlassian hosts that installation in. The app declares no remote egress and no external servers: nothing is transmitted to infrastructure operated by us or on our behalf, and there is no telemetry.

4. Our access to your data

We do not access the contents of your instance in the ordinary course of providing the app, and we hold no copy of it anywhere.

There is one exception, and we would rather state it than let you discover it. The app writes diagnostic messages to the platform’s own logging facility, and some of those messages include a work item key — for example when a field is present on a work item but omitted from a search response. Those logs remain within Atlassian, are readable by us as the app’s developer for the purpose of diagnosing faults, and expire on the platform’s own schedule. They contain keys and technical detail, not work item summaries.

If you ask us to investigate a specific problem, we may ask you for information or a screenshot. That is your disclosure to make, not our access.

5. Sub-processors

We engage no sub-processors for app data.

The app executes on, and stores its data in, the Atlassian platform you already contract with directly. We do not interpose any provider of our own between you and it. Should that ever change, we will publish the sub-processor and its role on this page before it begins processing, and material changes are recorded in the app’s changelog.

Note that the processors listed in our Privacy Policy — for the website and its contact forms — are not involved in app data.

6. Security measures

  • Least privilege. The app requests read-only platform scopes and cannot modify your data. It asks for no personal access tokens, no passwords, and no shared secrets.
  • No egress. No remote endpoints are declared, so app data has no path out of the platform.
  • Permission fidelity. Totals are rendered per viewer, respecting your project permissions and issue-level security; a viewer sees no number they could not compute from work items they are entitled to see.
  • Platform controls. Authentication, tenancy isolation, encryption in transit and at rest, and infrastructure security are provided by the Forge platform.
  • Minimization by construction. The stored copy holds the fields listed in section 2 and nothing else.

We hold no third-party security certification today, and we do not claim one. Section 11 says what we can offer instead.

7. Assisting with data subject requests

Because the app’s stored copy is derived from your instance and lives inside it, the shortest route is almost always your own: correct or delete the work item in Jira and the app’s copy follows on its next synchronization. Uninstalling the app removes the stored copy entirely.

We will assist with any request you cannot satisfy that way, at no charge, within a reasonable period. We hold no independent index of your data to search on your behalf.

8. Retention and deletion

Every app prunes what it no longer needs rather than accumulating it, and downsamples any history it keeps so that older periods hold aggregates instead of detail. The schedule is a property of the app: you will find the figures in its annex below.

On uninstall, the platform deletes the app’s storage for your installation under Atlassian’s Forge data lifecycle. We retain nothing afterwards.

9. International transfers

We initiate no transfer of your app data. It remains in the Atlassian region hosting your installation, and we do not move it, copy it, or replicate it elsewhere.

10. Personal data breach

If we become aware of a personal data breach affecting your app data, we will notify you without undue delay through the contact on your marketplace order, with what we know, what we are doing, and what we recommend. Our channel for security matters, in both directions, is security@claused.io.

11. Audits and information

On reasonable written request, and no more than once a year unless a supervisory authority requires otherwise, we will answer questions about the processing described here and provide the app’s security documentation, its declared scopes, and its manifest.

We are a small vendor with no SOC 2 or ISO report to hand you. What we offer in its place is specificity: the security documentation states what the app reads and stores field by field, and it is written against the code.

12. Duration and changes

This DPA applies for as long as the app is installed in your instance and we process personal data on your behalf. We may update it prospectively; the current version is published at claused.io/legal/dpa with its revision date, and material changes are noted in the app’s changelog.

13. General

This DPA supplements the End User License Agreement; where the two conflict on the processing of personal data, this DPA prevails. It is governed by the laws of Georgia, and disputes shall be resolved by the competent courts of Georgia, unless mandatory law of your jurisdiction provides otherwise.

If your organization requires a signed agreement on your own template, use the contact form and say so.

Annex A — Hierarchy Totals for Jira

Security documentation. claused.io/apps/hierarchy-totals/docs/security/

Categories of data. The app’s stored copy holds:

  • work item keys and project keys;
  • parent links, work item type, and status category;
  • work item summaries — free text authored by your users, which may contain personal data if they put it there;
  • a flag recording that a work item carries an issue-level security level;
  • the values of the number-type custom fields and the time-tracking fields a gadget is configured to aggregate;
  • gadget scope registrations: the project list and the JQL filter text a filtered or multi-project gadget needs for its daily capture;
  • daily aggregate history — numbers only, no work item detail;
  • synchronization bookkeeping.

Retention schedule.

  • Per-work-item rows for a project nobody has viewed for 30 days are pruned automatically.
  • Aggregate history is downsampled: daily points for 90 days, weekly to two years, monthly thereafter. It never contains per-work-item data.

Diagnostic logs. As described in section 4, the platform’s logs carry work item keys from this app’s diagnostics. They do not carry summaries.