LogQuillSubprocessors
The companies that process data for LogQuill, what for, and where.
Draft
The parts marked [to fill] are still to be completed before this page is published.
Last updated: [to fill: date of publication]
These companies process data on our behalf to run LogQuill. Each one only receives what it needs for its part, under its own data protection terms.
| Company | What for | What it receives | Where |
|---|---|---|---|
| Atlassian | Hosts the app's pages inside Jira (Forge) and vouches for each request | What Jira shows the app: people, issues, worklogs | Atlassian's own hosting, per your Jira site |
| Cloudflare | Runs the app's server | Every request to the server, and its logs, kept a few days | Cloudflare's global network, nearest to the person using the app |
| Neon | Hosts the database | Everything listed under "What the app stores" in the privacy policy | European Union (Frankfurt, Germany) |
| Upstash | A short-lived cache, to keep the app fast | Answers from Jira: your own Jira profile (name, picture and, when Jira shows it, email address) for up to 15 minutes, issue details such as titles for up to an hour; the site's settings for up to an hour | [to fill: region] |
| Sentry | Error reports and performance traces | The error, the page, your Atlassian account ID, your site, your browser type. No IP addresses, no request credentials | European Union (Germany) |
| Resend | Delivers the app's emails | The recipient's address and the email: timesheet reminders, approvals, shared reports, deletion notices, support requests | [to fill: region] |
Only when you or your administrator connect them:
| Company | What for | What it receives | Where |
|---|---|---|---|
| Reads your Google Calendar events for suggested worklogs, and adds your absences if you ask | Your calendar's access, granted by you: read only, unless you ask for your absences to be added | Google's own hosting | |
| Microsoft | Reads your Microsoft 365 calendar events for suggested worklogs, and adds your absences if you ask | Your calendar's access, granted by you: read only, unless you ask for your absences to be added | Microsoft's own hosting |
| Tempo | Imports worklogs and their attributes from Tempo | The Tempo API token an administrator entered | Tempo's own hosting |
Changes to this list
We update this page before a new subprocessor starts receiving data, and change the date at the top. [to fill: how customers are told, for example an email to site administrators, and how long before the change.]