keelapps/Prefill/Privacy policy
Privacy policy — Prefill for Jira
The short version
Prefill for Jira (“Prefill”, “the app”) is published by Keelapps. Prefill does not send your data anywhere. It runs entirely on Atlassian Forge, inside Atlassian's infrastructure. The app declares no external network permissions, which Atlassian enforces at the platform level — it cannot make an outbound call even if it tried. There is no Keelapps server, no analytics service, no third party.
What the app stores
Everything below lives in Forge hosted storage, on your own Atlassian site.
- Request forms you create. A name and description, the target project and issue type, and the field configuration — which fields the form fills, which it asks about, and the values you set for them. The account id of whoever created and last changed the form.
- Use counters. How many times each form was opened and submitted, and when it was last used. These are approximate by design.
- Recent issues. For each form, the last 20 issue keys it produced, with the account id of the person who submitted, a timestamp, and a random id the submitter's page made up for that submission, so that a second click on Submit is recognised rather than filing the request twice. Issue content is not stored — the summaries and statuses shown next to those keys are read from Jira live, each time you look.
- The last refusal. When Jira refuses a form's hidden settings, or a form stops fitting its project, the field involved and the wording of the refusal, with the date, so the form's owner can see what went wrong. Nothing a submitter typed is kept.
- Site settings, and the last observed licence state.
What the app does not store
Issue descriptions, comments, attachments, email addresses, and any Jira content beyond the issue keys described above. The only personal data the app stores is Atlassian account ids; display names are resolved from Jira when a page renders and are not persisted.
One thing that is up to you
The values you set on a form are stored as you type them. If you put personal data into a field's default or fixed value, that data is in Forge storage. The app cannot tell the difference between a routing label and a person's name.
How issues are created
Issues are created as the person submitting the form: the app asks Jira to act on their behalf, so Jira's own permissions decide whether the issue can be created, and the issue's reporter and creator are the submitter. Prefill cannot create an issue on behalf of someone who could not have created it themselves.
Prefill is for people who already have a Jira seat. It does not provide anonymous or external submission: every issue is created as the signed-in person who submits it.
Who can see what
- The request form behind a link is visible only to signed-in Jira users who have permission to create issues in the target project. Anyone else is told why they cannot use it, without the form's name or description; its project is named only to people who can already see that project in Jira.
- Values a form hides from submitters are applied on the server and are never sent to a submitter's browser. If Jira refuses one, the submitter is told that the form's owner has to fix it, not what the value is.
- A form's own page — its hidden values, use counts, recent issues and last refusal — and editing, retiring or deleting it are limited to the people who may build forms for the project it files into. By default that is the project's administrators; a Jira administrator can narrow it to Jira administrators only, or widen it to anyone who can create issues in that project. Jira administrators always qualify.
- A form's recent issues are listed only to viewers who can read those issues in Jira.
- Site-wide lists of forms are visible only to Jira administrators.
What Keelapps can see
Keelapps runs no servers of its own and cannot browse what the app stores on your site. Like every Forge app, Prefill's logs are shared with its developer by default, and your site administrator can switch that off (Atlassian Administration → Connected apps → Logs access). The app writes to them only when something fails unexpectedly, and then only the kind of failure, its HTTP status or storage error code, and where in the app's code it happened — never field values, hidden values, issue content or anyone's name.
Retention and deletion
Deleting a form (retire it first, then Delete on its page) removes its definition, its counters and its recent-issue list. When the app is uninstalled, Atlassian deletes its Forge storage after 28 days. Issues that were created through a form are ordinary Jira issues and are unaffected.
Sub-processors
None. Atlassian hosts everything; there is no other party involved, and Keelapps cannot browse your data (see What Keelapps can see). Forge storage is reachable only by the app itself, running inside Atlassian's infrastructure.
Because no data is transmitted outside Atlassian's infrastructure and the vendor neither accesses, stores nor transmits customer data, Keelapps is not a data processor for the purposes of this app. If your compliance team requires a Data Processing Addendum, Atlassian's standard addendum for the platform applies.
Data residency
Because everything is stored in Forge hosted storage, data residency follows your Atlassian site's data residency configuration automatically.
Changes
Material changes to what is stored or where will be reflected here and in the Marketplace listing before they ship. The effective date above moves with any change.
Contact
support@keelapps.atlassian.net — for questions about this policy, and for data access, correction or deletion requests.