In Marketplace review · Updated October 7, 2026
Privacy policy
Last updated: October 7, 2026
This policy explains what the Portal Notices for Jira Service Management app ("the app"), provided by Bobob Apps ("we"), stores and why. The app is built on Atlassian Forge and runs inside your Atlassian cloud.
Summary
- The app stores only what it needs to show notices and remember who closed them.
- Everything is stored in Atlassian's Forge storage in your Atlassian cloud. The app sends no data outside Atlassian and uses no analytics or tracking services.
- We, the developer, cannot read your stored data.
What the app stores
| Data | Why | Where |
|---|---|---|
| Notice content and settings (title, message, schedule, maintenance window, audience, translations, color) | To show the notices you create | Forge storage |
| Saved templates (notice text and settings, and the account ID of who saved them) | So admins can reuse their own templates | Forge storage |
| Atlassian account ID of the person who created or last changed a notice, with times | To show who changed what | Forge storage |
| For signed-in people: account ID with the time they first saw or closed a notice | To stop showing closed notices, and to show admins how many people saw one | Forge storage |
| For visitors who aren't signed in: an approximate count of views per notice, with no identifier | To show admins roughly how many visitors saw a notice | Forge storage |
| For visitors who aren't signed in: which notices they closed | So the same notice doesn't come back | Only in the visitor's own browser (local storage) |
| App settings (whether project admins can post notices) | To apply your choice | Forge storage |
The app reads, but does not store, the following from Jira Service Management when needed: the customer organizations of the person viewing the portal (only when a notice targets organizations, and kept in memory for at most five minutes), and the lists of portals, request types and organizations (to let admins choose them).
Who can see it
Jira admins can see notices and counts for every portal; project admins for their own portal. Customers only see the notices meant for them.
Retention and deletion
Data is kept while the notice exists. Deleting a notice deletes its records. If you uninstall the app, Atlassian handles the stored data under its Forge data lifecycle.
Data location and transfers
Data is stored and processed by Atlassian under its own terms and data residency settings for your site. The app makes no external network calls.
Your rights
To ask about data the app stores for your site, contact your Jira admin, or email us at support@bobob.app. Because the data lives in your Atlassian cloud, your admin can delete notices and their records at any time.
Changes
We will update this page if the app starts storing anything new, and change the date above.
Contact
Bobob Apps — support@bobob.app
Questions? Email support@bobob.app. Bobob Apps · bobob.app