Privacy Policy – Upstream for Jira Service Management

What Upstream reads in your service desk, what it keeps inside your Atlassian site and for how long, and why it only reads vendors' public status pages and never sends them anything about your desk.

Data Privacy & Security – Upstream for Jira Service Management

Upstream 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

  • Customer requests of the desk: their request type and the minute they were raised, to count them; and whether a request’s title names a vendor. Requests are counted, not copied: no request text, customer name or email is kept.
  • Request types of the desk, to bind them to vendors.
  • Incident work items the app opened, and the requests linked to them.
  • Pages a person opens are read as that person, with their permissions. Counting new requests and polling status pages have no person behind them and run as the app.

What the app writes in Jira

  • An incident work item when a person (or the Rovo agent at a person’s request) opens one.
  • A portal banner on the request types bound to the vendor, while the incident is open.
  • One reply to each linked request and a closing comment, with texts a lead approved.

What the app keeps (Forge storage, inside your Atlassian site)

  • Vendor feeds: each status page’s last answer — status, when it was checked, failures in a row — rewritten on every poll; the vendors’ incidents from their pages — name, impact, stage and times.
  • Request counts: per request type and minute — 35 days; per hour — 13 months (the detector’s baseline).
  • Spikes: start, end, peak, the verdict and the account ID of whoever dismissed one — 400 days.
  • Incidents: the vendor, the verdict, the work item, the banner, reply and closing texts a lead approved, the note, the account ID of who opened it, and the linked requests — while the app is installed.
  • Settings: the vendors each desk follows, bindings to request types (with the account ID of who bound one by hand), the detector’s sensitivity, the vendors’ SLA terms for the ledger, the agent’s proposals.
  • The demo: the recorded incident’s minutes and request titles — until Remove demo.

Outside services: public status pages only

Upstream reads the public status pages of the vendors you follow — Stripe, AWS Health, Duo, Atlassian, Twilio, GitHub, Cloudflare, Google Cloud, Azure (and Statuspage pages at *.statuspage.io) — plus up to ten status domains a site admin approves. These are plain requests for public pages: nothing of your desk is sent to them. Every domain is declared in the app’s manifest or approved by an admin in Atlassian’s own dialog.

Teamwork Graph

Where Teamwork Graph is available, the app writes each vendor incident to it (its hash and sequence are kept), so Atlassian’s search and Rovo can see that an outage happened.

Rovo and AI clients

  • The Upstream agent in Rovo, Atlassian’s AI, is used only when a person opens it on a site with Rovo. It reads the facts the app gives it — vendors’ status, counts, incidents — and every change it proposes is made at a person’s request.
  • MCP tools for an AI client are off until a site admin turns them on. The AI client and its model are chosen by your team and are outside Upstream.

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 request text, texts you wrote or account IDs.

Uninstalling

When the app is uninstalled, Atlassian deletes its Forge storage under Atlassian’s Forge data retention. Incidents, replies and pages stay in Jira: they are your work items.

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.

By using Upstream, 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.