Privacy policy

Privacy Policy — OpenAPI Viewer & Macro Migrator for Confluence

Last updated: 17 October 2026 · Regulation (EU) 2016/679 (GDPR)

The short version

The app runs on Atlassian Forge and stores no personal data. It reads an OpenAPI specification from the place you configure in each macro and shows it in the page. The only thing it keeps is the access token or password you may enter for a private repository, stored by the app on Atlassian’s platform and sent only to the address it was saved for. We do not operate a server, a database or an analytics pipeline for this app, and nothing it handles is sent to us.

Who we are

Pieran Lab di Erik Pieran — sole trader, Italy

Via Bruno Mion 100, 30038 Spinea (VE), Italy

VAT / Tax code: IT04915430278 · REA: VE-463627

Email: support@pieranlab.cloud

What the app reads

The app does not read user profiles, e-mail addresses, comments, or any page other than the ones above.

What the app stores

One thing only, and only if you use it: credentials for a private repository — an access token, or a username and password — entered in the macro configuration.

When the migration page converts an old macro that had credentials in its parameters, those credentials are moved into this storage and removed from the page.

What leaves Atlassian, and why

Nothing is sent to us. When reading a specification fails, the app writes the host name and the HTTP status code to Atlassian’s app logs, which we can see as the developer — never the path, the query string, the credentials or the content.

What the app does not do

Where the data lives

In your Confluence site and in Atlassian’s Forge platform, under Atlassian’s own data residency arrangements. We do not choose or control that location, and we never hold a copy.

Your rights under the GDPR

The app stores no personal data. Repository credentials can be removed at any time from the macro configuration. If you need written confirmation for an audit, write to support@pieranlab.cloud.

Roles: for the content of your Confluence site you, the customer, are the controller. We do not act as a processor in the usual sense, because no data reaches us: the processing happens inside your own Atlassian tenancy, under Atlassian’s terms, and towards the addresses you configure.

See also

The security statement and the support page.

Changes

This policy is versioned with the app. The date at the top changes when the content does, and material changes are noted in the release notes.