Privacy policy
Effective date: October 4, 2026
1. Who we are
PageAck: Page Acknowledgements for Confluence (the "app") is provided by Colorado Home Protection LLC, doing business as Aspyn, Boulder, Colorado, USA ("we"). Contact: support@pageack.com. Inside Confluence the app is titled "Page Acknowledgements".
The app runs entirely on Atlassian's Forge platform, inside your Confluence Cloud site. This policy explains what the app stores, where, and who can reach it.
2. The short version
- The app stores acknowledgement records in Atlassian's own app storage for your site.
- It stores Atlassian account IDs. It does not store names, email addresses or page content.
- It sends no data to us or to any third party. It reports the account IDs it holds to Atlassian, which issued them.
- We cannot access your records.
- Records are kept while the app is installed. After an uninstall, Atlassian deletes them.
3. Data the app stores
For each Confluence site where it is installed, the app stores the following in that site's own database.
| Data | Examples | Purpose |
|---|---|---|
| Atlassian account IDs | People in an audience, the person who acknowledged, the person who created, changed or closed a requirement, the person who changed app settings | To know who is asked and who has acknowledged |
| Page and space identifiers | Page ID, space ID | To link a requirement to its page |
| Page titles | The current title, and the title at the time of each acknowledgement | To label reports and records |
| Page version numbers | The version each person acknowledged, the version currently required | To show which text a record refers to |
| Timestamps | When someone was added, acknowledged, or a setting changed | To build the record and work out due dates |
| Requirement settings | Whether a page update asks for a new acknowledgement, the schedule, the due period | To apply your rules |
| Group IDs and group names | The Confluence groups you chose as an audience, with their names at the time | To refresh the audience from group membership |
| Custom message | The optional text you write for readers, up to 500 characters | To show it in the banner |
| Acknowledgement statement | The words "I have read and understood this page." | Stored with each record as the text the person agreed to |
| Audit events | Requirement created, changed or closed; audience updated; new page version detected; acknowledged; export generated; app settings changed | An unchangeable history of what happened |
| App settings | Who may create requirements, and defaults for new requirements | To apply your site's choices |
The app also sets one hidden property on each page that has a requirement. It holds the requirement's internal ID and whether it is active. It contains no personal data and is stored by Confluence with the page.
Account IDs are identifiers that Atlassian assigns to user accounts. Together with Confluence they identify a person, so we treat them as personal data.
4. Data the app does not store
- Names, email addresses, profile pictures or any other profile detail.
- Page content, comments or attachments.
- Passwords, API tokens or payment details.
- IP addresses, device details or cookies of its own.
Names shown on screen are displayed by Confluence from the account ID at that moment. When a manager creates an export, the app asks Confluence for names and email addresses, puts them in the file, and does not keep them.
5. Where the data is stored
All app data is stored in Atlassian Forge hosted storage, in a separate database for each installation. According to Atlassian's documentation, this storage is hosted in the location your administrator has chosen for your Confluence site. At the time of writing Atlassian lists these locations: Australia, Canada, the EU, Germany, India, Japan, Singapore, South Korea, Switzerland, the United Kingdom and the USA. If no location has been chosen, Atlassian decides where the data is hosted and may move it.
We operate no servers, databases or other systems that hold your data.
6. Who can access the data
- Your users. People who can manage a requirement can see its records and export them. By default that is anyone who can edit the page, plus Confluence administrators. Your administrators can restrict it to administrators only. Readers see only their own status. The app checks permissions with Confluence each time, as the person using it.
- Atlassian. Atlassian hosts the app and its storage under its own terms and privacy policy.
- Us. We cannot access your records. The app has no connection to any system of ours. We receive only the following, all through Atlassian:
- Anonymous counters. The app counts events such as "a requirement was created" or "an export was generated". Atlassian adds these up across all installations. They contain no account IDs, no page details, no site names and no other identifiers, and cannot be traced to a site or a person.
- Technical logs. When something fails, the app logs the name of the operation and the technical error. Logs are designed to contain no names, account IDs, page titles or request content.
7. Sharing and transfers
- The app sends no data to us and no data to any third party. It declares no access to any external service.
- The app reports the account IDs it holds to Atlassian, as Atlassian requires of apps that store personal data. Atlassian issued those IDs. This lets Atlassian tell the app when an account has been closed (section 11).
- We do not sell data. We do not use it for advertising or profiling.
- Exports are created only when one of your users asks for one, and go only to that user's browser. What happens to an exported file afterwards is under your control.
8. Information we receive from Atlassian as a vendor
Atlassian provides Marketplace vendors with information about installations, licences and transactions, such as the site name, the customer name, the licence type and the user tier. We use this to run the business: to understand sales, to meet our obligations to Atlassian, and to answer support requests. Atlassian handles all billing and payment. We never receive payment card details.
If you write to us for support, we receive what you send: your email address and the content of your message. We use it to answer you. Please do not send exports, lists of people, or screenshots that contain personal data. We do not need them and will not use them.
9. Retention and deletion
- Records are kept for as long as the app is installed.
- Acknowledgement records and audit events cannot be edited or deleted in the app, by your users, your administrators or us. This is deliberate: the records are meant to serve as evidence.
- Closing a requirement stops the app from asking people. Its records are kept.
- Removing a person from an audience stops the app from asking them. Their earlier acknowledgements are kept.
- If the app is uninstalled, Atlassian marks its stored data as deleted and removes it at the end of Atlassian's own retention period. Atlassian's documentation says the data can be linked to a new installation if that is requested within 21 days of the uninstall. Export anything you need to keep before uninstalling.
- We hold no copies or backups. We cannot restore deleted data.
- Support emails are kept for 24 months after the last message in a conversation and then deleted.
10. Your responsibilities as a customer
Your organisation decides which pages need acknowledgement, who is asked, and who may see the records. You are responsible for:
- having a lawful basis to ask your users for acknowledgements and to keep the records, and telling your users about it as your own policies require,
- deciding who may create requirements and view records, through the app's settings and your Confluence permissions,
- handling exported files, which leave Atlassian's storage when a user downloads them,
- exporting records you must keep before uninstalling the app,
- answering requests from your users about their data.
11. Individuals' rights
If you are asked to acknowledge pages by your organisation, please contact your organisation about your data. It decides how the app is used, and it can view and export your records. We cannot see them.
Limits you should know about: the app cannot delete or change the records of one person. Records for a site are deleted together when the app is uninstalled and Atlassian's retention period ends.
Closed accounts: the app reports the account IDs it holds to Atlassian, as Atlassian requires of apps that store personal data. When Atlassian tells the app that an account has been closed, the app stops asking that account for acknowledgements. Past acknowledgement records and history entries keep the account ID, which Confluence then shows as a former user. The app holds no name and no email address for any account.
For data we hold ourselves, which is limited to support correspondence and the vendor information in section 8, write to support@pageack.com.
12. Security
- The app runs on Atlassian's platform with a separate database for each site.
- Every action is checked against Confluence permissions as the signed-in user.
- The app asks for the minimum set of permissions it needs, listed in its documentation.
- Records are append-only.
No system is perfectly secure. If you believe you have found a security problem, write to support@pageack.com.
13. Changes to this policy
We will update this page when the app or our practices change, and change the effective date above.
14. Contact
Colorado Home Protection LLC, doing business as Aspyn
Boulder, Colorado, USA
support@pageack.com