Partner Security Policy
This policy explains how DevBuddy, the publisher of AnswerLoop, secures the app and the systems used to build and release it, how we manage vulnerabilities, and how we handle security issues and incidents. For how the app itself protects your content (permissions, what it stores, AI behaviour), see the AnswerLoop security and permissions page.
Scope and architecture
- AnswerLoop is an Atlassian Forge app that runs entirely on Atlassian's infrastructure ("Runs on Atlassian"). It makes no calls to servers outside Atlassian, and DevBuddy operates no servers that receive or store your Confluence content.
- App data is kept in Forge's hosted storage for your site, and AI requests go through Atlassian's Forge LLMs. These services are operated and secured by Atlassian.
- DevBuddy has no administrative console or database access to your Confluence content or to the app's stored data in production installations. That data can only be read by the app's own code running in your site, and changes to that code go through the release process below. (Atlassian's developer console shows app storage only for our own development and staging installations, which hold test data.)
Access control
- DevBuddy is a single-developer company. Only the developer's Atlassian account can deploy or configure the production app, and only the developer can change its source code.
- Multi-factor authentication is enabled on the Atlassian developer account and on the source-code hosting account.
- The development computer uses full-disk encryption, endpoint protection and automatic operating-system updates.
- App secrets are stored as encrypted Forge environment variables. They are never committed to source code or written to logs. The app does not ask for or store customer passwords, API tokens or other shared secrets.
Secure development and release
- Every change is tested in a separate development environment before it reaches production.
- Before each production release we run the automated test suite (including permission checks for restricted pages, cross-space questions and different user roles) and Forge's linter. A release that fails either is not deployed. After each deployment we confirm the app still passes Atlassian's "Runs on Atlassian" eligibility check.
- New permissions (scopes) are added only when a feature needs them and are reviewed before release; the app requests the narrowest scopes Forge allows for each feature.
- Operational logs contain record IDs, counts, timings and sanitized diagnostic statuses. They are designed to exclude question text, page content, personal data and credentials.
Vulnerability management
- We scan the app's third-party dependencies for known vulnerabilities before each production release and at least monthly.
- We do not knowingly ship dependencies with known critical or high-severity vulnerabilities. Lower-severity findings are assessed for whether they affect the app and fixed when a compatible fix is available.
- Security bugs in AnswerLoop are fixed within the timeframes set by Atlassian's Security Bug Fix Policy for Marketplace Apps.
- We monitor vulnerability reports from Atlassian's Marketplace security programme and act on them.
Reporting a security issue
Email support@devbuddy.ai with "Security" in the subject. We reply to security reports within 24 hours. Please include steps to reproduce and do not access other customers' data.
Security incidents
If we suspect a security incident affecting AnswerLoop or customer data, we:
- Assess the report and its impact.
- Notify Atlassian promptly, and no later than 24 hours after becoming aware of the incident, by raising a P1 ticket in its ecosystem support portal with the facts available, as Atlassian's incident guidelines require; then keep Atlassian updated during remediation.
- Contain it. For example, the app's AI features can be paused for one site or for all sites through a configuration change and redeployment, while search, saved answers and asking a person keep working.
- Fix the cause and release the fix through our normal tested release process.
- Inform the administrators of affected customer sites.
- Review what happened and update our processes to prevent a repeat.
What we don't claim
DevBuddy does not currently hold third-party security certifications (such as SOC 2 or ISO 27001), run a bug bounty programme, or commission external penetration tests. We will update this page if that changes.
Changes to this policy
We review this policy at least once a year and when our practices change. The date at the top shows the latest update.