Privacy policy
Effective date: 27 August 2026
This policy explains what personal data is involved when you use the Confluence
app Custom HTML, CSS & JavaScript Macro (Atlassian Marketplace app key
ovh.kzar.custom-macro.confluence), and what we do and do not receive.
It covers the Forge version of the app only. It does not cover Confluence itself, the Atlassian Marketplace, or any other product.
1. Who we are
| Provider | Kamil Zarychta IT Consulting |
| Trading name on the Atlassian Marketplace | Atlas Cloudlet |
| Address | ul. Bluszczańska 34/12, PL-00-712 Warszawa, Poland |
| Responsible person for privacy matters | Kamil Zarychta |
| Contact for all privacy requests | [email protected] |
We are established in Poland, inside the European Union, so we act through the contact above rather than through an Article 27 representative. The same contact handles requests made under the UK GDPR and under California law.
2. Summary
The app runs entirely in your browser, on infrastructure operated by Atlassian. It has no server of ours, no database of ours, and no way to send your content anywhere.
| Question | Answer |
|---|---|
| Do we receive your macro content? | No. It never leaves Atlassian’s platform. |
| Do we receive Confluence page content, user names, or email addresses through the app? | No. |
| Do we run analytics, telemetry, or crash reporting in the app? | No. |
| Does the app set cookies or store data in your browser? | No. |
| Do we sell or share personal information? | No. We never have. |
| What do we actually receive? | Only what you send us in a support request, plus licence and installation records that Atlassian makes available to us as the app’s provider. |
3. How the app handles your data
The app stores exactly two values per macro:
| Value | Content |
|---|---|
source | The HTML, CSS, and JavaScript that a page author entered. |
maxHeight | A maximum display height in pixels. |
Both are saved by Atlassian as Confluence macro configuration, inside the body of your own Confluence page. They are transmitted to your browser by Atlassian when the page is viewed, and the app renders them there.
The app requests no Confluence API permissions, declares no external network permissions, uses no app storage service, and has no backend function. It does not read the identity of the person viewing or editing a page: anonymous and unlicensed viewers are supported precisely because no identity is needed.
Consequently we hold no copy of your macro content and no copy of your page content. We cannot read it, export it, restore it, or delete it, because we never receive it.
4. What we receive directly
4.1 Support correspondence
If you contact [email protected], we receive whatever you
choose to include: typically your name, email address, organisation, Confluence
site, and a description of the problem, along with any screenshots, macro source,
or log extracts you attach.
Our support address is an Atlassian Jira Service Management address, so support tickets are stored in Atlassian’s systems on our behalf.
- Purpose: answering your request and fixing the reported problem.
- Legal basis: performance of a contract, or our legitimate interest in supporting and improving the app (GDPR Article 6(1)(b) and 6(1)(f)).
- Retention: two years from the last message in the conversation, then deletion.
Please do not send us personal data you do not need us to see. A redacted reproduction is usually enough.
4.2 Licence and installation records
Atlassian makes licence, installation, and evaluation records for the app available to us as its Marketplace provider. These typically include the Confluence site, the licence tier and status, and the technical or billing contact that the customer supplied to Atlassian.
Atlassian holds these records and determines how long they are kept. We view them in Atlassian’s Marketplace partner tools to administer licences and provide support. We do not maintain a separate copy of them, load them into any system of ours, or use them for advertising or profiling.
5. Roles under data protection law
| Data | Your organisation | Atlassian | Us |
|---|---|---|---|
Macro source, maxHeight, and Confluence page content | Controller | Processor to you | Neither controller nor processor, with no access |
| Support correspondence you send us | Not applicable | Processor to us (Jira Service Management) | Controller |
| Licence and installation records | Not applicable | Controller of its own records | Recipient with access, for licensing and support |
Under California law the equivalent statements are: we are not a service provider or contractor for your macro or page content, because we never receive it; and we do not sell, share, or use for cross-context behavioural advertising any personal information at all.
Because the app gives us no access to your content, no data processing agreement with us is needed for it. The relevant processing agreement for content in your Confluence site is the one between your organisation and Atlassian.
6. Recipients and sub-processors
| Recipient | Role | What it involves |
|---|---|---|
| Atlassian (Atlassian Pty Ltd and affiliates) | Platform, Marketplace, and support-desk provider | Hosts Confluence and the Forge app, stores macro configuration as page content, holds licence records, and stores our support tickets |
We use no other processors for the app. There is no analytics provider, no error tracking provider, no advertising network, and no data broker in this app.
7. International transfers
We are established in Poland and handle support correspondence from within the European Economic Area.
Atlassian may process data outside the EEA and the United Kingdom under its own transfer mechanisms, including the European Commission’s standard contractual clauses. Those transfers are governed by your agreement with Atlassian and by Atlassian’s privacy policy, not by us.
8. Retention
| Data | Retention |
|---|---|
Macro source and maxHeight | For as long as the macro, the page, and the page’s history exist in your Confluence site. Governed by your own Confluence retention and trash settings. |
| Support correspondence | Two years from the last message. |
| Licence and installation records | Held and retained by Atlassian. |
| Anything the app holds in browser memory | Discarded when the page or editor is closed. |
Uninstalling the app stops it from rendering macros. It does not delete the stored macro configuration, because that is part of your page content and is held by Atlassian, not by us.
9. Cookies and browser storage
The app sets no cookies and writes nothing to localStorage, sessionStorage, or
any other browser store.
Confluence and the Forge platform set their own cookies to run the page and the app frame. Those are Atlassian’s, and Atlassian’s privacy policy and cookie notice describe them.
10. Your rights under the GDPR
For the personal data we control, which in practice is your support correspondence, you have the right to:
- request access to it, and a copy of it;
- have inaccurate data corrected;
- have it erased;
- have its processing restricted;
- object to processing based on our legitimate interests;
- receive it in a portable, machine-readable form.
We do not rely on consent for any of this processing, and we carry out no automated decision-making or profiling.
Write to [email protected] to exercise any of these rights.
We answer within one month, and will tell you if we need longer, as Article 12
permits. We may need to confirm who you are before acting, so that we do not
disclose one person’s data to another.
You may also complain to a supervisory authority. Ours is:
Prezes Urzędu Ochrony Danych Osobowych (President of the Personal Data Protection Office)
ul. Stawki 2, 00-193 Warszawa, Poland
uodo.gov.pl
You can instead complain to the authority where you live or work.
Requests about macro or page content
If your request concerns personal data that appears inside macro source or Confluence page content, we cannot act on it: we have no access to that content. Send the request to the organisation that operates the Confluence site, which is the controller for it. Their Confluence administrators can edit or delete the macro, the page, and its history.
11. Your rights in California
We honour the rights below for California residents, whether or not our processing meets the thresholds that make the CCPA and CPRA mandatory for a business.
Categories of personal information involved. Through the app itself: none. Through support requests: identifiers such as your name and email address, professional information such as your organisation and role, and the contents of your messages to us. We collect no sensitive personal information, no biometric information, no precise geolocation, and no information about anyone under 16.
Sources. You, when you contact us. Atlassian, for licence and installation records.
Purposes. Providing support, administering licences, and fixing defects. Nothing else.
Disclosure. We do not sell personal information. We do not share it for cross-context behavioural advertising. We have not done either in the preceding twelve months. The only disclosure is to Atlassian in its role as our support-desk and platform provider.
Your rights. You may request to know what we hold and how we use it, request a copy, request correction, and request deletion. You may not be discriminated against for exercising these rights. Rights to opt out of sale or sharing and to limit the use of sensitive personal information have nothing to opt out of here, because we do neither.
Send requests to [email protected]. An authorised agent may
act for you if they provide your written permission; we may still ask you to
confirm the request directly. We verify requests against the information already
in the relevant support conversation, and will ask for no more than we need.
12. Children
The app is a business tool for Confluence and is not directed at children. We do not knowingly collect personal data from anyone under 16.
13. Security, and one limitation you should understand
The app renders macro source inside a nested, sandboxed iframe with an opaque origin and a restrictive content security policy. Macro code cannot read the Confluence page, the Forge bridge, or the macro configuration, and cannot make network requests. Security and limitations describes this in full.
Two consequences matter for privacy, and they are the responsibility of the organisation that runs the Confluence site:
Macro source can contain personal data. Whatever a page author types into a macro becomes part of the Confluence page. Treat it exactly like any other page content, and do not put personal data, credentials, or private URLs there.
The sandbox is not an absolute barrier against a hostile macro author. The app blocks external requests, but a browser always permits a document to navigate itself. Macro JavaScript can therefore send the viewer’s browser to an external address of the author’s choosing, and anything the author placed in that address travels with the request. The app restores the original macro display afterwards, which limits the visible effect but does not prevent the request.
The control for this is Confluence page-edit permission. Only allow people you trust to create or edit macro source, and review macro code that came from an untrusted source before publishing it.
14. Changes to this policy
If we change how the app or our support process handles personal data, we update this page and change the effective date at the top. Material changes will also be noted in the app’s Marketplace release notes.
15. Contact
Kamil Zarychta IT Consulting
ul. Bluszczańska 34/12, PL-00-712 Warszawa, Poland[email protected]