Last updated: 14 November 2026
Reperform is an app for Jira made by TrueSquare Labs. It tests whether a control worked over a period, using the records in your Jira site. This page says what the app reads, what it keeps, where that is kept and who can see it.
Reperform runs entirely on Atlassian's Forge platform, inside your Atlassian cloud. It has no server of its own and sends nothing to any address outside Atlassian.
TrueSquare Labs does not receive, see or store your records, your tests or anything about the people on your site.
The app keeps no person's name, email address or picture. Where a test refers to a person, the app keeps the Atlassian account ID and asks Jira for the current name each time it shows one.
There is no tracking, no analytics, no advertising, and the app sets no cookies.
The app reads your site only when someone uses it, and always as that person. It can read only what that person may see.
Jira records that a control's filter finds, with their fields, their change history, their web links and, for service desk requests, their approvals.
The names of your site's statuses, fields and record types, so that a control can be fitted to your site.
The members of a group, when a control tests that an approver belonged to it.
The display names of the accounts a test refers to, at the moment a page, an answer or a workpaper is shown.
Your site's address and name, to build links to records.
Once an administrator has limited who can use the app: which groups the person using it belongs to and whether that person administers Jira, asked each time and kept nowhere. The app does not ask this while it is open to everyone.
The names of your site's groups, when a Jira administrator chooses among them.
In Confluence: the list of spaces when someone chooses where to write a workpaper, and a workpaper page the app wrote before, when it writes a new version of it.
The app keeps what a test of a control consists of.
The control: its filter and what is tested on each record.
The population: the keys of the records that fell in the period, and how the search was run.
The sample, with the seed it was drawn from.
The register of samples: for every sample drawn, the account ID of the person who drew it, the time, the seed, and how many items were drawn from how many records.
For each sampled record, the result of each test and the evidence for it. Evidence is copied from the record as it stood when it was tested: its summary, an excerpt of a field, the title of a link, a change of status with its date, an approval with its date.
What people decide: a decision on a result with the note the person wrote, the conclusion, the two signatures and the history of the test. Each is kept with the account ID of the person and the time.
The controls your team adapted or wrote, and your site's address.
Who can use the app: the groups a Jira administrator chose, by their ID and name, and the latest 50 changes of that setting, each with the account ID of the administrator who made it and the time. The app keeps no list of the people who used it or were refused.
When a test is deleted after a sample was drawn for it, the register keeps one line of it: the sample as above, the account ID of the person who deleted the test, the time, the reason that person typed, and how many items had been tested with how many deviations. Everything else about the test is removed. The line is there so that a later test of the same control and period can say that an earlier sample existed.
Text copied from a record is your content. If a record's summary or description mentions a person, the copy does too. The same goes for what people type into the app: a note on a decision, a conclusion, a reason for deleting a test.
Everything is kept in Forge's hosted storage, which Atlassian provides for the app on your site. It is held in the same location as your Jira site and moves with it if your administrator moves the site.
A test stays until someone deletes it in the app. The line the register keeps of a deleted test and the changes of who can use the app stay until the app is uninstalled. Uninstalling the app removes everything the app kept. In both cases Atlassian holds a copy that the app can no longer read for a limited time, so that an accidental deletion can be undone, and then destroys it, as Atlassian's own retention policy describes.
The app identifies a person by Atlassian account ID. It keeps no names, email addresses, pictures, time zones or languages. Whatever else Jira says about a person is dropped before the app works with a record.
A name is read from Jira when it is shown and is kept nowhere. If a person changes their name, the app shows the new one. If a person's account is deleted, the app can no longer name them.
A workpaper written to Confluence is different. It is a page in your own Confluence, it states names as they were when it was written, and it stays under your control like any other page.
Automation rules and other apps that act on records are named as apps. They are not people.
As installed, everyone who can use Jira on your site can open Reperform and see every test on that site, with the evidence copied from the sampled records.
A Jira administrator can limit the app to Jira administrators and the members of chosen groups, on the page "Reperform access" in Jira's admin settings. The limit holds on every screen of the app, for its assistant, and for AI clients connected through Atlassian's MCP server. Jira administrators can always use the app, so the setting cannot lock a site out. The app's start page says who can use it, so everyone working in it knows who else sees the tests.
Inside the app there are no further divisions: whoever can use it sees every test. A person's own search still finds only the records that person may see. A workpaper written to Confluence is a page in a space, and Confluence decides who can read it.
Reperform includes an assistant for Rovo, Atlassian's AI. Rovo runs the assistant under your organisation's agreement with Atlassian. When someone asks it a question, Rovo calls the app's tools and receives what they answer, such as where a test stands or what was found in a sampled record. The app has no AI model of its own and sends nothing to any other AI service.
If your administrator lets other AI clients use the app's tools through Atlassian's MCP server, those clients receive what the tools answer, as the person using them.
When the app fails in a way it did not expect, it writes one line to Forge's app log, with the error and where in the code it happened. It does not log records, results or people. Atlassian lets the maker of an app read that log. Your administrator can turn this off for your site under Connected apps.
Nothing. None of it reaches us, so we cannot sell it, share it or use it.
Write to truesquarelabs@gmail.com.
Because none of your data reaches TrueSquare Labs, a request to see, correct or delete data is carried out on your own site. A test is deleted in the app, where the register keeps the one line described above, and everything the app kept is removed when your administrator uninstalls it. Atlassian's privacy policy covers the platform the app runs on.
If the app changes what it reads or keeps, this page changes first, and the date above with it.