Nativelog — Privacy Policy
The short version. Nativelog does not keep a copy of your hours. Every entry it creates is a native Jira worklog, written as you, and it stays in your Jira site. The only thing Nativelog stores is the timer you currently have running, and that record is deleted the moment the timer stops. The app runs entirely on Atlassian infrastructure and sends nothing to any third party.
Who we are
Nativelog is developed by Northstack Apps. For anything in this policy, contact [email protected].
For the purposes of the GDPR, the customer who installs Nativelog into their Jira site is the data controller. Northstack Apps acts as a data processor for the small amount of data described below.
Where the app runs
Nativelog is an Atlassian Forge app. It runs inside Atlassian's own cloud infrastructure and is eligible for Atlassian's Runs on Atlassian programme, which means app data is stored on Atlassian-operated infrastructure in the same way your Jira data is. There is no Northstack Apps server involved in running the app, and no data is transferred to one.
What Nativelog stores
Exactly one kind of record, and only while a timer is running:
| Data | Why | How long |
|---|---|---|
| Your Atlassian account ID | To keep your running timer separate from anyone else's | Until the timer stops or is discarded |
| The ID and key of the work item the timer is running on | To know where to log the time when you stop | Until the timer stops or is discarded |
| The instant the timer started | To calculate the duration | Until the timer stops or is discarded |
| Only if saving to Jira failed: the reason, the number of attempts, and whether the save may have reached Jira anyway | So that trying again does not log the same time twice | Until the timer stops or is discarded |
When you stop a timer, that record becomes a native Jira worklog and the stored record is deleted. No logged hour is ever kept in Nativelog's own storage.
What Nativelog reads
To show your timesheet, Nativelog reads worklogs, work items and project data from your Jira site through Atlassian's official APIs, using your own permissions — it can never see anything in Jira that you could not see yourself. This data is read at the moment you open a screen, used to draw that screen, and not retained afterwards.
Nativelog also asks Jira which permissions you hold on a work item, so it can tell you up front whether you are able to log work there.
And it reads two sets of settings, so that it behaves the way your Jira does: your site's time tracking settings (the default unit, the hours in a working day and the days in a working week), and the time zone and language of your Jira profile. They decide what a number you type means and which day an entry belongs to. They are not stored either.
What Nativelog writes
Native Jira worklogs, created, edited and deleted as you rather than as the app. That is the entire point of the product: your time appears under your name in Jira's own Work log tab and in reports, and it survives the app being uninstalled. Nativelog only ever edits or deletes worklogs whose author is you.
What Nativelog does not do
- No analytics, tracking pixels, or usage telemetry. The app's page at admin.atlassian.com shows two switches that Atlassian enables for every app, Analytics data access and Custom metrics access. The first lets an app send data to analytics domains declared in its manifest; Nativelog declares none. The second lets an app record custom metrics; Nativelog records none. The only usage figures that exist are the invocation counts Atlassian itself collects, listed under What we can see.
- No cookies beyond what Atlassian itself sets to run Jira.
- No advertising, and no selling or sharing of data with anyone.
- No third-party sub-processors. There is no service beyond Atlassian in the path.
- No AI or machine-learning training on your data.
- No copy of your worklog history in any database of ours, because there is no database of ours.
Data retention and deletion
A running-timer record is deleted when the timer stops or is discarded. If you uninstall Nativelog, Atlassian deletes the app's storage for your site, which removes every remaining running-timer record for every user at once, and reinstalling does not bring them back. A timer that was still running at that moment had not been logged yet, so that time is lost; the people affected get no warning from Jira or from us. Ask them to stop their timers before uninstalling.
Worklogs are not deleted when you uninstall, because they are not ours to delete: they are ordinary Jira worklogs and they stay in your Jira site exactly as if they had been entered by hand. This is deliberate, and it is the main reason the product exists.
Your rights
Because Nativelog stores almost nothing, most requests are answered by Jira itself: your logged hours are Jira data, and your Jira administrator can export, correct or delete them through Atlassian's own tools. For the running-timer record, stopping or discarding the timer deletes it immediately.
For any request under the GDPR, LGPD, CCPA or similar legislation — access, correction, deletion, portability, or objection — write to [email protected] and we will respond within 30 days.
Permissions
Nativelog holds no credentials of its own. Every call to Jira is made through Atlassian's authenticated APIs on your behalf, with your own Jira permissions.
The install screen lists four permissions. This is what each one is used for:
| On the install screen | Scope | What Nativelog does with it |
|---|---|---|
| View user profiles | read:jira-user |
Knows who is logging time, and reads your profile's time zone and language and the site's time tracking settings |
| View Jira issue data | read:jira-work |
Reads worklogs, work items, projects, and your permissions on a work item |
| Create and manage issues | write:jira-work |
Creates, edits and deletes your own worklogs, and nothing else |
| App storage | storage:app |
Keeps the running timer described above |
The third permission is broader than what the app does, and you should know that. The scopes Atlassian recommends for apps have no "worklogs only" option: the permission that lets an app write a worklog would also let it edit or comment on a work item. Nativelog does neither. The only write requests in its code go to Jira's worklog endpoints.
Two things hold that in place besides our word:
- The app always acts as you, so it can never do anything in Jira that you could not do yourself.
- It refuses to edit or delete a worklog whose author is not you, even when your Jira permissions would allow it.
Atlassian also publishes finer-grained scopes. We do not use them yet: its API reference marks them as beta for these operations, its guidance is to use the classic ones where they exist, and the finer-grained set for editing a worklog still includes permission to write comments. We will revisit this when they are stable.
What we can see
No server of ours is involved, but Atlassian gives every app vendor a developer console. This is what it shows us about a site that has Nativelog installed:
- That the app is installed: the site's address and the app version it is running.
- Usage counts: how many times the app ran, how many of those runs failed and how long they took, per site.
- Error logs: when something fails, the app writes one line with the reason (for example, "permission denied") and the place in our code where it happened. It never writes what you typed, a work item's title, or the contents of a worklog.
- The app's stored data: the console can display what an app keeps in its storage for a site. For Nativelog that is only the running-timer record described under What Nativelog stores, and only while a timer is running.
A site administrator can turn off our access to the logs at admin.atlassian.com, and can read or download them there. Nativelog works the same with our access turned off.
None of this shows us your worklogs, your work items or anything you type, and the app's code does not send them anywhere outside your Jira site. This list is complete as of the date at the top of the page; if Atlassian's console starts showing vendors more, the list and the date change.
Beta programme
During the private beta, the same rules apply without exception. What we can see about a participating site is exactly what is listed under What we can see. Feedback reaches us only when a participant sends it.
Changes to this policy
If this policy changes in a way that affects what is stored or who can see it, the date at the top changes and participants in the beta are told directly.