Myriastra Studio

Privacy and Security Policy — AccessRoll for Confluence (Space Access Review)

Version 1.2 · Effective 5 November 2026

This policy explains what data AccessRoll for Confluence (Space Access Review) (the "app", or AccessRoll) reads, writes, stores and logs, and how it is secured. The app is published on the Atlassian Marketplace by Myriastra Studio ("we", "us"), and is built on Atlassian Forge. The security disclosures are in section 8, Security. The data residency declaration is in section 6.

1. Where the app runs

The app runs entirely on Atlassian's Forge platform, and Atlassian's eligibility check reports the released version as meeting the technical requirements for Atlassian's Runs on Atlassian program (see section 8). We operate no servers, no database and no analytics infrastructure of our own for this app. The app's manifest requests no permission to contact any host outside Atlassian, the app makes no network requests to such a host, and we operate no system that receives your data. The app sends no email of its own: people learn about a review through Confluence mentions, which Confluence delivers according to each person's own notification settings — see section 3.

2. What the app reads from your Confluence site

When a review cycle is prepared, the app lists the spaces on your site that it can see, including personal and archived spaces, and decides which are in scope. Personal and archived spaces are left out by default, and a site admin can leave out other spaces with a reason. For each space in scope, the app reads its role assignments, the list of space roles, the space's permissions (to find its space admins), the name and members of each group that has a role in the space, and the profile of each person who has a role in the space directly. When a space admin uses Refresh current access, the app reads the same things again for that one space. These reads use the app's own identity, so they reach only what the app is allowed to read.

To decide who may open a screen, the app reads, as itself, the permissions of the space and the members of the groups that administer it. For the administration screen and for the referral recipient, it asks Confluence, on that person's behalf, which operations they may perform (section 8).

For its own work, the app reads: the space with the key MYRIASTRAAR and who created it, its own account id, a space by its key when a site admin leaves that space out, its own notification pages and the comments on them (so that it does not post the same comment twice), the access given to all licensed users in its own space, the restrictions and attachments of its export pages, and your site's base address (to build links). When an export is requested, it reads the requester's display name to print it on the workbook's cover. It does not read the content of pages in your other spaces.

3. What the app writes and sends

This app writes to your Confluence site in three ways: it creates its own space, AccessRoll (Myriastra) with the key MYRIASTRAAR; in that space it creates one notification page per review cycle and posts comments that mention the people asked to review; and for each export it creates a page there that only the requester and the app can read, with the workbook attached. It does not edit or delete content in your other spaces and changes no space permissions.

The app's space is created with only a name and a key; the app does not set that space's permissions (section 8). Each notification page is titled "Access review" followed by the cycle id, and its text is fixed wording that names the cycle and says that the page only collects review notifications and that the review is done in the app's screen. Only the app can edit it. Each comment mentions one person and carries one fixed sentence — a request to review, a reminder, a note that preparation of the cycle has stopped, or, for the referral recipient, the number of entries passed to them and of spaces that could not be read — and one link to the app's screen. Comments do not name spaces, list entries or name anyone other than the person mentioned. Confluence then notifies that person according to their own notification settings; the app sends no email of its own.

Each export page is titled with the period and the export id, and its text gives the attached file's name and its SHA-256 checksum. Its read restriction names the requester and the app, and only the app can edit it. The attached workbook (.xlsx) holds, for each review entry in the period: the cycle and its start date, the space, the person, group or access class with access and how they have it, the assignee, the answer with the account id of the person who answered and the time, the resulting outcome, when a missing answer was passed on, referrals with the recipient's account id, when they were opened and resolved and how many days they have been open, and the reason a space was left out or could not be read. A few columns are left empty by this version. A person is shown by display name, or by account id if no name was recorded. The cover gives the period, the scope and the requester's display name and account id.

4. What the app stores

