Stint Privacy Policy

Last updated: August 11, 2026

Stint is a time tracking app for Jira built by Aquarium Apps (operated by Stargazers Consulting LLC). This policy explains what data Stint touches, where it lives, and what rights you have over it.

What data we collect

Worklog data. When you log time, Stint writes a native Jira worklog via Jira's REST API. That worklog lives in your Jira instance and is never otherwise copied, dispatched or sent to an external server.

App settings and state. Timer state (running timers, elapsed time), pinned issues, user preferences, and approval records are stored in Forge Storage (Atlassian's key-value store) and Forge SQL (a database hosted by Atlassian). These records are keyed to your Jira account ID.

Approval, audit, and import records. Approval records, audit log entries, and import job records are keyed to Jira account IDs. For example, the account ID of an approval's owner and reviewer, the account ID recorded as the actor on an audit log entry, and the account ID recorded as the creator of an import job. Some of these records include free-text fields you can fill in with personal data at your discretion, such as a rejection reason on an approval, and error messages generated during an import.

Worklog metadata property. When Stint creates or imports a worklog, it writes a property named io.stint.metadata directly onto the native Jira worklog, recording the account IDs of who the time was logged for, who created it, and potentially who imported it. This property lives in your Jira instance as part of the worklog, not in the Forge Storage or Forge SQL described above.

Jira account ID. Stint uses your Jira account ID to scope your personal settings. We do not store your account ID in any separate database we control - it exists only as a key within Atlassian's infrastructure.

(if you use Calendar Sync) Calendar connection preference. If you connect Google Calendar, Stint stores a connection preference (provider, which calendar, and when you connected) in Forge Storage, keyed to your Jira account ID. See "Google Calendar sync" below.

What we don't collect

  • No analytics or usage tracking
  • No cookies. Forge apps run inside Jira's own interface and there is no external web session.
  • No email address, name, or profile data, except the Google account email requested as part of the Calendar Sync connection, which is used by Atlassian's Forge platform to establish the connection

How your data is stored

All data Stint writes - worklogs, settings, and timer state - lives on Atlassian's infrastructure. Atlassian's own privacy commitments and data residency controls apply. You can review Atlassian's privacy policy at atlassian.com/legal/privacy-policy.

We do not operate any external servers, databases, or cloud functions related to Stint outside of Atlassian Forge.

Google Calendar sync

Stint includes an optional feature to read your Google Calendar events and convert one into a Jira worklog. When you connect a calendar, Stint requests read-only access to your calendar events (Google's calendar.events.readonly scope) and your Google account email (userinfo.email scope, used only to establish the connection). Calendar events are fetched live from Google each time you view them in Stint and are not stored.

The connection is handled by Atlassian's Forge platform. That is, Aquarium Apps code never sees or stores them. Only the connection preference described above is stored.

Disconnect is available in Stint's Settings page at any time.

Tempo import

Stint includes an optional feature to import time entries from Tempo. When you use it, the app calls api.tempo.io directly using an API token you provide. That token is stored as an org-level entry in Forge Storage. If you want to remove it, you can do so in Stint's Settings page at any time.

Your GDPR rights

If you are in the European Economic Area or United Kingdom, you have the right to access, correct, export, and delete your personal data.

Export: Go to Settings → GDPR → Export my data inside Stint.

Deletion: Go to Settings → GDPR → Delete my data. Doing so will do the following:

  • Deletes your entries in Forge Storage and your rows in the approvals and audit log tables in Forge SQL
  • Redacts your account ID in the io.stint.metadata property Stint writes onto native Jira worklogs. That is, your account ID is replaced with "[redacted]" in that property rather than the property itself being removed
  • Nulls out the account ID recorded as an import job's creator
  • Redacts your account ID wherever it appears in Tempo import logs

The worklog itself is a native Jira object and is managed through Jira directly; the io.stint.metadata property is Stint-authored data embedded in that worklog.

For any GDPR requests you can't fulfil through the app, email us at support@aquariumapps.io and we will respond within 30 days.

Data retention

Your data persists for as long as Stint is installed on your Jira instance. When the app is uninstalled, Atlassian's Forge platform soft-deletes your Forge Storage and Forge SQL records: Atlassian retains them for 28 days, during which reinstalling within 21 days and requesting recovery can bring them back, before they are permanently deleted.

Native Jira worklog fields (time spent, description, author) are unaffected by uninstall - they remain in Jira regardless. The io.stint.metadata property Stint writes onto those worklogs is different: uninstalling triggers an app-wide scrub that redacts the account IDs in that property (replacing them with "[redacted]") across every worklog Stint has written to, regardless of account. The property itself stays on the worklog; the personal data inside it does not survive uninstall unredacted.

Contact

Questions or requests: support@aquariumapps.io. See also the Stint Support page.

Aquarium Apps is operated by Stargazers Consulting LLC.