Privacy Policy: OpenAPI Swagger Viewer for Confluence
Effective date: 18 October 2026
Vendor: Ashkan Ayyoogh, United Kingdom (postal address available on request), the United Kingdom ("we", "us")
Contact for privacy questions and security reports: support@capella.business
1. The short version
- The app shows OpenAPI/Swagger specs inside Confluence Cloud. It runs on Atlassian's Forge platform and is designed to Run on Atlassian: it makes no outbound network requests and declares no external permissions.
- Your specs, page content and attachments are read in your own browser from your own Confluence site. They are not sent to us, and not to anyone else.
- We do not store passwords, API tokens or any other credentials. We do not use analytics, advertising or tracking tools inside the app.
- The only app data we or the app keep is: the macro settings you enter, and small anonymous error counters, both held in Atlassian's Forge storage for your site.
- We receive the usual customer and licence information from Atlassian Marketplace (who bought what, for which site), and the emails you send us for support.
- We have no sub-processors. Atlassian hosts the app and its data.
2. Who is responsible for what
- Your content (specs, page text, attachments, macro settings): you are the controller of this data. Because it stays on Atlassian's infrastructure and never reaches our own systems, we do not hold a copy. To the limited extent that running the app processes it on your behalf, we act as your processor and will sign a data processing agreement on request (support@capella.business).
- Business and support data (Marketplace licence information, support emails): we are the controller.
- Atlassian operates Confluence, Forge hosting and storage, and Marketplace billing. Atlassian's own privacy policy and terms apply to that processing: https://www.atlassian.com/legal/privacy-policy
3. What data is involved, precisely
3.1 Data processed inside your Confluence site (the app itself)
| Data | What it is | Where it lives | Do we receive it? |
|---|---|---|---|
| Macro configuration | Source mode (paste or attachment), the pasted spec text if you chose paste, the selected attachment and version, display options | In the Confluence page's macro configuration, and where needed in Forge hosted storage for your site | No. It stays in Atlassian. |
| Attachment content | The .yaml/.yml/.json file attached to the page | Stored by Confluence as a normal attachment | No. The app reads it with the viewing user's own permissions through the Confluence API, in that user's browser, and renders it there. It is never transmitted to us or to any third party. |
| Anonymous error events | One log line per render with a fixed category (for example parse_error, download_error, ok) and a size bucket (for example "1–5 MB"). They contain no spec content, no file or page names, no user identifiers and no IP addresses | Atlassian Forge application logs (inside Atlassian’s infrastructure, subject to Atlassian’s retention) | Yes — we can read these category-only lines through Atlassian’s Forge developer tooling to measure error rates. Nothing else leaves your site. |
| Forge diagnostic logs | Technical error entries written by the app when something fails (error type, app version, time, installation identifier) | Atlassian's Forge logging; visible to us as the developer | Yes, but the app is written not to log spec content, tokens or personal data. We use them only to fix bugs. |
The only permission the app asks Atlassian for is read:attachment:confluence (read attachments of the pages a user can already see). It uses no Forge storage, does not write to your pages or attachments and requests no external domains.
3.2 Data we receive as the vendor
| Data | Source | Why | Legal basis (GDPR) |
|---|---|---|---|
| Licence and transaction information: site URL or identifier, app version, licence type and user tier, dates, and the technical and billing contact names, emails and company that you gave Atlassian | Atlassian Marketplace | To provide and support the app, keep licence records, handle tax and accounting | Contract; legal obligation |
| Support correspondence: your name, email, anything you write, and attachments you send | You, by email | To answer you and fix problems | Legitimate interests (running support); contract |
| Optional feedback or review responses | You | To improve the product | Legitimate interests |
We ask you never to send API tokens, passwords or confidential specs by email. If you need us to look at a spec, send a minimal anonymised example.
3.3 What we do not collect
- Passwords, API tokens, OAuth tokens or any credentials (your CI pipeline uses your own Confluence token against Atlassian directly; it never passes through the app or through us).
- The content of your pages, spreadsheets, specs or attachments.
- Analytics, usage tracking, fingerprinting, advertising identifiers or third-party tracking scripts. The app sets no cookies.
- Sensitive categories of personal data. Please do not put personal data into specs; they are meant to describe APIs.
4. How we use data
To run, secure, support and bill the app; to fix errors; to meet legal obligations; to communicate about outages, security issues and changes to these terms. We do not sell personal data, do not use it for advertising, and do not use it to train AI models.
5. Where data is stored and who can see it
- App data (3.1) is stored by Atlassian in Forge hosted storage and follows the data residency of your Confluence site. We do not move it elsewhere.
- Licence and support data (3.2) is held on our email provider and bookkeeping tool and may be accessed from the United Kingdom and other countries where our team works.
- Only people at Ashkan Ayyoogh who need it for support (currently one person, bound by confidentiality) can see licence and support data.
6. Sub-processors and third parties
- For the app and your content: none. All processing happens on Atlassian infrastructure (as host) and in your browser.
- For our own business records we use ordinary tools such as an email provider and an accounting or bookkeeping tool. They only ever see licence and support data, never your content: Google Workspace / Gmail (email, EU/US), Cloudflare (email routing and website delivery, EU/US), GitHub (website hosting, US).
- We disclose data to authorities only when legally required.
7. How long we keep data
| Data | Retention |
|---|---|
| Macro configuration | While the app is installed and the macro is on the page. The pasted spec in a macro is part of your page; removing the macro or page removes it. |
| Error counters | Rolling [90] days, then deleted |
| Forge diagnostic logs | As long as Atlassian keeps Forge logs (currently short-lived; see Atlassian documentation) |
| Licence and transaction records | As long as needed for tax and accounting law: 7 years |
| Support emails | [24] months after the last message, then deleted |
8. Uninstalling and deleting data
- If you uninstall the app, Atlassian soft-deletes the app's Forge storage for your site and permanently removes it after Atlassian's retention period. Atlassian's current documentation describes this period as 28 days after uninstall, with the possibility to relink data if you reinstall within 21 days. We cannot shorten or extend it.
- Macro settings that sit inside Confluence pages stay in those pages until you delete the macro or the page. They belong to your Confluence content.
- Attachments belong to your pages and are not removed by uninstalling the app.
- To delete licence or support data we hold about you, email support@capella.business. We will do it unless the law requires us to keep it (for example invoice records), and tell you which parts we kept and why.
9. Your rights (GDPR, UK GDPR and similar laws)
You can ask us to: access your personal data, correct it, delete it, restrict or object to processing, and receive it in a portable format. You can withdraw any consent at any time. Email support@capella.business; we respond within 30 days. You can also complain to your local data protection authority.
If you are a customer and your own users or data subjects contact us about content in your Confluence site, we will direct them to you, because you are the controller of that content and we do not hold it.
10. International transfers
We are based in the United Kingdom. Licence data reaches us from Atlassian, and support emails from you, possibly from outside our country. Where required, transfers rely on the UK International Data Transfer Agreement or Standard Contractual Clauses, or an adequacy decision. Atlassian's own transfers are described in its policies. Your app data does not leave the Atlassian infrastructure that hosts your site.
11. Security
- The app Runs on Atlassian: it holds no credentials, calls no external hosts and has no backend of ours that stores your data.
- We keep dependencies patched and scanned, log no sensitive data, and limit access to licence and support data to the people who need it.
- Please report vulnerabilities to support@capella.business (subject "SECURITY"). We acknowledge within one business day.
- If we learn of a personal data breach affecting our data, we notify affected customers without undue delay and authorities within 72 hours where the law requires it.
12. Children
The app is a developer tool for workplace use. It is not directed at children, and we do not knowingly collect their data.
13. California and other US states
We do not sell or share personal information as those terms are defined in US state privacy laws, and we do not use it for targeted advertising. You may exercise access and deletion rights via support@capella.business.
14. Changes
We will update this policy when the app's data handling changes (for example if we add a feature that stores new data) and change the effective date above. For material changes we will update the Marketplace listing's Privacy and Security tab and notify administrators by email where we have a contact.
15. Contact
Ashkan Ayyoogh · United Kingdom (postal address available on request) · support@capella.business