The app stores data inside Atlassian (Forge storage). For each review cycle and space: the people, groups and access classes with access, with each person's account id, display name, account type and status and the route of their access; the space admins' account ids; group members' account ids and names; each answer (Keep or Not needed) with the account id of the person who answered and the time; and entries passed to the referral recipient, with that person's account id. It also keeps the settings (period, time zone, the referral recipient, excluded spaces, for all cycles or for one cycle, with the reason and who excluded them), the account id of the person who started the reviews, the account ids of people who asked for a retry or for Refresh current access, the latest list from Refresh current access, and for each export the requester's account id, the period and the page it created. It also keeps operational records: for each review notification, the account id of the person mentioned and whether it was sent; for each person who exports, their latest export request; and the status of its scheduled runs. Review records are deleted two years after their cycle closes; the most recent cycle is kept. Export pages, their attachments and the notification pages are not deleted by this. Uninstalling the app deletes the stored history. When Atlassian tells the app that a person has closed their account or changed their personal data, the app deletes that person's display name from the group member lists and review lists it keeps, and clears the latest list from Refresh current access if that person is in it; it keeps their account id, the answers and the rest of the record. In exports made after that, the person's review entries show their account id in place of the name. Names already in notification pages and in exported workbooks in Confluence are not changed. The app does not send data to any server outside Atlassian.

In more detail: for each group in a cycle, the app keeps the member list with each member's account id, display name, account type and status. For each space in a cycle, the app keeps its name and key and whether it was in scope. The list from Refresh current access holds the same fields as a review list and is replaced by the next refresh. For each export, the app keeps the number of rows, whether the data was whole, the file's SHA-256 checksum and size, and its progress. The app also keeps its own account id and the id of its space.

If preparing a space's list fails, its record keeps the error text as it was returned (up to 500 characters). The hourly run keeps its last error text (up to 200 characters), and a failed export keeps its error text (up to 200 characters). Such text can contain the id of a group, a space or a person (an account id). The app does not keep page content from your spaces, and it does not keep a copy of exported workbooks; those stay as attachments on the export pages in its space.

5. Logs

The app writes one line to Forge's application log each time one of its background steps runs — the hourly check and its worker, preparing a space's list, Refresh current access, an export, and the daily retention run — and a second line in its place if that step fails. Opening the app's screens or acting on them writes no line. Each line gives which step ran, the ids it worked on where the step has one (a cycle id such as c0001, a space id or an export id, and for the hourly and daily runs the name of the scheduled module), counts or a status, and timing. When a step fails, the line carries a short error code only. These lines do not carry account ids, display names, email addresses, group or space names, or page content. If a step fails, Forge may also keep its own record of the failure, which can include the error text and with it the id of a group, a space or a person. Forge logs are held on Atlassian's infrastructure and are retained according to Atlassian's platform policy; we read them only to diagnose faults, and we do not copy them anywhere else.

6. Data residency

Atlassian asks each app to define and publish what it treats as in scope and out of scope for data residency. This section is that declaration. It adds no new processing — it restates what sections 2 to 5 already describe.

In scope: everything the app writes to Forge hosted storage, as listed in section 4 — the account ids, names and group member records, the answers, settings and bookkeeping records. All of it is held exclusively in Forge hosted storage, which Atlassian operates. We operate no storage of our own, so where that data physically sits is determined by the Atlassian platform for the site the app is installed on, under Atlassian's data residency policy rather than under any arrangement of ours.

Read "exclusively" as: this app writes in-scope data to no store other than Forge hosted storage. It does not mean the values in section 5 appear nowhere else on Atlassian's infrastructure — see Platform logs below.

Out of scope:

Your Confluence data. The app's space, its notification pages and comments, and the export pages with their attached workbooks become part of your Confluence site. Confluence holds them under its own data residency, not this app. The notifications Confluence sends about mentions are Confluence's own.

Data read but not used beyond a step. Of what the app reads (section 2), only what section 4 lists is kept. The rest — such as space permissions, page restrictions, attachment lists, the text of comments on the app's own pages and your site's base address — is used while a step runs and discarded with it.

Messages between the app's own functions. These carry only ids (a cycle id, a space id or an export id), a time and a step counter, and are passed through Forge's event queue.

Platform logs. The lines described in section 5, and any record Forge keeps of a failed step, sit on Atlassian's logging infrastructure. Their location and retention are managed by Atlassian, not by this app, so we cannot offer a residency commitment over them. If your organisation needs a residency commitment that reaches platform logs, this app cannot give you one — please write to us before you buy rather than after.

7. Third parties

The app has no sub-processors. It shares data with no third party, and it contains no analytics, advertising or tracking code. It builds the export workbook with the open-source ExcelJS library, which runs inside the app on Forge and sends nothing anywhere. This page itself loads a web font from Google Fonts; the rest of the page is served by Cloudflare Pages.

