Data residency

Last updated: [to fill: date of publication]

Atlassian lets organizations choose where their Jira data is kept (data residency). LogQuill runs its own server and database outside Atlassian, so it keeps its own data, and Atlassian asks every app like it to say which of that data is in scope for data residency. This page does.

Where your data is today

LogQuill keeps your data in one place for every customer: the European Union.

• The database is in Frankfurt, Germany (Neon).
• The short-lived cache is in [to fill: Upstash region].
• Error reports go to Sentry in the European Union (Germany).

LogQuill doesn't support data residency yet: if your Jira site is pinned to another location (the United States, Australia and so on), LogQuill's data stays in the European Union. In Jira's Data residency settings, LogQuill shows as not following your site's location.

In scope

Everything LogQuill stores about your site, wherever it's kept:

• People: Atlassian account IDs, names, profile pictures, email addresses (when Jira shares them), time zones, languages, account status, roles and personal settings.
• Time: worklogs (including the copy of those logged directly in Jira) and plans, with their descriptions, days, durations, issues, work types, overtime, accounts, billable hours and other worklog fields; timesheets, their notes and review history.
• Absences: absences, their notes and approvals, supporting documents (such as medical certificates), leave plans and balances.
• Your site's setup: teams, members and projects, roles, settings, holidays, work types, accounts and their customers, worklog fields, saved reports and their shares.
• Where issues sit in Jira: the IDs of each issue's project, parent and epic, and project leads.
• The audit log, including the issue keys and names it records.
• Suggestions: the Jira activity kept for suggested worklogs, and the suggestions people dismissed or logged.
• Connections: connected calendars and a Tempo connection (stored encrypted), and API keys (stored as a fingerprint, never the key).
• The cache: answers from Jira held for a short time, such as a person's Jira profile (up to 15 minutes) and issue titles (up to an hour).

The full list, and how long each is kept, is in the privacy policy.

Out of scope

• Request logs kept by Cloudflare for a few days to run the server.
• Error reports sent to Sentry: the error, the page, your Atlassian account ID and site, and your browser type.
• Emails while they're delivered by Resend: the address and the email itself.
• Data in other services you connect, which stays where those services keep it: Google Calendar, Microsoft 365, Tempo, and Odoo.
• Data in Jira itself, such as your issues and the worklogs in Jira, which Atlassian keeps under your site's own data residency.

Moving between locations

While LogQuill keeps all data in the European Union, moving your Jira site to another location doesn't move LogQuill's data. [to fill: when other locations are supported, how a move works and how long LogQuill's part takes.]