Alidade

Privacy policy

For the Atlassian Marketplace app Swagger UI, OpenAPI Docs & API Catalog for Confluence, published by Alidade.

Last updated 2026-08-23.

The short version

The app runs entirely on Atlassian's infrastructure. We operate no servers, and your specifications never reach us. Everything the app stores is stored inside your own Atlassian site, by Atlassian, under Atlassian's data residency and security terms.

We collect no analytics and send no telemetry. There is no third-party service in this app: no tracker, no error reporter, no font or script loaded from somebody else's host — including on this website.

Who we are

Alidade is a trading name of INFOSERVICES SERVIÇOS DE INFORMÁTICA LTDA, a company registered in Brazil.

For the data the app handles inside your Confluence site, you are the controller and we are a processor. Atlassian is a sub-processor, and the only one.

What the app stores, and where

Everything below is stored by Atlassian, inside your Confluence site.

What Where Notes
The OpenAPI or Swagger specification you provide Forge key-value storage, split into chunks Atlassian-hosted app storage for your site
Endpoint index — operation names, paths, tags, counts A Confluence content property on the page This is what makes the endpoints searchable
Macro settings — a specification id, the API title and version, display settings, and what kind of source it came from The Confluence page body, as macro configuration Readable by anyone who can read the page
A URL you configured as a source Forge encrypted storage Kept out of the page because a URL can carry a token
A CI push token Forge storage, as a hash only The token itself is shown once and never stored

Macro configuration is page content. The specification id, the API title and version, and your display settings are written into the page like any other macro's settings, and anyone who can read the page can read them. That is why the source URL and the push token are deliberately kept out of it.

What we never store

What leaves Atlassian

Two features make outbound requests, and in both cases the request goes from the reader's or editor's browser to a host you chose — never through us, and never to us.

  1. "Try it out." When someone runs a request against your API from the rendered documentation, their browser calls your API directly, carrying whatever they typed into the form.
  2. Fetching a specification from a URL. When an editor saves a macro configured with a public URL, that editor's browser fetches it once.

This is why the app declares outbound network access, and why it deliberately does not carry the Runs on Atlassian badge. It is explained in full on the limitations page.

What we can see

Almost nothing, and it is worth being exact about the "almost".

As the app's publisher we can read Atlassian's application logs for the app. Those logs are written to contain identifiers and outcomes only — a specification id, whether a push was accepted, why a document failed to parse. They are written never to contain a document's contents, a request header, or a token. That is a design rule of the code, not a promise about the platform.

We cannot browse your app storage, read your pages, or retrieve a specification.

If you write to support and choose to attach a specification, we hold that email until the conversation is finished and our mailbox retention removes it. Please do not send credentials — see support.

Personal data inside a specification

An OpenAPI document is a technical description of an API. It usually contains no personal data, but it can — an example email address, a contact name, a server hostname.

Whatever you put in, the app stores and indexes as it is. It does not inspect, classify or extract personal data. If a specification must not contain something, remove it before uploading: hiding a tag or a path is a display filter and not access control, and the whole document remains retrievable by anyone who can read the page.

Retention and deletion

Removing a macro removes it from the page. Uninstalling the app ends its access to your site, and Atlassian deletes the app's storage for that site under its own retention schedule. We hold no copy anywhere else, so there is nothing for us to delete separately.

One thing to know, because it is a real behaviour rather than a promise: replacing a specification does not delete the old one. Copying a macro or a page copies the pointer, so two macros can share one stored specification, and deleting on replace would empty someone else's page. This costs storage, not correctness, and it is on the limitations page too.

To have something removed sooner, write to privacy@alidadeapps.com.

Your rights

Under the Brazilian LGPD, the GDPR and comparable laws, the people whose data you process have rights of access, correction, deletion, portability and objection. Because we are a processor and hold no copy of your data outside your Atlassian site, those requests are answered from your own site — you already have full access to everything the app stored.

Where you need us to act, write to privacy@alidadeapps.com and we will help.

For data Atlassian holds as your provider, see Atlassian's own privacy policy and Data Processing Addendum.

Sub-processors

Atlassian Corporation — hosting, storage and execution of the app, as part of your Confluence Cloud subscription.

That is the entire list. If it ever changes, this page changes first, and the change is announced on the status page.

Changes to this policy

The date at the top is the date it last changed. Material changes are announced on the status page and in the app's release notes on the Atlassian Marketplace.