harvizzle — Atlassian Marketplace apps. Last updated 16 September 2026.
Scope
This policy covers every app published by harvizzle on the Atlassian Marketplace:
Simple Issue Templates, Simple Recurring Issues, Bulk Subtasks and
Page Sign-off.
Architecture, and why it shortens this document
Every app is built on Atlassian Forge and runs entirely inside Atlassian's own
cloud. Specifically:
There is no vendor server. No VM, no container, no database, no object store
operated by harvizzle.
Apps make no network calls to any host outside Atlassian. No external egress is
declared in any manifest.
Any data an app stores is held in Forge storage, inside Atlassian's cloud, scoped to the
customer's own site, encrypted at rest by Atlassian. harvizzle cannot read it.
Apps hold no API keys, tokens, passwords or shared secrets. Authorisation is
Forge's own scoped tokens, issued and rotated by Atlassian.
Most operations run as the signed-in user, under that user's existing product
permissions, so an app cannot do anything the person using it could not already do.
The practical effect is that the attack surface a customer's security team has to assess is the
app's declared scopes and modules, both of which are visible on the install screen, and nothing else.
Reporting a vulnerability
Email harvizzle@gmail.com with the subject line
SECURITY, or raise it through Atlassian's Marketplace security channel.
Please include the app name, the version, what you did, what happened, and what you expected.
A proof of concept helps. Please do not test against another customer's site.
What happens next:
Within 2 business days — acknowledgement, and a first assessment of
severity.
Critical and high severity — investigation starts immediately and a fix is
targeted within the timeframes set by Atlassian's Marketplace Bug Fix Policy.
Medium and low severity — scheduled into the next release.
You will be told when a fix ships. Credit is given on request.
Reports made in good faith will never be met with legal action.
Incident response plan
An incident is any confirmed or suspected compromise of an app, of the publishing account, or of
customer data reachable through an app.
Triage — same day. Confirm the report, establish which apps and versions are
affected, and assign a severity.
Contain. If an app version is actively dangerous, the offending version is
withdrawn from the Marketplace and, where the risk warrants it, the app is disabled rather than left
running.
Notify. Atlassian is notified through the Marketplace security incident process.
Where customer data is implicated, affected site administrators are notified by email, following
Atlassian's Security Incident Notification guidelines and any applicable legal deadline.
Fix and release. A patched version is deployed to the Forge production
environment. Because Forge apps are versioned by Atlassian, customers receive the fix without having
to install anything.
Review. Root cause is written up, a regression test is added to the app's test
suite, and this policy is updated if the process itself failed.
Development practices
All app logic is covered by an automated unit test suite that must pass before deployment. Those
suites cover the parts most likely to break safely-relevant behaviour, such as schedule calculation,
input parsing and approval state.
Dependencies are limited to Atlassian's own @forge/* packages. There is no
third-party runtime dependency tree to audit.
Every deployment runs forge lint plus a bundle-and-load smoke check, because a clean
lint alone has been observed to pass code that cannot start.
Apps request the narrowest scopes that make them work. Bulk Subtasks, for example, is
published with no storage scope at all, because it stores nothing.
Personal data
Where an app stores personal data it is limited to Atlassian account IDs, never
names, email addresses or profile details. Those apps implement Atlassian's Personal Data Reporting
API and report weekly, erasing identifiers belonging to closed accounts. Each app's privacy policy
states exactly what it holds:
Stated plainly, so that no customer has to discover it during procurement. harvizzle is a
one-person publisher. It does not hold ISO 27001, SOC 2, PCI or HIPAA certification, does not
commission external penetration tests, and does not run a paid bug bounty. What it has instead is an
architecture with no vendor-operated infrastructure to certify, which is why the questions those
programmes exist to answer mostly do not arise.