Security Policy: Sprint Automation for Jira Cloud (Automatic Start & Close)
This Security Policy describes how Sprint Automation for Jira Cloud (Automatic Start & Close) ("the app"), published by Divim, Inc., is secured and operated, and the safeguards that protect customer data. It applies to all Atlassian Marketplace cloud installations of the app.
Last reviewed: 2026-06-15
1. Atlassian Marketplace trust programs
Cloud Fortified. The app is Cloud Fortified, Atlassian's designation for apps that meet higher, continuously re-verified standards across security, reliability, and support. Maintaining the badge requires participation in Atlassian's security programs, defined Service Level Objectives, real-time monitoring, and a committed support response for critical issues, exactly the assurances you want behind unattended, scheduled automation.
Marketplace Bug Bounty Program. The app participates in the Atlassian Marketplace Bug Bounty Program and is continuously scanned by Atlassian's Ecoscanner.
SOC 2. The Atlassian Cloud platform the app runs on is covered by Atlassian's SOC 2 Type II. Divim does not hold a separate SOC 2 report for the app; Atlassian's platform report is available from the Atlassian Compliance Resource Center.
2. Platform and hosting
The app runs as a cloud app integrated with Jira Cloud. The underlying Atlassian Cloud platform is operated by Atlassian and is covered by Atlassian's own security certifications and controls, including SOC 2, ISO 27001, and the broader Atlassian Trust program. See the Atlassian Trust Center.
3. Authentication and authorization
The app authenticates through Atlassian's standard Marketplace app-installation and authentication model.
It requests least-privilege Jira permissions: only those required to read boards and sprints and to start, close, create, and update sprints and move incomplete issues.
Starting and closing sprints requires the Manage sprints permission on the relevant projects; the app operates within Jira's permission model and cannot exceed the permissions granted to it.
Administrative configuration, including selecting the boards the app automates, is restricted to Jira administrators.
4. Encryption
In transit: all communication between the user's browser, Jira Cloud, and the app is protected with HTTPS / TLS.
At rest: data persisted by the app is encrypted at rest.
5. Data handling
The app processes Jira data: boards, sprints, issues, and the configuration that controls automation (selected boards, schedules, sprint duration, and destination for incomplete issues), to start and close sprints automatically and move incomplete issues. Data is used only to deliver app functionality and is never sold. How the app accesses, uses, and retains data is described in the Privacy Policy. Because this app operates under Divim's partner privacy policy, the Privacy Policy is the authoritative description of data processing for this app.
6. Auditability
The app maintains audit, configuration, and automation logs that record configuration changes and automated sprint operations, so administrators can see exactly what the app did and when.
7. Software development lifecycle
Source is maintained in a private repository with branch protection; changes land through reviewed pull requests.
Schedule inputs are validated server-side (for example, dates must be in the future and end dates must follow start dates) before automation runs.
Dependencies are monitored against published security advisories; releases are versioned and published through the Atlassian Marketplace.
8. Vulnerability disclosure
Report suspected vulnerabilities to support@divim.io with the subject "Security Vulnerability Report: Sprint Automation". Researchers may also report through the Atlassian Marketplace Bug Bounty Program.
Please do not publicly disclose a vulnerability before a fix is available.
We acknowledge reports within 5 business days and aim to remediate verified high-severity issues promptly.
9. Incident response
In the event of a confirmed security incident affecting the app, Divim will triage, contain, and remediate the issue, notify affected customers via the published support contact where appropriate, and coordinate with Atlassian where the incident touches Atlassian-operated infrastructure.
10. Customer responsibilities
Grant the app the Manage sprints permission only on the projects you intend to automate, and review the boards configured for automation.
Maintain appropriate Jira user and administrator permissions.
Keep the contact details on the Atlassian site current so Divim can reach you with security notices.
11. Contact
Security issues: support@divim.io
Trust Center: https://trust.divim.io
This policy is reviewed at least annually and updated as the app evolves. Trust-program participation is verified on the Atlassian Marketplace listing.