FAQ

Nothing, until you ask. Installing grants no scan, sends no data anywhere, and changes no pages. Your first scan starts when you start one from the Scans tab.

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, shows in page history, and reverts in one click.

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), 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 remembers that we’ve already asked once about a Marketplace review, so we don’t ask twice. 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.

On the default setup, your content stays in the EU: WikiFix stores and processes it in AWS Frankfurt (eu-central-1), and the AI analysis runs on AWS Bedrock in the EU. WikiFix keeps a derived index and the short excerpts behind findings, not a full copy of your wiki, and your content is never used to train AI models. There’s one exception, and only on a paid Advanced plan: if you add your own Anthropic API key, the AI step is sent to Anthropic’s API under your account instead — Standard installs and tenants still inside Atlassian’s 30-day evaluation don’t have this option. Details: Editions & plans, Security & data and the security page.

By default, everything runs on OpenAI’s gpt-oss-120b, an open-weight model served directly by AWS Bedrock in Frankfurt — AWS running the model weights in-region, not a live API call out to a third party. It does the reading: extracting the facts each page states and building the fact graph WikiFix compares pages against. Deciding whether two pages actually disagree isn’t a separate AI judgment call — it’s a fixed rule over that graph, so the same facts always produce the same result, every time. The same default model also authors the page rewrite when you apply a fix. Per AWS Bedrock’s contractual terms, no model provider has access to your prompts or completions.

On a paid Advanced plan you can bring your own Anthropic API key, and extraction, fact-graph building, and rewrites all run on Claude Sonnet 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 WikiFix catches — and what it doesn’t yet has the full list, including what’s being built next and what’s on the list after that.

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 a fixed rate: every dollar of list price becomes the same number of credits. 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.

No — Confluence Cloud only.

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.

One kind, visible and ordinary: comments. Ask owner posts a regular Confluence comment anchored to the passage in question, 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.

Server-side data is retained so a re-install picks up where you left off. Want it removed instead? Email security@wikifix.ai.

Not yet — and the security page explains exactly why, what we have instead, and what triggers the audit. We’d rather you read that than a vague compliance badge.

support@wikifix.ai. A person answers.