OVERALL RATINGS
INSTALLS
39
SUPPORT
- Partner Supported
Privacy and Security details
The Atlassian Marketplace partner is responsible for the accuracy of the information provided below. Details with a verified status are confirmed by Atlassian. For any further queries, contact the partner.
Data storage and management
End-User Data processed and/or stored outside of Atlassian apps and services (excluding process/storage of End-User Data in logs)
The app processes the following types of End-User Data:
The same End-User data that is stored
User email, to send the user who initiated a scan, a post-scan report
The app stores the following types of End-User Data:
User's accountId
Record of user's activity in the app (no PII), e.g. "user owns this scan report", "user started a scan"
Their auth token (minted by the app, in order to run scans on user's behalf and with user's access scope) - Encrypted
Encrypted BYOK API key, where a customer supplies their own Anthropic key for scanning
Data residency for in-scope End-User Data
Marketplace app supports data residency and stores End-User Data independently outside of Atlassian apps and services in the following locations:
🇩🇪
Germany
More information on the Marketplace app’s data residency policy can be found in app’s product documentation or please contact the respective Marketplace app partner at
support@wikifix.aiApp REST APIs
This app does not provide REST APIs.
List of in-scope End-User Data
App stores the following types of in-scope end-user data:
User account ID, user-created report, user's access token (encrypted) are stored in AWS Aurora, eu-central-1
User's activity in the product is recorded in Posthog (EU)
Product errors, that can be traced back to user by ID, are in Sentry (EU)
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
None
Migration of in-scope End-User Data between data residency supported locations
No
End-User Data shared with third-party entities
End-User Data accessed in logs
No
End-User Data processed and/or stored in logs outside of Atlassian apps and services
No
End-User Data in logs shared with third-party entities
No
End-User Data in logs shared with third party entities integral for app functionality
No
End-User Data stored after app is uninstalled
Minimum storage period post un-install:
30 days
Maximum storage period post un-install:
31 days
Custom retention period for End-User Data
Yes
Supports customer-managed egress
No.
The app only accesses domains declared during installation.
Security and compliance
Contact for app security issues
App’s e-mail contact:
support@wikifix.aiIntegration permissions with Atlassian apps
Delete comments on content.
Access and interact with your data from outside of Atlassian.
Access and interact with your data as the logged-in user from outside of Atlassian.
View comments on pages or blogposts.
Read a summary of space information without expansions.
View details regarding content and its associated properties.
View information about the content. Note that this does not provide access to the content itself.
Check if a user or a group can perform an operation to the specified content.
View email addresses of all users regardless of the user's profile visibility settings.
View details about groups including its members.
View page content.
View space details
View user details.
Read and write to app storage service
Create and update comments on content.
Create and update pages.
More information on the justification of app’s integration permissions are shared by the app’s partner hereCompliance certifications
None.
Marketplace Security Bug Bounty Program participant
No
CAIQ Lite
CAIQ Lite Questionnaire has not been submitted
Security policy
Full disk encryption for data stored outside of Atlassian
Yes
App accesses Atlassian Personal Access Tokens (PATs), user account passwords, or another type of shared secret
No
Privacy
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policyCompany/Organization is a 'data controller' under the General Data Protection Regulation (GDPR) with reference to this app
No
Company/Organization is a 'data processor' under the General Data Protection Regulation (GDPR) with reference to this app
Yes.
Company/Organization is a 'data processor' for the following types of End-User Data:
Email address, read from Confluence and used only at send-time for the scan-completion notification - never stored
Atlassian account identifier (atlassian_account_id) and the internal pseudonymous user ID derived from it
Encrypted user's access token
Encrypted BYOK API key, where a customer supplies their own Anthropic key
Product-analytics identifier and raw search-query text - every PostHog event carries distinct_id (our internal per-user ID), and search_performed additionally carries the user's own search text
Company/Organization is a 'business' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
No
Company/Organization is a 'service provider' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Yes.
Company/Organization is a 'service provider' for the following types of End-User Data:
Product-analytics identifier and raw search-query text - every PostHog event carries distinct_id (our internal per-user ID), and search_performed additionally carries the user's own search text
Encrypted BYOK API key, where a customer supplies their own Anthropic key
Encrypted user's access token
Atlassian account identifier (atlassian_account_id) and the internal pseudonymous user ID derived from it
Email address, read from Confluence and used only at send-time for the scan-completion notification - never stored
General Data Protection Regulation (GDPR) approved mechanism for transferring European Economic Area (EEA) residents’s End-User Data outside of the EEA
No. App does not transfer EEA residents' data outside of the EEA.
Privacy enhancing technologies (PETs) used to protect End-User Data
Yes
pseudonymization: WikiFix uses internal id as the cross-system key, with atlassian_account_id kept as an external handle only the Atlassian adapter resolves, so most of the system never touches the raw account ID directly
field-level encryption: OAuth tokens and BYOK keys are KMS-envelope-encrypted (refresh_token_ciphertext, access_token_ciphertext, byok_anthropic_key_ciphertext), not just generic disk encryption
data minimization by design: WikiFix does not store full page bodies/titles from storage, keeping only derived embedding vectors and short excerpts, necessary for analysis
Data Processing Agreement (DPA) for customers
Yes,
DPA
Did you find this information useful?
Atlassian will use this feedback to serve you better.