Security policy
How Factuur for Jira is built, hosted and operated. This document covers data handling, encryption, access control, secure development, vulnerability management and incident response. For what we collect and why, and for your rights under the GDPR, see the privacy policy instead.
Architecture
The app has no backend of its own
Factuur for Jira is an Atlassian Forge app. Its functions, its storage and its front end all run on Atlassian's own infrastructure, inside the Jira Cloud site that installed it. Bit Flare operates no servers, no database and no object storage that hold customer data, and has no standing access to any customer's Jira site.
The practical consequence is that most of the attack surface a conventional SaaS add-on would have does not exist here. There is no host of ours to compromise, no credential of ours that would unlock customer data, and no copy of your invoices anywhere outside your own Jira site.
Tenant isolation
Forge scopes app storage to a single installation. Code running for one Jira site cannot address another site's data; the platform, not the app, enforces that boundary.
Sandboxed runtime
App functions run in Atlassian's hosted Forge runtime, with no shell, no filesystem and no inbound network listener.
Documents built in the browser
Invoice PDFs are rendered client-side, on the user's own machine. An invoice is only transmitted when someone chooses to email it.
No analytics
No tracking, no advertising, no cookies of the app's own, and no telemetry sent to us about how the app is used.
Data handling
What is stored, and where
Everything the app saves lives in Atlassian's Forge storage for the installing site: the company profile (name, address, KvK and VAT numbers, IBAN, logo, invoice footer), clients, roles and rates, issued invoices and their frozen snapshots, the invoice number counter, and reminder settings. The app also writes two Jira custom fields on work items — Billable and Invoice description.
Data residency follows the Jira site: Forge storage is held in the region Atlassian hosts that site in, under Atlassian's own data residency commitments. Bit Flare does not choose, move or replicate it.
Data that leaves Atlassian
Two actions, and only two, send anything outside Atlassian — both of them an email to the client the invoice is addressed to:
- Send to client, pressed by a user on an issued invoice.
- An automatic payment reminder, for an unpaid invoice due today or tomorrow. This is off by default and stays off until an administrator switches it on.
Each carries the recipient address, subject, message body and the invoice PDF to our email provider. Nothing else is ever transmitted off-platform.
Subprocessors
| Processor | Role, region and purpose |
|---|---|
| Atlassian Platform | Hosting, compute and storage for the entire app. Covered by Atlassian's own security program and data residency commitments. |
| Resend Email | Transactional email delivery, EU region (Ireland). Receives only the message and its PDF attachment. Email logging and retention are disabled on our account, so sent messages cannot be read back by us or by support. |
Retention
App data persists until the app is uninstalled, at which point Atlassian deletes the app's storage for that site. PDFs already downloaded and emails already sent are outside the app and are unaffected.
Support access
We have no mechanism to read a customer's data. Support sees only what a customer chooses to send us, and we delete it once the question is resolved.
Logging
Forge retains standard invocation logs for the app's functions, visible to us through the Forge developer console. They are used only to diagnose errors and are not exported anywhere.
No secondary use
Customer data is never used to train models, build profiles, enrich datasets or market to anyone, and is never sold or shared beyond the subprocessors above.
Encryption
In transit
Every connection is encrypted. Browser-to-Jira and Jira-to-app traffic is HTTPS, terminated by Atlassian. The
app's one outbound call, to the email provider, is HTTPS to api.resend.com. The app neither offers
nor accepts an unencrypted endpoint anywhere.
At rest
App data is encrypted at rest by Atlassian as part of the Forge platform — the app stores through the Forge storage API and never manages disks, volumes or backups itself. Atlassian documents the platform's encryption and key management in its security practices.
Secrets
The app holds exactly one credential: the API key for the email provider. It is stored as a Forge
encrypted environment variable (forge variables set --encrypt), is write-only once set,
is never readable from the deployed app's source or logs, and is scoped per environment, so development cannot
send with production's key. No credential, key or token is committed to source control. Deployment credentials
live as GitHub Actions encrypted secrets and are exposed only to the job that needs them.
Access control
Least privilege, declared in the manifest
A Forge app can only use permissions it declares up front, and Atlassian shows them to an administrator at install. Factuur for Jira asks for these and nothing more:
| Scope | Why it is needed |
|---|---|
read:jira-work | Work item summaries and logged time, to build invoice lines. |
read:sprint:jira-software | A sprint's name, so an invoice names a sprint rather than a numeric id. |
read:jira-user | The current user's time zone, name and email, to prefill their profile and date invoices in the right zone. |
write:jira-work | Setting the Billable field, only when a user toggles it. |
manage:jira-project | Placing the Billable field on project screens, from the settings page. |
storage:app | Saving settings, clients and invoices in Forge storage for the site. |
Writes run as the user, not as the app
Every call that changes something in Jira is made asUser, so Jira applies the acting user's own
permissions. Someone who could not edit a work item by hand cannot edit it through this app either, and only a
Jira administrator can reach the screen-configuration action. The app cannot escalate anyone's privileges,
because it has none of its own to lend.
Outbound traffic is allowlisted
Forge blocks all egress that is not declared. The manifest declares exactly one address,
api.resend.com. Any attempt to reach another host — whether through a mistake of ours or injected
code — fails at the platform, not at our discretion. Adding an address requires a new major app version that
every installing administrator must explicitly approve.
Our own accounts
The Atlassian developer account, the GitHub organisation and the email provider account are each protected with multi-factor authentication and unique, password-manager-generated credentials. Production deployment credentials exist only as repository secrets, not on any laptop.
Secure development
Every change goes through the same gate
Changes reach the default branch only by pull request, and the same automated checks run on the pull request
and on the branch it merges into: unit tests, ESLint, a production build, and forge lint, which
catches manifest faults such as a Jira endpoint used without its scope. Dependencies install from the committed
lockfile with npm ci, so a build cannot silently pick up a package that was never declared.
The deployment pipeline's GitHub token is read-only (contents: read), the Forge CLI version is
pinned rather than floating, and deploys are serialised so two merges cannot land out of order. Publishing to
production is gated on a deliberate version tag; merging alone never touches production, and a change to
permissions or egress additionally requires an explicit major-version approval.
Minimal dependency surface
The app's runtime dependencies are the Forge SDKs plus three small libraries for PDF and QR rendering. There is no web framework, no ORM and no analytics SDK to keep patched. Build and test tooling is confined to development dependencies and never ships in the deployed bundle.
Vulnerability management
How issues are found
- Automated dependency monitoring. Dependabot watches both the npm dependencies and the GitHub Actions used by the pipeline, and raises a pull request when a newer or patched version exists. Security advisories are raised as soon as they are published, not on the weekly schedule.
- Advisory audit in CI. Every pull request and every push runs
npm auditagainst the committed lockfile. A critical advisory fails the build outright, so nothing of that severity can reach a deploy unnoticed. Advisories below critical are reported on every run and triaged to the targets below, rather than blocking an unrelated change the moment they are published. - Platform patching. The runtime, the hosting and the storage layer are Atlassian's to patch, and are updated by Atlassian without action from us.
- Reports from users and researchers. See below.
How quickly they are fixed
Severity follows the CVSS v3.1 rating of the advisory, judged against how the app actually uses the affected code. These are the targets we hold ourselves to, measured from the moment we confirm the issue:
| Severity | Target |
|---|---|
| Critical (9.0–10.0) | Mitigated or patched within 7 days, and deployed as soon as it is verified. |
| High (7.0–8.9) | Patched within 30 days. |
| Medium (4.0–6.9) | Patched within 90 days. |
| Low (0.1–3.9) | Addressed in the normal release cycle. |
Bit Flare is a one-person company, which is precisely why these are written down: the response does not depend on anyone remembering to look.
Reporting a vulnerability
Email info@bitflare.nl with "Security" in the subject. Please include what you found, how to reproduce it, and what you think the impact is. We will acknowledge the report within one business day (Monday to Friday, CET) and tell you what we intend to do about it within five.
We ask for coordinated disclosure: give us a reasonable chance to ship a fix before publishing, do not access, modify or exfiltrate anyone else's data while testing, and test against your own Jira site rather than someone else's. We will not pursue legal action against researchers who follow that. There is no paid bounty programme, but we are glad to credit you.
Penetration testing
No independent penetration test has been commissioned to date. Because the app is a Forge app with no infrastructure of its own, the network and host layers a test would normally cover belong to Atlassian and are within the scope of Atlassian's own testing programme. Should Atlassian's Marketplace review require a scoped application-level test, we will commission one and update this page with the date and scope.
Incident response
If something goes wrong
On confirming an incident that affects customer data, we contain it first — which for this app usually means rotating the email provider's key, disabling the affected capability, or rolling the deployed version back — then establish what data was involved, fix the cause, and verify the fix before restoring the capability.
Where the incident is a personal data breach, Bit Flare acts as processor and the customer as controller. We notify affected customers without undue delay, with what we know at the time, so the controller can meet its own 72-hour obligation to the supervisory authority under the GDPR. We follow up with a written account of cause, impact and remediation once the investigation closes. Incidents originating in the Atlassian platform are reported by Atlassian under its own process.
Business continuity
Availability, backup and restore of the app's data are properties of the Forge platform and are covered by Atlassian's commitments; we hold no separate copy to restore from. The app's source is held in version control with full history, so any previously released version can be rebuilt and redeployed from a tag.
Certifications and compliance
What we hold, stated plainly
Bit Flare Software ontwikkeling holds no independent security certification of its own — no SOC 2 report, no ISO/IEC 27001 certificate. We would rather say so than imply otherwise.
What the app does inherit is the certified posture of the platform it runs entirely inside. Atlassian maintains SOC 2 Type II, ISO/IEC 27001 and ISO/IEC 27018 among others, covering the hosting, storage and encryption that Factuur for Jira depends on. Current reports and certificates are published in the Atlassian Trust Center. Our email provider's own compliance posture is published at resend.com/security.
GDPR
The app is built and operated in the Netherlands and processes personal data within the EU. The customer is the controller of the data in their invoices; Bit Flare is a processor acting on their instructions, as is each subprocessor listed in section 02. Data subject requests, and any question about our role, go to info@bitflare.nl; the privacy policy sets out the rights themselves.
Keeping this current
This page is reviewed whenever the app's permissions, egress or subprocessors change, and at least once a year. The review date at the top of the page is the last time that happened.
Contact
- Security reports
- info@bitflare.nl — "Security" in the subject
- Response time
- Within one business day (Monday to Friday, CET)
- Company
- Bit Flare Software ontwikkeling, eenmanszaak
- KvK number
- 42166689
- Address
- Caan van Necklaan 47, 2281 BB Rijswijk, Netherlands
- Privacy policy
- Privacy & data handling