Data processing addendum
This addendum applies when Wikiwright processes personal data for a customer. It forms part of the terms under which the customer uses Wikiwright, and needs no signature.
1. Parties and roles
The customer that installed Wikiwright (“Customer”) is the controller, or a processor acting for its own controllers. Extoris LLC (“we”) is the Customer’s processor (and its service provider under the California Consumer Privacy Act). Atlassian, which hosts Wikiwright, is our sub-processor.
2. Processing details
| Subject matter | Providing Wikiwright: indexing the links between Confluence pages, reporting problems, and making changes people ask for. |
|---|---|
| Duration | While Wikiwright is installed, then until the data is deleted as described in section 8. |
| Nature and purpose | Reading Confluence content to find links; storing link structure; showing it to authorized users; editing pages at users’ request; optional AI suggestions using Atlassian-hosted models. |
| Data subjects | People with accounts on the Customer’s Confluence site. |
| Personal data | Atlassian account IDs (of page owners and authors, people who ask for or undo changes, who triage links or are assigned them, and who report links); notes written in triage or reader reports; page titles, link text and headings where they contain personal data. |
| Special categories | None intended. Wikiwright doesn’t store page bodies. |
3. Our obligations
- We process personal data only on the Customer’s documented instructions, which are these terms and the Customer’s use and configuration of Wikiwright, unless the law requires otherwise; we will tell the Customer if we think an instruction breaks the law.
- People authorized to process the data are bound by confidentiality.
- We apply the security measures in Annex 1.
- We help the Customer respond to requests from data subjects, mainly through Wikiwright’s design (account IDs only, erased when Atlassian reports an account as closed), and otherwise on request.
- We help the Customer with security, breach notification, data protection impact assessments and consultations with authorities, taking into account the nature of the processing.
- We don’t sell or share the personal data, keep or use it for any other purpose, or combine it with other data, except as the CCPA allows a service provider to.
4. Sub-processors
The Customer authorizes the sub-processors listed in Annex 2. We will give at least 30 days’ notice of a new sub-processor on this page and by email to the Customer’s technical contact on the Marketplace licence; the Customer may object on reasonable data protection grounds, and if we can’t address the objection, may stop using Wikiwright, and we will arrange a pro-rated refund of prepaid fees for the remaining term through Atlassian. We bind each sub-processor to data protection terms at least as protective as these, and remain responsible for them.
5. Personal data breaches
We will notify the Customer without undue delay, and within 48 hours, after becoming aware of a personal data breach affecting the Customer’s data, with the information the Customer needs to meet its own obligations, and keep it informed as we learn more.
6. International transfers
Wikiwright stores and processes the Customer’s data on Atlassian’s Forge platform, in the Customer’s data residency region. We don’t transfer it elsewhere. Where Atlassian transfers data, Atlassian’s own transfer safeguards apply. If a transfer by us ever requires them, the European Commission’s Standard Contractual Clauses (Module 2 or 3) and the UK addendum are incorporated by reference.
7. Audits
We will make available the information reasonably needed to show compliance with this addendum, including answers to security questionnaires, once a year or after a breach. Hosting controls are covered by Atlassian’s audit reports, available from Atlassian’s Trust Center.
8. Deletion
When the Customer uninstalls Wikiwright, Atlassian keeps the app’s data for 21 days so a reinstall can resume, then deletes it. An Atlassian account’s ID is erased from Wikiwright’s records within a week of Atlassian reporting the account as closed; free-text notes stay until deleted with the app’s data. We keep no copies outside Atlassian’s platform.
9. Order of precedence
If this addendum conflicts with the other terms for Wikiwright on data protection, this addendum applies.
Annex 1: Security measures
- Hosting, storage, encryption in transit and at rest, backups and physical security by Atlassian’s Forge platform, with each installation’s data kept separate.
- No processing or storage outside Atlassian; no outside network access declared by the app.
- Every list checked against the viewer’s Confluence permissions; every change checked against the requester’s edit permission and the site’s settings; administrator checks on the server.
- Data minimization: account IDs instead of names or emails; page bodies not stored; logs limited to IDs, counts and error codes.
- Parameterized database queries; least-privilege OAuth scopes; no stored credentials.
- Code review and automated tests for every change; dependencies kept current; vulnerabilities fixed within Atlassian’s Marketplace deadlines (see Security).
- Every change to a page is saved as a page version naming who asked for it; link fixes can be undone from Changes.
Annex 2: Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Atlassian (Atlassian US, Inc. and its affiliates) | Hosting the app, its storage and logs (Forge); AI models when AI suggestions are on (Forge LLMs) | Atlassian’s cloud: app data in the Customer’s data residency region; AI requests where Atlassian runs Forge LLMs |
| Google Workspace (Google LLC) | Support email, only for what the Customer chooses to send us (for example screenshots) | United States |
Contact
Extoris LLC, Florida, United States. Email privacy@extoris.com.