Privacy policy

Last updated: [to fill: date of publication]

LogQuill is an app for Atlassian Jira, provided by [to fill: legal name], [to fill: address] ("we"). This page explains what the app stores about you and your organization, where it is kept, for how long, and who can see it.

Your organization decides to install the app and how it is used. For the data the app holds about you, your organization is the controller and we process it on its behalf. For questions about how your organization uses the app, ask your Jira site administrator.

What the app stores

About the people on your Jira site. Atlassian account ID, display name, profile picture address, email address when Jira shares it with apps, time zone, language, and whether the account is active. Also your role in the app, your personal settings (theme, language, how durations are shown, your dashboard layout) and when you last used the app.

Your time. Worklogs and plans: the day and time, the duration, the description, the Jira issue, the work type, the overtime mark, the account, the billable hours and any other worklog fields your site uses. This includes worklogs logged directly in Jira, which the app copies so that its views and reports match Jira. Timesheets and their review history, including notes and the reasons given when a timesheet is sent back.

Worklogs other apps made in Jira (such as Tempo): the author, the issue, the day and the duration, kept aside so they are not counted as anyone's own time.

How your site is organized in the app. Teams, their members and projects, roles and what they allow, settings, public holidays, work types, accounts (with their customer names and leads), worklog fields, and saved reports and who they are shared with.

Where issues sit in Jira. For each issue with time on it, the IDs of its project, parent and epic, and who leads each project, so reports can group time without asking Jira every time. Issue titles, statuses and other details are read from Jira when they are shown and are not stored.

An audit log of changes made in the app: who did what, when, and to whom. Entries name the Jira issues and projects involved (their keys and names as they were at the time).

Suggested worklogs. The app suggests time to log from what you did in Jira and, if you connect one, from your calendar.

• From Jira, the app keeps, for each day, which issues you created, commented on or changed, and when. This is so each past day is read from Jira only once. It is never shown to anyone but you and is deleted after about three months.
• Calendar events are read when the suggestions are shown and are not stored.
• The app keeps the suggestions you dismissed or logged (a code for each, and its day), forgotten about four months later, and, for meetings, the issue you picked for a recurring meeting or a meeting title, so later ones go on the same issue.

Absence supporting documents. When an absence type asks for one, the file a person adds to their absence (a PDF or an image, such as a medical certificate), its name and size. It may hold health data. It is stored encrypted by the app, opened only by the person, whoever approves the absence while it is their turn, and HR, and each opening is recorded in the audit log.

Calendars you connect (Google Calendar, Microsoft 365): the calendar account's address and the access you granted, encrypted. The app reads your events (title, description, start and end, whether you declined, whether it shows as free). It changes your calendar only if you ask it to add your approved absences: then it adds, moves and removes events named "Out of office", with their times (and your time zone) and nothing else, plus a hidden mark saying LogQuill added them, and keeps their ids to find them again.

A Tempo connection, if an administrator imports from Tempo: the Tempo API token they entered, encrypted, who connected it, and how Tempo's accounts and attributes map to the app's.

Support requests you send from the app: your message, your account ID, name and reply address, any screenshots you attach, and the technical details listed in the form before you send it. Screenshots are kept for at most an hour before they are sent, then only in the support email itself.

We do not sell this data, use it for advertising, use it to train AI models, or track you across other sites.

Where it is kept, and who processes it

The companies that process data for the app, what for and where, are listed on Subprocessors. In short: Atlassian hosts the app's pages inside Jira, Cloudflare runs its server, Neon hosts its database in the European Union (Frankfurt), Upstash keeps a short-lived cache, Sentry receives error reports (in the European Union), and Resend delivers its emails. Google, Microsoft and Tempo only take part if you or your administrator connect them.

The cache is a second place personal data passes through, for a short time only. To keep the app fast, it holds some of Jira's answers: your own Jira profile (your name, your picture and, when Jira shows it, your email address) for up to 15 minutes, and issue details such as titles for up to an hour. Nothing is kept there longer: each answer expires on its own and is read from Jira again.

LogQuill's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used only to show you your own meetings as suggested worklogs and, when you turn these on, to make absences of your Out of office events and to add your approved absences to your calendar; it is not used for advertising, sold, read by people, or used to train AI models.

How long it is kept

• While the app is installed and its subscription is active, your data is kept so the app keeps working.
• If the app is uninstalled or its subscription lapses, all of your site's data is deleted 60 days later. Administrators are emailed before that happens, and reinstalling within the 60 days keeps everything.
• When the app is uninstalled, people's names, email addresses and profile pictures are erased at once. A reinstall brings them back from Jira. API keys are deleted at once too.
• One exception: the name and email address of the people who manage LogQuill's settings (its administrators) are kept until the site's data is deleted, 60 days later. They're needed for one thing only: the emails telling administrators that the data will be deleted, a week and a day before it happens. They're deleted with the rest of the site's data.
• When someone's Atlassian account is closed, Atlassian tells the app within about a week (the app reports the accounts it holds data for, as Atlassian requires). Their name, email address and profile picture are then erased: they appear as "Former user", as in Jira. Their time, timesheets and the record of what they did stay with your site.
• Absence supporting documents are deleted a year after the absence ends (the absence stays), at once when the app is uninstalled, and when the person's Atlassian account is closed. A document uploaded but never added to an absence is deleted within an hour.
• Audit log entries are deleted after 6 to 7 months.
• The Jira activity kept for suggestions is deleted after about three months; dismissed and logged suggestions are forgotten after about four.
• A connected calendar is kept until you disconnect it in your settings, which deletes it at once.
• Cached answers from Jira expire within an hour; your Jira profile within 15 minutes.
• Error reports are kept by Sentry for its standard retention period.

Who can see it

Inside your organization, people see what their role in the app allows: their own time, the time of teams they lead, the time on Jira projects or accounts they lead, or everything for managers and administrators. A report shared with someone shows them what it shows its owner. Suggested worklogs, and anything read from your calendar, are shown only to you, whatever anyone else's role. An absence's supporting documents are shown only to its person, whoever approves it while it is their turn, and HR. Only you can edit or delete your own worklogs and plans.

We access your data only to provide the app and to answer your support requests. How it is protected is described on Security.

Your rights

You can ask to see, correct or delete the data the app holds about you. Ask your Jira site administrator first, as your organization controls it; you can also write to us at [to fill: privacy email] and we will help. If you are in the European Union, you may also complain to your data protection authority.

Changes

We will update this page when what the app stores, or where, changes, and change the date at the top.

Contact

[to fill: legal name], [to fill: address]. Email: [to fill: privacy email].