Security & Compliance

Your data stays in Atlassian

TimeSnap is built from the ground up to be secure by design — powered by Atlassian Forge with no external data exposure.

🏗️

Forge Runtime

TimeSnap runs entirely inside Atlassian's Forge platform — a sandboxed, secure serverless environment managed by Atlassian.

🚫

No External Servers

We operate zero external servers or databases. Your Jira time data is never transmitted outside the Atlassian infrastructure.

🔐

Scoped Permissions

TimeSnap requests only the minimum Jira API scopes needed to function. No access to unrelated Jira data.

🌍

GDPR Alignment

No personal data is stored outside your Jira instance. Atlassian's data residency settings govern where your data lives.

🔍

Open Documentation

Our full security documentation is publicly available on GitHub for review by security teams.

Atlassian Trust

Listed on the Atlassian Marketplace and subject to Atlassian's security review process for Forge apps.

Data Flow

👤
Jira User
Logs time in TimeSnap UI
Atlassian Forge
Secure serverless runtime
📋
Jira Cloud
Work logs stored in Jira

No external services involved at any point in this flow.

Privacy Policy

TimeSnap does not collect, store, or process any personal data on external systems. All data accessed by the app (Jira issues, work logs, user identifiers) is processed within the Atlassian Forge runtime and stored within your Jira Cloud instance.

We do not use analytics, tracking pixels, or third-party data processors. The app has no login system, no external API calls, and no telemetry beyond what Atlassian's own platform logs.

For full details, refer to Atlassian's own Privacy Policy, which governs the Forge platform.

Service Level

Bug Response
72 hours
Critical bugs acknowledged within 72 hours via GitHub Issues.
Feature Requests
Reviewed monthly
All feature requests are reviewed and triaged on a monthly basis.
Uptime
Atlassian SLA
TimeSnap availability is tied to Atlassian Forge's own uptime SLA.