Security Policy for Kaijio Atlassian Marketplace Apps
At Kaijio, security is foundational to how we build, ship, and maintain Forge apps on the Atlassian Marketplace. This policy describes the security practices we follow across our app development lifecycle, aligned with Atlassian's Marketplace Security Requirements and the Forge platform's built-in protections.
1. Platform Security — Built on Forge
All Kaijio apps are built on Atlassian Forge, Atlassian's serverless app development platform. Forge provides a security-by-default architecture:
- Hosted on Atlassian infrastructure — no external servers, no self-managed hosting. Apps run inside Atlassian's compute environment.
- Tenancy isolation — Forge enforces strict isolation between customer tenants at runtime. One customer's data is never accessible to another.
- Data egress control — Forge apps run inside a second security layer that restricts when and how data can leave Atlassian Cloud. External calls are declared and auditable.
- Automatic environment management — Forge provisions separate development, staging, and production environments for every app automatically.
2. Authentication & Authorization
- Every API request is authenticated and authorized. Our apps use Forge's built-in authentication and never collect or store Atlassian user passwords, API tokens, or credentials.
- We follow the principle of least privilege — apps request only the permission scopes strictly necessary for their functionality.
- Where elevated permissions are required, we default to
asUser()context and verify permissions explicitly before anyasApp()invocation.
3. Data Handling & Privacy
- Kaijio apps do not collect, store, or process Personally Identifiable Information (PII) outside of the Atlassian Cloud environment.
- All data processed by our apps resides within Atlassian's infrastructure. Data residency is governed by Atlassian's cloud infrastructure and the customer's own configuration.
- We do not perform automated decision-making, profiling, or behavioral analysis of users.
- Secrets and credentials used by our apps (e.g., for external integrations) are stored using Forge's encrypted environment variables and
storage.setSecret()— never in source code, URLs, logs, or referer headers.
4. Secure Development Practices
- Input validation — all untrusted data is validated and sanitized to prevent injection attacks (XSS, SQL injection, and other OWASP Top 10 vectors).
- Dependency management — we continuously monitor third-party libraries for known vulnerabilities. No critical or high-severity CVEs are shipped in production. End-of-life runtimes are not used.
- Code review — all code changes undergo peer review before merge.
- CI/CD & automated testing — apps are built and deployed through automated pipelines with linting, unit tests, and security checks.
- Content Security Policy — we configure CSP headers and cookie security attributes (HttpOnly, Secure) where applicable.
5. Vulnerability Management
- We follow Atlassian's Security Bug Fix Policy with defined remediation timelines based on severity.
- Critical and high-severity vulnerabilities are prioritized for immediate remediation.
- We maintain a designated security contact registered with the Atlassian Marketplace ecosystem to receive and respond to Atlassian Marketplace Security (AMS) vulnerability notifications.
6. Incident Response
- In the event of a security incident affecting our apps or customer data, we will notify Atlassian through the ECOHELP channel within the required disclosure window.
- We will investigate, contain, and remediate the incident, and communicate transparently with affected customers.
- Post-incident reviews are conducted to identify root causes and prevent recurrence.
7. Vulnerability Disclosure
If you believe you have found a security vulnerability in any Kaijio app, please report it responsibly:
- Email: security@kaijio.com
- Include a description of the vulnerability, steps to reproduce, and the app name/version.
- We will acknowledge receipt within 2 business days and provide an initial assessment within 5 business days.
- We ask that you do not publicly disclose the vulnerability until we have had a reasonable opportunity to address it.
8. Atlassian Security Review
All Kaijio Marketplace apps undergo Atlassian's security review process before listing. This includes validation of permission scopes, data handling practices, authentication flows, and compliance with Atlassian's cloud app security requirements. We maintain compliance with these requirements on an ongoing basis as part of our regular update cycle.
9. Encryption
- In transit — all communication between our apps and Atlassian APIs, as well as any external services, uses TLS 1.2+ with HSTS enforced (minimum one year).
- At rest — any data stored by our apps uses Forge's built-in encrypted storage. We do not store customer data outside of Atlassian's infrastructure.
10. Access Control
- Internal access to app source code, deployment pipelines, and Marketplace vendor accounts is restricted to authorized team members only.
- Multi-factor authentication (MFA) is required for all accounts with access to production systems and the Atlassian Marketplace vendor portal.
11. Changes to This Policy
We may update this Security Policy to reflect changes in our practices, Atlassian's platform requirements, or applicable regulations. Updates will be published on this page with a revised date.
12. Contact
For security-related inquiries or to report a vulnerability:
Email: security@kaijio.com
General inquiries: info@kaijio.com
Company: Kaijio
Last updated: September 2026