Tech Adoption Radar for Confluence Privacy Policy

Effective 1 August 2026 (supersedes the version dated 21 July 2026)

Who we are

Tech Adoption Radar for Confluence is provided by Cloudscript Pty Ltd (ABN 14 700 662 362). If you have questions about this policy, contact us at support@cloudscript.io.

What data Tech Adoption Radar for Confluence collects

The macro processes the blip-list source you paste into it: technology names, ring and quadrant assignments, descriptions, movement status, and any same-site links you include. It also processes up to four optional quadrant-colour selections, chosen from a fixed set of Atlassian accent colours. Both of these are content you type or paste into the macro yourself, not data the app generates.

The macro also reads two further pieces of information at the moment they are needed, without storing either: your Confluence licence status (whether the app is licensed, on trial, or has an inactive licence), and the base URL of your Confluence site, which it uses only to resolve same-site links when you export the radar.

Where data is stored and processed

Tech Adoption Radar for Confluence operates no data store of its own. Its manifest declares no Forge storage:app usage, and none exists in the app's code. The blip-list source and any quadrant-colour selections you enter are saved through Confluence's own macro-configuration save path and held as part of your Confluence page's own content (its macro parameters), inside your own Confluence instance. This is the same storage and permission model as the rest of your Confluence page: anyone with view access to the page can see the rendered radar, and there is no separate access surface for it.

Your licence status and your site's base URL are read live from the Confluence/Forge runtime context at the moment they are needed and are not written to any store, by this app or otherwise.

Egress destinations and sub-processors

The app's manifest declares permissions.scopes: [] and no remotes or external.fetch block of any kind. The app makes no calls to any host outside Atlassian's own platform, and there is no third-party service, analytics tool or sub-processor that receives any of the data described above. This is confirmed both by the manifest itself and by a review of the app's source code, which contains no network call of any kind.

Retention

There is no app-defined retention period for the blip-list source or the quadrant-colour selections, because the app holds no copy of either outside your Confluence page. Their retention is governed entirely by your own Confluence page's ordinary version history and content lifecycle, in the same way as any other content on that page.

This is consistent with, not a deviation from, Cloudscript's standard retention and tombstoning default applied across its other apps (operational and audit records retained until app uninstall, with any stored personal-data identifier replaced by a non-identifying marker if the underlying Atlassian account closes). Here there is no record for that default to apply to in the first place, because the app creates none.

Data residency

Tech Adoption Radar for Confluence does not store End-User Data of its own, so there is no Cloudscript-operated location, region or residency setting for it to offer. The content you paste into the macro resides only inside your own Confluence page, within your own Confluence instance, and its residency follows whatever arrangement you already have with Atlassian for that instance. Cloudscript does not implement, support or vary any data-residency option for this app.

Uninstall, revocation and deletion

Because the app keeps no store of its own, uninstalling it triggers no app-initiated deletion process. The blip-list content and any quadrant-colour selections you have entered remain exactly where they already were: inside the macro body on your Confluence page, governed by Confluence's own page and version retention, until you remove or change that page content yourself.

Access, correction and complaints

Tech Adoption Radar for Confluence holds no data of its own, so in practice any personal data Cloudscript could hold in connection with this app is limited to support correspondence you send us directly. If you believe we hold personal data about you in that correspondence, or you wish to access or correct it, contact us at support@cloudscript.io and we will respond within a reasonable period. Complaints about how we handle personal data can be made to the same address; if you are not satisfied with our response, you may complain to the Office of the Australian Information Commissioner (oaic.gov.au), or to your local data protection authority if you are outside Australia.

Personal data that may incidentally appear within the blip-list content you paste into the macro (for example, a free-text description that names an individual) is held only inside your own Confluence page, under your own Confluence instance's access controls. Any request to access, correct, or delete that content, or any complaint about it, should be directed to the organisation that operates your Confluence site, since it controls that content and we hold no copy of it to act on directly.

Your rights

Cloudscript's role for this app has been assessed in a data-protection characterisation, and the recorded conclusion is that Cloudscript acts as a software supplier for Tech Adoption Radar for Confluence. It is neither a data controller nor a data processor under the GDPR, and neither a business nor a service provider under the CCPA/CPRA, for the blip-list content, because it operates no data store of its own, makes no network request to any host outside Atlassian, and never receives or holds a copy of the content you enter.

Because Cloudscript holds no copy of the content you paste into the macro, any request to access, correct, export, or delete that content (and any privacy right you wish to exercise over it) is directed to the organisation that operates your Confluence site, which controls that content within your own Confluence instance. Where that content includes personal data, that organisation is the controller able to act on your request, and if you are in the EEA or the United Kingdom your GDPR rights over it are exercised against that controller rather than against Cloudscript.

The only personal data Cloudscript itself may hold in connection with this app is any support correspondence you send us directly. You may ask us to access or correct that correspondence, or make a privacy complaint about it, using the contact details below and as set out under "Access, correction and complaints" above.

Contact

Cloudscript Pty Ltd (ABN 14 700 662 362)
Support: support@cloudscript.io