8. Security

This section is the security policy for AccessRoll. Myriastra Studio is a one-person studio, and this app's security rests on how little the app is able to do, rather than on a formal security program. Most of what follows is a property of the app rather than a promise about us; the commitments we make are under Reporting a vulnerability.

Who is responsible for what. Atlassian provides the platform the app runs on: the infrastructure, tenant isolation, TLS in transit, encryption at rest for Forge storage, and the authentication of the people involved. We are responsible for the app itself: the permissions it asks for, what it does with them, what it writes to logs and storage, its dependencies, and fixing it when something is wrong. Nothing below asks you to treat Atlassian's own security attestations as ours.

The app has no server or endpoint of its own. There is no Myriastra Studio server, database, queue or endpoint anywhere in this app. It exists only as functions running on Atlassian's Forge platform, and its manifest requests no permission to contact any host outside Atlassian. This is why Atlassian's eligibility check reports the app as eligible for Atlassian's Runs on Atlassian program; that is a check on where data can go, not Atlassian vouching for the rest of our code. There is no web trigger and no URL of ours that anyone can call: the app's functions are run only by Atlassian, on a schedule and from the app's own screens inside Confluence, and each action on those screens checks who the person is and what they may do (below).

We do not receive your credentials. The app does not ask for, receive or store any API token, password or shared secret belonging to you or to anyone on your site. It authenticates to Confluence with the identities Atlassian issues to it: its own app identity, and, for the check described in section 2, access on behalf of the person using it.

The first time a site admin opens the AccessRoll administration screen, Atlassian may ask them to grant this app access on their behalf. The app uses that access only to check that the person is a site admin. Space admins are checked by the app itself. The access requested at installation includes changing space permissions; this version does not use it.

The permissions we ask for. The app requests sixteen scopes and no others: read:space:confluence, read:space.permission:confluence, read:group:confluence, read:user:confluence, read:content-details:confluence, read:page:confluence, write:space:confluence, write:page:confluence, read:comment:confluence, write:comment:confluence, read:content.restriction:confluence, write:content.restriction:confluence, write:space.permission:confluence, read:attachment:confluence, write:attachment:confluence and storage:app. These are declared in the app's manifest, which lists what the app is able to do. The write scopes are used for the writes in section 3: creating the app's space, creating and updating pages in it, posting comments, setting page restrictions and attaching workbooks. write:space.permission:confluence is the access to change space permissions named above; this version does not use it. Confluence grants these scopes more broadly than the app uses them: they would also let an app write to other spaces it can reach. This app writes only to its own space and its own pages, and it sends no request that deletes anything.

Encryption and storage. The app writes your data only to your Confluence site and to Forge storage hosted by Atlassian. Encryption at rest and TLS in transit are provided by the Atlassian platform, not by us. We add no encryption of our own, and we operate no storage of our own.

Who can reach what. Starting the reviews, the administration screen, its settings and leaving spaces out require a site admin, checked on that person's behalf as described above. A space's review list and its answers are open only to admins of that space, checked by the app from the space's permissions and the members of the groups that administer it. The Your spaces to review page shows a person only the spaces where they are recorded as a space admin. The person acting is taken from Confluence's own context for the request, not from anything the screen sends.

The review lists are read by the app itself, so a space admin sees each person and group with access to their space. Only admins of that space can open its list. The referral recipient, who must be a site admin, sees the entries passed on. Site admins can export records for all spaces, space admins for their own.

Export pages are created with a read restriction naming the requester and the app. Admins of the app's space can change page restrictions in Confluence, so they can change who reads an export page; the app does not prevent that. An export page stays readable by its requester even if they later stop being an admin. The app does not set the permissions of its own space: space admins see the notifications, and export pages can be opened, only if all licensed users can view that space, and anyone who can view it can read the notification pages and the names mentioned in them.

Our access is limited to publishing new versions of the app and reading Forge's application log (section 5), through the single Atlassian developer account that owns the app. We have no access to your Confluence site, and this version of the app gives us no way to read the data it stores on your installation.

How the app is built and released. The app's runtime dependencies are Atlassian's own Forge packages, React and ExcelJS; it bundles no analytics, advertising or tracking library. Each release is built from a version-controlled source tree, and before each deployment we run the project's automated checks (manifest validation, code lint and tests). This is our own practice, not a pipeline that blocks a release by itself. Updates are delivered by Atlassian, not by us. According to Atlassian's documentation, a version that asks for new permissions is held until one of your administrators approves the new scopes, so this app cannot quietly widen what it is allowed to read or write.

