Privacy Policy – Build Map for Jira
What Build Map for Jira reads, what it keeps inside your Atlassian site and for how long, and the only two outside services it talks to — MET Norway and Stadia Maps.
Data Privacy & Security – Build Map for Jira
Build Map for Jira is built by Simplify on the Atlassian Forge platform. Its code and data run on Atlassian’s infrastructure, in your Atlassian site. Simplify has no server that receives your data.
What the app reads
- Work items of the project — segments, permits, cabinets and drops: their summary, status, due date, links and the app’s own property — read as the person who opens a page or uses the planner, with that person’s permissions. Nobody sees more through Build Map than in Jira.
- Jira Service Management requests on the linked desk: contractors’ progress reports (percent done, blocker, note, photo) and residents’ Notify me requests.
- Confluence spaces a Jira admin may choose for the weekly report and permit letters.
- Work that no person starts — a contractor’s report as it arrives, the nightly snapshot, Load and Remove demo town after the admin who pressed the button is checked — reads as the app.
What the app writes in Jira and Confluence
- Due dates, the blocked flag and comments when a person presses Apply on the planner’s proposal, as that person; the crew lead becomes the assignee of moved work.
- Comments on a resident’s request when their street’s date moves, and answers to contractors.
- Drafts of the weekly report and permit letters in the Confluence space you chose. A person publishes or sends them.
- The demo town (project BMD, work items, JSM organisations and request types, all marked TEST), only when a Jira admin loads it.
What the app keeps (Forge storage, inside your Atlassian site)
- Segments: each segment’s map box and line, its design id and kind, and the work item it belongs to — while the app is installed.
- Streets: each street’s phase and due week for the resident page — rewritten every night.
- The forecast: rain, wind and gusts per hour for each map cell — 10 days; each day’s forecast and the rain that fell — 12 weeks.
- Applied moves: the work item, its old and new due date and the reason — 1 year.
- Contractors’ reports: percent done, blocker and a note of at most 500 characters — while the app is installed.
- Residents’ Notify me requests — until the street goes live.
- Weekly snapshots: homes passed, metres, live and pending per project — 2 years.
- Settings: weather limits, contractor capacity (with the crew lead’s account ID only: the name is looked up in Jira when Settings is shown and never stored), the linked desk, the report space. Your own Stadia Maps key, if you add one, sits in Forge’s secret store and is never shown again.
No email address and no resident’s name or address is kept by the app: those stay in Jira Service Management.
Outside services
Build Map talks to two services outside Atlassian. Neither receives a work item, a name or any text you write.
- MET Norway (api.met.no) — the weather forecast. The app sends only the coordinates of a map cell (a square of 0.025°, about 2–3 km across) and keeps the answer in its own storage. MET Norway’s data is free under CC BY 4.0; no key is needed.
- Stadia Maps (tiles.stadiamaps.com) — the street map under your segments. Your browser asks for map tiles by their tile numbers, with Simplify’s shared key or with your own key if a Jira admin added one. Stadia’s own terms apply to the key’s owner.
Without either service the app still works: the map draws a plain grid from your design’s coordinates.
Rovo and AI clients
- The Build planner agent in Rovo, Atlassian’s AI, is used only when a person opens it on a site with Rovo. It receives the facts the app gives it — segments, phases, due dates, the forecast’s verdicts, permits and capacity — and proposes moves; a person applies them.
- MCP tools for an AI client are off until a site admin turns them on in Atlassian Administration → Connected apps → Build Map → Tools. The AI client and its model are chosen by your team and are outside Build Map.
Data Access & Sharing
- Your data is never shared with third parties by Simplify, and Simplify cannot access it.
- The app’s logs record only what failed and an error’s name — never work item text, reports or account IDs.
- Segments, plans and history live in Forge storage and move with your site under Atlassian’s data residency.
Uninstalling
When the app is uninstalled, Atlassian deletes its Forge storage under Atlassian’s Forge data retention. Due dates, comments, crew reports and report pages stay in Jira and Confluence: they are your work items and pages.
Updates to the Policy
We may update this privacy policy to reflect changes in the app or legal requirements. Any updates will be posted on this page and take effect immediately.
Consent
By using Build Map for Jira, you agree to this privacy policy and our End User License Agreement (EULA). For privacy-related inquiries, contact us via our Support Desk.
For more information, please visit Atlassian’s Privacy Policy.