Security Policy
This policy covers the apps Eolivion builds for Atlassian Cloud: Issues by Team for Jira Dashboards, Scrum Poker by Eolivion, Scrum Retro by Eolivion, Issue and Work Item Templates by Eolivion and Time in Status, Cycle Time and Lead Time by Eolivion, including the free editions. What each app stores is described in the Privacy Policy; this page is about how that data is protected.
The short version
The apps run entirely on Atlassian Forge. There are no Eolivion servers, no remote backend and no requests to any host outside Atlassian. Your data stays inside Atlassian's infrastructure, under Atlassian's own security, hosting and data residency commitments.
Where the apps run
- Every app is built on Atlassian Forge and qualifies for Atlassian's Runs on Atlassian program.
- The apps declare no external fetch permissions, so the platform itself blocks any connection to a host outside Atlassian.
- The apps have no secrets, API keys or tokens to store or rotate.
- The apps never ask for Atlassian passwords or credentials for any other service.
How data is protected
- In transit: every request goes between the browser, Jira and Forge over Atlassian's encrypted connections (TLS).
- At rest: what the apps keep lives in Atlassian Forge storage, which Atlassian encrypts at rest.
- Isolation: each Jira site's data is kept apart by the Forge platform. One site's app can't read another site's data.
- Access: Eolivion has no access to customer data. There's no admin console or database on Eolivion's side to look into.
Permissions
- The apps ask only for the Jira scopes they need, listed on each Marketplace listing.
- Requests to Jira run as the person using the app, with that person's own permissions. The app can't show anyone something they couldn't already see in Jira.
- Scrum Poker has one exception: it can save an estimate to a field that isn't on the issue's edit screen. Before that, it checks that the person saving is allowed to edit that issue, and stops if they aren't.
Secure development
- Text people type is escaped before it's shown, and limited in length on the server side. Forge's content security policy blocks inline scripts.
- Dependencies are checked for known vulnerabilities (npm audit) on every build, and a production release ships with no known vulnerabilities in them.
- Automated tests run before every release, and every production deploy is reviewed and run by hand.
- Logs hold only technical details (which function ran, the HTTP status and Jira's error message). No personal data, issue content or tokens are logged.
- The accounts used to build and publish the apps (Atlassian, source control, email) are protected with multi-factor authentication, and the development machine uses full disk encryption and up-to-date antivirus.
Personal data
- The apps store Atlassian account IDs only where a feature needs them, never names or email addresses. Names and avatars are asked from Jira when they're shown.
- Once a week, each app asks Atlassian which stored account IDs belong to closed accounts, and erases their data.
Reporting a vulnerability
If you find a security issue, write to security@eolivion.com or open a request on the support portal. Please include the app, the steps to reproduce it and what you think the impact is. Security reports are handled ahead of everything else, and you'll get a reply within 2 business days.
Fixes follow the Atlassian Marketplace security bug fix policy, counted from the report:
| Severity | Fixed within |
|---|---|
| Critical | 10 days |
| High | 4 weeks |
| Medium | 12 weeks |
| Low | 25 weeks |
If something goes wrong
If a security incident affects an app, Eolivion contains it first (by shipping a fix or disabling the affected feature), tells Atlassian within 24 hours as the Marketplace's incident guidelines require, and lets affected customers know what happened, what data was involved and what to do.
What Eolivion doesn't have
To be clear about it: Eolivion is a one-person company. It has no security certifications (such as SOC 2 or ISO 27001), hasn't had a third-party penetration test, and doesn't run a bug bounty program. The apps rely on Atlassian's platform for hosting, encryption and isolation, which is covered by Atlassian's own certifications.
Contact
Eolivion · Erik Carvalho Gomes de Oliveira · São Paulo, SP, Brazil
Security: security@eolivion.com · Support portal: eolivion.atlassian.net/servicedesk/customer/portal/1