Skip to content

FAQ

Nothing, until you ask. Installing grants no scan, reads no page, and changes no pages. It does tell our servers that the app was installed, with your site’s address and installation id, so we can set you up. Your first scan starts when you start one from the Scans tab.

Yes. A Confluence admin connects a Notion workspace from WikiFix Admin → Sources, and shares the pages WikiFix may read. One scan can cover Confluence spaces and Notion pages together, and finds where a Confluence page and a Notion page disagree. Fixes apply and revert on Notion pages too. The check for pages whose owner has left runs on Confluence only. See Confluence and Notion.

Not yet. Today you start by installing WikiFix in Confluence Cloud from the Atlassian Marketplace, then connect Notion from there.

Can WikiFix change my pages without approval?

Section titled “Can WikiFix change my pages without approval?”

No. Scans are read-only. A page changes only when someone with write access picks an answer and clicks Apply — and that edit is made as the approving user, and reverts in one click. In Confluence it shows in page history; in Notion it goes through that person’s own Notion sign-in.

In Confluence: read access to spaces and pages (to scan), write access to pages (used when you apply a fix — rewriting content, updating the owner on a departed-owner finding, or replacing a merged-away duplicate’s content with a pointer to the page you kept), read access to page metadata, comment read/write access (used when you ask a page owner to decide — that posts a regular Confluence comment — and to delete that comment if you undo asking), read access to user and group info (to know who owns a page and who has left), and read access to content details (to recognize which users are Confluence admins — WikiFix’s permission settings treat site admins as implicitly authorized). Read access to your email address resolves the address of whoever started the scan, for the scan-completion email at send time — the address itself is never stored. A small app-storage scope lets the WikiFix agent in Atlassian’s Rovo keep one pending summary per person in Atlassian’s Forge storage, until that person settles the finding it belongs to. Two further Forge platform scopes, read:app-system-token and read:app-user-token, let the app’s backend authenticate its own calls — they grant no additional access to your content. The Forge manifest is public on the Marketplace listing, so you can verify the scope list rather than take our word for it. In Notion, WikiFix asks to read content, update content, insert comments, and read user information without email addresses — and reads only the pages you share with it (details).

  • Your content is stored in AWS Frankfurt (eu-central-1). WikiFix keeps a derived index and the text behind findings, not a full copy of your wiki.
  • With EU residency required (Residency tab in WikiFix Admin), every AI step runs in the EU. Two analysis checks run on different AI models, which reside in the EU: eu/jev, operated by Bevelites GmbH on its own server in Germany. Every other AI step stays on AWS Bedrock in the EU. eu/jev receives the same excerpts TypeSafe would (below), and doesn’t store them or use them to train AI models. See Data residency.
  • Without it, the AI analysis runs on AWS Bedrock in the EU, apart from two checks that run on TypeSafe in the US. Each request to TypeSafe carries excerpts of the pages being checked: a passage with its page’s title and headings and up to 2,500 characters of its section (on a short page, that can be the whole page). Never a whole space. TypeSafe runs with zero data retention, so it doesn’t keep what it receives or use it for anything else, including training AI models.
  • With your own Anthropic API key (paid Advanced plan only, not during Atlassian’s 30-day evaluation), every AI step except indexing goes to Anthropic’s API under your account instead. See Editions & plans.
  • With the WikiFix agent in Rovo, Atlassian’s Rovo AI sees the findings, passages and pages the agent works with, under your Atlassian agreement.

Your content is never used to train AI models. Details: Security & data and the security page.

By default, the reading and the rewriting run on EU-hosted models on AWS Bedrock. The same pages usually give the same findings. Per AWS Bedrock’s contractual terms, no model provider has access to your prompts or completions.

With EU residency required, two analysis checks run on eu/jev, operated by Bevelites GmbH in Germany, which doesn’t store the excerpts it receives or use them to train AI models. Without it, those two checks run on TypeSafe in the US, which sees excerpts of the pages it checks and doesn’t keep them or use them for anything else, including training AI models. See Data residency.

On a paid Advanced plan you can bring your own Anthropic API key, and the analysis and rewrites all run on Claude instead, under your own account and your own agreement with Anthropic. Standard installs, and tenants still inside Atlassian’s 30-day evaluation, use the default EU Bedrock route. See Editions & plans and Credits & capacity.

Three today: pages that contradict each other, duplicate and near-duplicate content, and pages whose owner has left your site. What a health check covers — and what it doesn’t yet has the full list.

How is this different from archiving and content-quality apps?

Section titled “How is this different from archiving and content-quality apps?”

Apps like Better Content Archiving track page metadata — age, views, last edit — and help you archive what looks stale. WikiFix reads what pages actually say, finds where they contradict each other, and writes the fix. A page edited yesterday can still contradict the page next to it; page age won’t catch that.

Billed through Atlassian at a per-seat monthly price — see the WikiFix Marketplace listing for current pricing and seat tiers; Atlassian is the source of truth for price, not us. Your subscription converts into scan credits at your edition’s rate: every dollar you pay buys 120 credits on Standard and 140 on Advanced. Atlassian’s standard 30-day trial applies. The full mechanics: Credits & capacity.

The running scan stops cleanly and what it found stays on the scan. Scanning resumes with your next billing period’s grant — allow a few hours after your renewal date — or, on a paid Advanced plan, doesn’t stop at all if you’ve added your own Anthropic API key. See Credits & capacity.

Does it work on Confluence Data Center or Server?

Section titled “Does it work on Confluence Data Center or Server?”

No — Confluence Cloud only.

We’re in a regulated industry (FDA, SOX). Is WikiFix for us?

Section titled “We’re in a regulated industry (FDA, SOX). Is WikiFix for us?”

Probably not. WikiFix is not a compliance tool — no electronic signatures, no audit-evidence workflows, no formal approval chains. For regulated document control, Comala Document Management is the established choice. If you just need your internal knowledge base to stop contradicting itself, that we do.

Does WikiFix create content in my Confluence or Notion?

Section titled “Does WikiFix create content in my Confluence or Notion?”

One kind, visible and ordinary: comments. Ask owner posts a regular Confluence comment anchored to the passage in question, or a Notion comment on the page, handing the decision to the page owner. WikiFix never creates pages: scan results and run history live in WikiFix, applied fixes edit existing pages rather than adding new ones, and merging duplicate pages leaves the ones you didn’t keep live, replacing their content with a short notice pointing at the page you kept — so links to them still work. The comments remain after uninstall, and you can delete them like any comment.

Scans of your site stop at once, and the app token we cached for it is deleted. We keep the rest of your data for 30 days so a re-install picks up where you left off, then a daily job deletes it, whether or not you ask. Notion workspaces and other Confluence sites you added by hand stay connected for those 30 days, with their scheduled scans waiting. The comments WikiFix posted stay in Confluence and Notion. A few records follow their own schedule, such as AI records, logs and the change history: the DPA lists them. Want your data removed sooner? Email security@wikifix.ai. More in Security & data.

Does the WikiFix agent in Rovo send my data to Atlassian’s AI?

Section titled “Does the WikiFix agent in Rovo send my data to Atlassian’s AI?”

Yes, when someone uses it. Atlassian’s Rovo AI receives the finding text, page titles and the passages behind them, the text of any page the agent reads for them and, when they settle a finding, the before and after text. Your pages are already at Atlassian. It is the same on every Data handling level, Strict included, because the level doesn’t apply to it.

Not yet. We plan to obtain one, and the security page will say when we have.

support@wikifix.ai. A person answers.