keelapps/Mail Templates/Privacy policy
Privacy policy — Mail Templates for Jira
The short version
Mail Templates does not send your data anywhere. It runs entirely on Atlassian Forge, inside Atlassian's infrastructure. Notifications are delivered through Jira's own notification endpoint, so there is no external email service, no vendor server, and no third party. The app declares no external network permissions, which Atlassian enforces at the platform level.
What the app stores
Everything is stored in Forge app storage (Atlassian-hosted KVS) inside your own Atlassian tenant region.
| Data | Examples | Why |
|---|---|---|
| Project rules | per-event templates (subject and body), recipient configuration (reporter, assignee, watchers, voters, named users, groups) | to know what to send and to whom |
| Send log | timestamp, event type, issue key, result, recipient count | so every send is accounted for |
| Quota counters | sends per period | per-project and site-level volume limits |
| Dedupe claims | event fingerprints | one event, one email |
Personal data is limited to the Atlassian account ids and group names named in a rule's recipient configuration, and the account ids of the people who create and update rules.
What the app reads from Jira
At send time the app reads the issue fields a template actually references, so it
can interpolate them — {{issue.key}}, {{issue.summary}},
status, issue type, priority, assignee, reporter, labels, due date and project.
Those values go into the message and are not retained afterwards. The app never
reads issue descriptions, comment bodies, or attachments.
The app writes nothing to Jira. Its only write permission,
send:notification:jira, permits exactly one thing: handing a message
to Jira's notification service.
What is never stored
- Issue descriptions or comment bodies
- Rendered message bodies — the send log records that a send happened, not what it said
- Email addresses — delivery is handled by Jira's own notification service using Atlassian's infrastructure
- IP addresses, usage analytics, or behavioural tracking
Who can see it
Project administrators manage their own project's rules, checked as the calling user rather than assumed from the interface. Jira administrators see the site-level quota and the list of configured projects. Recipients always still have to be able to see the issue: Jira drops anyone who cannot.
Retention and deletion
- Deleting a rule deletes its configuration.
- The send log is a ring buffer: older entries are replaced by newer ones.
- Uninstalling the app removes all Forge storage.
Data residency
Whatever your Atlassian site's residency is. Mail Templates adds no storage outside Forge and therefore introduces no additional residency considerations.
Sub-processors
None. Atlassian hosts everything; there is no other party involved.
Changes
Material changes to what is stored or where will be reflected here and in the Marketplace listing before they ship.
Contact
support@keelapps.atlassian.net — for questions about this policy, and for data access, correction or deletion requests.