Reporting a vulnerability. Please write to contact@myriastrastudio.com with security in the subject line, describing what you found and how to reproduce it. If you believe an issue is being actively exploited, say so in the subject line so that it is triaged first. Please test only against a site you control, and please do not access or modify data that is not yours. Please do not put customer data, exported workbooks or any other confidential material in your report. That mailbox is an ordinary email account outside Atlassian — the property that data stays inside Atlassian belongs to the app at runtime, and it does not extend to an email you send us.

We will acknowledge your report and tell you what we intend to do about it. Confirmed vulnerabilities are fixed on the timeline set by Atlassian's Security Bug Fix Policy, which applies to us as a Marketplace partner. We do not run a bug bounty, do not run continuous scanning or scheduled penetration tests, and cannot offer payment. If we become aware of a security incident affecting this app, we will investigate it, report it to Atlassian as the Marketplace Security Enforcement Policy requires, work with Atlassian on containment and a fix, describe it on this page, and contact affected installations wherever we are able to identify them.

What we do not have. So that a procurement team can rule us in or out quickly: Myriastra Studio holds no third-party security report or attestation of any kind, has not completed a CAIQ Lite assessment, and offers no separate data processing agreement. If your organisation requires any of those, this app is not yet a fit — please write to us before you buy rather than after. AccessRoll records the answers your space admins give; it does not judge whether access is appropriate.

9. Retention and uninstalling

Review records become due for deletion two years after their cycle closes. A daily run of the app, which continues while the license is inactive, deletes them oldest cycle first, so the deletion happens on or after that date rather than at a set time. The most recent cycle, and the cycle in use, are kept however old they are, and so is a cycle whose closing time cannot be read. When a cycle's records are deleted, the app keeps a short marker for that cycle: its id, its dates and how many records were deleted, with no account ids or names. Export bookkeeping (section 4) is deleted two years after the request. Settings (except a space left out for one cycle only, which goes with that cycle's records), the record of who started the reviews, the latest list from Refresh current access and who asked for it, and the app's status records are not part of this deletion; they are replaced or cleared as they change and stay while the app is installed. There is no screen for deleting a cycle, an answer or a person's account id from the app's records sooner.

The app does not delete anything in Confluence. Its space, the notification pages and comments, and the export pages with their workbooks stay until someone deletes them in Confluence. Delete an export page, or change its restrictions, when it is no longer needed.

Uninstalling the app stops all further processing. According to Atlassian's Forge documentation, the app's Forge storage is then soft deleted and retained for 28 days, and what happens after that follows Atlassian's own data retention and disposal policy, not any action of ours. We cannot delete it sooner, so the data is not erased the instant you uninstall. Reinstalling the app starts a new installation; it is linked to the old data only if that is requested within 21 days of uninstalling. Export before uninstalling if you want to keep the records. The app's space, its pages, comments and attached workbooks stay on your site after you uninstall.

10. Turning it off

There is no setting that pauses the app. A site admin can leave a space out with a reason; a space left out is not read for the cycles prepared after that, until it is restored.

If the app's license is inactive, the screens and exports still work, but answers and settings are paused and no new cycle, reminder or referral is sent. The daily deletion of expired records (section 9) continues.

To stop everything, a Confluence administrator can uninstall the app (section 9).

11. Your rights and how to reach us

Because the app processes data only inside your own Atlassian site, requests about a specific person's data are usually best served by your Confluence administrator, who controls that site. The app has no screen for deleting one person's account id or name from its records — apart from the deletion of names described in section 4 — and we have no access to your site, so we cannot delete it for you. Review records are deleted two years after their cycle closes, with the exceptions listed in section 9, and after uninstalling, the whole of the app's storage is left to Atlassian's retention and disposal (section 9). A person's name can also appear in notification pages and exported workbooks in Confluence, which your administrators can delete there. If you would like to contact us about this policy or about a data request, write to contact@myriastrastudio.com. If you are reporting a security vulnerability, please read section 8 first — it tells you what to include and, more importantly, what not to.

12. Changes to this policy

If we change how the app handles data, we will update this page and the version and date at the top of it.