Security

How your Jira stays safe.

Last changed 8 November 2026.

What the app may do

Sprint Board TV only reads. On Jira it asks for read-only permissions to boards, sprints, projects, tickets and the signed-in account, nothing that writes. The customer chooses one Jira site on Atlassian's approval screen, and the TV can read only that site, and only what that person can see.

Where sign-ins are kept

A TV's sign-in is kept in the Apple TV's encrypted keychain, on that device only, and is never synced to iCloud. The board goes straight from the Apple TV to Jira or Linear over TLS.

Atlassian's sign-in needs the app's own key, so signing in and renewing access go through our sign-in service at auth.sprintboardtv.com. It runs on Cloudflare and:

  • accepts only TLS 1.2 or later, with HSTS;
  • keeps the app's key as an encrypted Cloudflare secret, never in the app or its source code;
  • holds a finished sign-in sealed with AES-GCM until the TV collects it, then deletes it, or after ten minutes at most;
  • checks a single-use state value on every sign-in, and shows a code to compare with the TV, so a sign-in can't be replayed or slipped to the wrong TV;
  • keeps no logs, and stores no board data.

How it's built

  • Third-party libraries are checked for known vulnerabilities before each release.
  • Development machines use full-disk encryption, antivirus and automatic updates.
  • Every account used to build and run Sprint Board TV has two-step sign-in and a unique password from a password manager.

Reporting a vulnerability

Email support@sprintboardtv.com. We reply within two working days, and fix issues within the times Atlassian's Security Bug Fix Policy sets: critical ones within 10 days.

If something goes wrong

  1. Contain it: take the sign-in service offline or change its keys.
  2. Tell Atlassian within 24 hours, as its rules ask, and keep it updated until it's fixed.
  3. Tell the customers affected, within 72 hours.
  4. Fix the cause, then say here what happened and what changed.