Security
Wikiwright runs entirely on Atlassian’s cloud, lists only pages each person can open, and changes a page only when Confluence confirms they may edit it.
Report a vulnerability
Email security@extoris.com with the steps to reproduce it. We confirm receipt within 4 business hours and keep you updated until it is fixed.
Please give us a reasonable time to fix the problem before you disclose it, and don’t access other customers’ data or disrupt their service while testing. We won’t take action against good-faith research that follows these rules.
We fix confirmed vulnerabilities within Atlassian’s deadlines for Marketplace apps, counted from the report: Critical (CVSS 9.0 or higher) within 10 days, High (7.0 to 8.9) within 4 weeks, Medium (4.0 to 6.9) within 12 weeks, Low within 25 weeks. We tell Atlassian within 48 hours of any security incident affecting customer data, and tell affected customers without undue delay and within 48 hours.
Where Wikiwright runs
- Runs on Atlassian. Wikiwright is built on Atlassian’s Forge platform. Its code runs in Atlassian’s cloud and its data is stored in Atlassian-hosted storage. It declares no outside servers and makes no requests outside Atlassian.
- Data residency. Wikiwright uses only Forge-hosted storage, which Atlassian keeps in your site’s data residency region and moves with it.
- Encryption. Data is encrypted in transit and at rest by Atlassian’s platform.
- No credentials. Wikiwright uses Forge’s built-in authentication. It never asks for, stores or uses passwords, API tokens or personal access tokens.
- AI. Optional AI suggestions use models hosted by Atlassian (Forge LLMs), so prompts stay inside Atlassian. See how Wikiwright uses AI.
Permissions
- Wikiwright reads pages as the app to build its link index, and shows that index only through each person’s own permissions: every list of pages is checked with Confluence, as the viewer, before it is shown.
- Before changing a page, it asks Confluence, as the person asking, whether they may edit it, and applies the site’s “who may fix links” setting.
- Archiving pages and trashing attachments are done as the person, so Confluence applies their permissions directly.
- Every change is saved as a page version naming who asked for it, listed under Changes, and can be undone.
- Admin screens check on the server that the person is a Confluence administrator.
- Rovo asks the person to confirm before any action that changes pages runs; the Wikiwright agent also shows its plan first.
What is stored
Wikiwright stores the structure of your links, not your page bodies: page and space IDs, titles, the links themselves (target, link text, section), headings, attachment names and sizes, settings, and the history of its own changes (the link before and after) for Undo. Page bodies are read to find links and are not stored. People are stored as Atlassian account IDs only, never names or email addresses. Details are in the privacy policy.
How we build it
- The OAuth scopes are the minimum the features need, and each is explained on the Marketplace listing.
- All database queries are parameterized. Logs hold IDs, counts and error codes, never page content or personal data.
- Every change to the code is reviewed and tested before release, including automated tests for the link-rewriting engine across every link form Confluence stores.
- Dependencies are kept current, and the app runs on a supported Node.js runtime.
- The app is tested on a 50,000-page site before release.
Our access to your data
We can’t browse your pages or Wikiwright’s data on your site. Forge isolates each installation, and the logs we can see contain IDs, counts and error codes. If you ask us to look into a problem, we work from what you send us.
Compliance
Wikiwright relies on Atlassian’s platform controls for hosting, storage and encryption; see Atlassian’s Trust Center. Extoris LLC doesn’t hold its own SOC 2 or ISO 27001 certification yet. Our data processing addendum covers customers’ GDPR and CCPA needs.