Privacy Policy — Mailpost for Jira

Effective: 18 September 2026

Mailpost ("the app") is published by Two Little Moons Consulting (ABN 49 732 400 198), based in Penrith, NSW, Australia ("we", "us"), on the Atlassian Marketplace. This policy explains exactly what the app does with data.

One thing is stated plainly up front, because it is the whole point of the app: when a site chooses to connect an email provider, the app sends the email you asked it to send through that provider. Who that provider is, what reaches it and who decides are set out below. A site that never connects one has no egress at all.

Where the app runs

The app is built on Atlassian Forge and its own code runs on Atlassian's infrastructure inside your site's installation. We operate no server. There is no backend of ours for your data to reach, no analytics, no error-reporting service and no sub-processor of ours in the path.

We cannot read your Jira data, and we never see the mail you send.

Data that leaves Atlassian, and where it goes

The app's manifest declares exactly one external host: api.postmarkapp.com. There is no user-supplied URL anywhere in the app, the delivery code re-checks the scheme, host and port immediately before every call, and redirects are never followed — so a 30x response cannot carry your API key anywhere else.

The provider is off by default. Until a Jira administrator connects one:

When a provider is connected, what reaches it is the message you composed: the recipients you addressed it to, the subject and body produced from the work item and the template chosen, and any attachment you explicitly chose to include. That is what sending an email means. Your provider's own terms and privacy policy then govern that message.

Declaring this host is why the app is not badged "Runs on Atlassian". We would rather say so here than bury it.

Data the app reads from Jira

Read on your behalf and with your own Jira permissions:

A work item you cannot open in Jira can never be emailed by you through this app.

Data the app writes to Jira

Data the app stores in Forge storage

All of it inside your Atlassian installation, never ours:

Data we collect about you

None. We run no analytics and receive no telemetry. We do not know who installs the app, who sends mail with it, or to whom. What we see is what Atlassian shows any Marketplace partner: aggregate install and licence counts for billing, and whatever you choose to tell us if you contact support.

Retention and deletion

Templates, rules, settings and the send log live in your installation and are removed when you uninstall the app. Disconnecting a provider deletes its stored key. You can revoke that key at the provider at any time, which takes effect immediately regardless of anything stored here.

Mail already delivered is held by your provider and your recipients under their own retention, not ours.

Data residency

The app stores End-User Data only within Atlassian apps and services, so it inherits your site's own data residency. The app itself offers no separate residency option. Mail sent through a connected provider is subject to that provider's residency, not ours.

Security

The provider key and inbound secret are held in Forge secret storage. Every read is performed with the permissions of the person asking, so the app cannot show or send anything Jira would not let that person see. Exactly one external host is declared, it is re-validated before every call, and redirects are refused.

Report a security issue to support@twolittlemoons.com. Our security statement is at https://ethanj2k.github.io/security.html.

Contact

Questions, or a request about data: support@twolittlemoons.com.

Two Little Moons Consulting, ABN 49 732 400 198, Penrith, NSW 2750, Australia.

Changes

Material changes will be published on this page with a new effective date, and noted in the app's release notes before they take effect. Adding an external service, or any new category of stored data, would be announced before it ships.