← Back to Epic Mapper

Privacy Policy

Last updated: March 2026

Overview

Epic Mapper is a personal project operated by Thomas Lees. It is made available as a convenience tool, primarily for internal team use. This policy explains what data is accessed and how it is handled.

What data is accessed

When you log in with your Atlassian account, Epic Mapper receives:

  • An OAuth access token issued by Atlassian
  • Your Jira account email address
  • Your Jira cloud instance URL

This information is used solely to make requests to the Jira API on your behalf. Jira project data (epics, issues, dependencies) is fetched live and is never stored persistently.

How data is stored

Your OAuth token and session data are held in server memory only for the duration of your session. No data is written to a database or disk. Sessions are cleared when you log out or when the server restarts. No personal data is retained between sessions.

Cookies

Epic Mapper sets a single session cookie (connect.sid) to maintain your login state. This cookie contains only an opaque session identifier — no personal data. It expires after 24 hours and is marked HttpOnly and Secure.

Third parties

Epic Mapper communicates only with Atlassian's APIs. No data is shared with any other third party. There is no analytics, advertising, or tracking of any kind.

Contact

Questions about this policy can be raised by opening a GitHub issue.