Effective date: 14 September 2026
This Privacy Policy explains how Ocupi Technologies (ABN 13 868 290 530), an Australian business ("Ocupi", "we", "us" or "our"), collects, uses, stores and discloses information in connection with Seal Docs, an app we distribute through the Atlassian Marketplace for use with Atlassian Confluence.
This policy is written for administrators and users of organisations ("Customers") that install Seal Docs into their own Atlassian Confluence instance. If you are an end user acting within a Customer's Confluence instance, please also refer to your organisation's own privacy policy, as your organisation controls how Seal Docs is configured and used.
1. Summary
Seal Docs is built on the Atlassian Forge platform and qualifies for Atlassian's "Runs on Atlassian" program. In practical terms this means:
- Seal Docs runs entirely on Atlassian's infrastructure, as part of your own Atlassian environment.
- There are no external servers operated by Ocupi that Seal Docs talks to.
- Seal Docs makes no outbound network calls to any third party. This is enforced by the Forge platform itself, which blocks network access an app has not declared. Seal Docs declares none.
- All data created or used by Seal Docs is stored using Forge app storage, hosted by Atlassian alongside your Confluence instance (see section 5 on data residency).
- Ocupi does not operate a database of Customer data and does not hold a separate copy of your Confluence content.
- Seal Docs writes diagnostic logs through the Forge platform, which Ocupi can read. They record account IDs and technical details such as page identifiers and outcomes (see section 7.1).
- Seal Docs does not use analytics, tracking pixels, advertising identifiers, or set cookies.
- Billing and licensing are handled entirely by Atlassian Marketplace; Ocupi never receives or stores your payment card or billing details.
2. What Seal Docs does
Seal Docs turns Confluence pages into controlled documents, in the style of an ISO 9001 document-control system. It provides a document register, an approval workflow, watermarked "controlled copy" PDF exports, a distribution log, and read-confirmation tracking.
3. Information we process
Because Seal Docs operates entirely within your Confluence instance, the "information we process" is, in substance, information your organisation already holds in Confluence, plus the records that Seal Docs creates as part of its document-control features. Specifically:
3.1 Document content
The content of the Confluence pages you choose to bring under document control is your organisation's own content. Seal Docs reads and renders it in order to produce controlled-copy PDFs and register entries; it does not copy that content anywhere outside your Confluence instance.
3.2 Personal data generated by Seal Docs
Seal Docs identifies people by their Atlassian account ID only. When it records that someone owns, approved, exported or read a document, it stores that person's account ID and the time, not their name or email address. Names are looked up from Confluence each time they are displayed (in the app, on exported PDFs and in exports) and are not stored by Seal Docs. If Confluence can no longer name an account, for example because the user has been deactivated, Seal Docs shows the account ID instead.
The records Seal Docs stores are:
- Document register entries: the Confluence page ID and space ID, the document ID and title (normally the page title), version and status, the document owner's account ID, and, if an approved page is edited, the editor's account ID;
- Approval and revision records: the account IDs of approvers and authors, their decisions, dates, and the text described below;
- the distribution log: who exported a controlled copy, when, and which version;
- read confirmations: who acknowledged reading a document, when, and which version; and
- administrative configuration: such as the approvers a space administrator nominates, PDF appearance settings (which can include an organisation name and watermark wording), and an organisation logo if one is uploaded.
Some of these records contain text that people type: comments an approver adds when approving or rejecting a document (a comment is required on rejection), and revision summaries. Seal Docs stores this text as it was entered. It can contain whatever the person chose to write, including names or other personal information, so it is worth treating like any other content your users put into Confluence.
Seal Docs also notifies people through Atlassian's own notification mechanisms. Currently that means Confluence comments that @mention the people involved (for example, asking an approver to review a document), which Confluence then surfaces to those users the same way as any other mention. These notifications contain user mentions and document details. Seal Docs operates no notification channel of its own outside your Atlassian environment, and never handles user email addresses. Any email involved is sent by Atlassian, not by Seal Docs.
We do not collect health information, financial account details, government identifiers, or other sensitive information as part of Seal Docs' own functionality. If such information appears in your Confluence content, it is your organisation's content and is handled as described in section 3.1 above, not as data collected by Ocupi.
4. Why we process this information
We (through the app running on your instance) process the above information in order to:
- maintain an auditable register of controlled documents and their status;
- operate the approval workflow you configure;
- produce watermarked controlled-copy PDF exports on request;
- record who has received or read a controlled document, to support compliance and audit requirements such as ISO 9001 document control; and
- let administrators and document owners see the history of a controlled document.
We do not use this information for advertising, analytics, profiling, or any purpose unrelated to providing the document-control functionality described above.
5. Where your data is stored
All data associated with Seal Docs is stored in Forge app storage, which is provided and hosted by Atlassian as part of your Confluence instance. Where your organisation has configured data residency for its Atlassian instance, Seal Docs' app storage follows that configuration. Ocupi does not choose, and cannot change, where your data is stored; that is governed by your own Atlassian settings and Atlassian's data-residency terms. No data is copied to infrastructure operated by Ocupi, because Ocupi does not operate any infrastructure that Seal Docs communicates with.
6. Who controls and processes this data
In data-protection terms, your organisation is the controller of the personal data processed through Seal Docs: you decide which Confluence pages to control, who approves them, and who your users are. Ocupi acts as a processor, providing the app that carries out those instructions automatically within your Confluence instance. Atlassian, in turn, is a sub-processor by virtue of hosting the Forge platform and app storage that Seal Docs runs on and stores data in.
In practice this means Ocupi does not decide what data is processed or why. Your organisation's configuration and use of Seal Docs determines that. Apart from reading the diagnostic logs described in section 7.1, Ocupi does not access, view, export, or otherwise handle your data as part of normal operation of the app.
7. Ocupi's access to your data
Ocupi personnel do not have access to the data Seal Docs stores in Forge app storage. We do not monitor, read, or export the contents of your document register, distribution log, or read confirmations. The one thing Ocupi can see is the diagnostic logs described below. If you contact us for support, we can otherwise only see the information you choose to share with us as part of that support request (for example, screenshots or descriptions you send us).
7.1 Diagnostic logs
Seal Docs writes structured diagnostic logs so that faults can be found and fixed. It writes them through the Forge platform's own logging, so they are held by Atlassian, and Ocupi can read them in Atlassian's Forge developer console. Atlassian makes these logs available for 30 days.
The logs contain pseudonymous Atlassian account IDs and operational metadata: page, space and document identifiers (and other Confluence identifiers, such as attachment and group IDs), which operation ran and whether it succeeded, HTTP status codes, counts and timings. They do not contain page content, page titles, approval comments, revision summaries, display names or email addresses.
A few further details are logged so that specific faults can be diagnosed: error messages when an operation fails, a short excerpt of the response when Confluence itself returns a server error, and, when an exported page contains characters that none of Seal Docs' fonts can display, a list of those characters. That list holds individual characters, never words or passages, but the characters do come from the page.
8. Retention and deletion
Seal Docs retains the document-control records described in section 3 for as long as the app remains installed on your Confluence instance, so that your document-control history remains available to you.
If you uninstall Seal Docs, data stored by the app in Forge app storage is removed in accordance with Atlassian's Forge platform policies for app data on uninstall. Because Ocupi does not keep a separate copy of this data outside your Atlassian instance, we have no copy to retain or delete once it is removed from Forge storage. If you have questions about the exact timing or mechanics of data removal on uninstall, please contact us using the details in section 12, or refer to Atlassian's own documentation on Forge app data handling.
Diagnostic logs (section 7.1) are held by Atlassian under its Forge platform policy, which makes them available for 30 days.
9. Cookies and tracking
Seal Docs does not set its own cookies, does not use analytics or tracking scripts, and does not use advertising identifiers. Any cookies or tracking associated with using Confluence itself are set by Atlassian, not by Seal Docs, and are covered by Atlassian's own privacy documentation.
10. Security
Seal Docs is designed so that data never leaves your Atlassian instance: it has no external servers to secure, no outbound network calls to make, and no separate database to protect. The Forge platform enforces this. An app cannot reach network destinations it has not declared, and Seal Docs declares none. Access to the data Seal Docs stores is governed by your own Confluence permissions and Atlassian's platform-level security controls for Forge apps and app storage.
We describe this architecture because we believe it materially reduces certain risks (such as data exfiltration to a third-party server), not as a guarantee that your data is free from all risk. No system is completely free of risk, and this policy should not be read as a promise that data is "completely safe" or invulnerable.
If a data breach involving personal data that Ocupi holds or can access (in practice, support correspondence and the diagnostic logs; see section 7) is likely to result in serious harm, we will assess and notify it in accordance with the Notifiable Data Breaches scheme under the Privacy Act 1988 (Cth). Breaches affecting data Seal Docs stores in Forge app storage are handled by your organisation and Atlassian under Atlassian's own security and incident processes, since Ocupi neither holds nor can access that data.
11. Your rights
11.1 Australian Privacy Act 1988
Ocupi is an Australian business and aims to handle personal data in line with the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth). Where Ocupi acts as a processor on behalf of a Customer who controls the relevant personal data, requests to access, correct, or delete that personal data should generally be directed to your own organisation (the controller) in the first instance, as it configures and administers Seal Docs and Confluence access. Where Ocupi holds information directly about you (for example, because you contacted us for support), you may contact us using the details in section 12 to request access to, or correction of, that information.
11.2 GDPR and UK GDPR
If you are located in the European Economic Area or the United Kingdom, the EU General Data Protection Regulation ("GDPR") or UK GDPR may also apply to certain processing of your personal data. In broad terms:
- Where Ocupi processes personal data on behalf of a Customer, the lawful basis for that processing is the performance of Ocupi's contract with the Customer (as a processor), and it is the Customer, as controller, that determines and is responsible for the lawful basis for its own processing of end users' personal data.
- Data subjects have rights including access, rectification, erasure, restriction of processing, data portability, and objection, in relation to their personal data, subject to applicable exceptions. Requests should generally be directed to the relevant Customer (controller) in the first instance, or to Ocupi using the details in section 12 if it concerns information Ocupi holds directly.
- Because Seal Docs stores data in Forge app storage that follows the data residency of your own Atlassian instance, international transfer of personal data (if any) is governed by the region you have configured for your Atlassian instance and by Atlassian's own data processing and transfer terms, rather than by any transfer to infrastructure operated by Ocupi.
This section is a high-level summary and is not a substitute for your own organisation's legal assessment of its obligations under GDPR, UK GDPR, or other applicable data protection law.
12. Contact us
If you have questions about this Privacy Policy, wish to make a privacy complaint, or have questions about how Seal Docs handles data, you can contact us at hello@ocupi.com.au. We will respond to complaints within a reasonable period. If you are not satisfied with our response, you may complain to the Office of the Australian Information Commissioner (oaic.gov.au).
13. Changes to this policy
We may update this Privacy Policy from time to time, for example to reflect changes to Seal Docs, to Atlassian's platform, or to applicable law. We will update the effective date at the top of this page when we do. If changes are material, we will take reasonable steps to bring them to the attention of Customers, such as by posting a notice on this page or on our website.
Ocupi Technologies