Account and data controls

Delete a SentinelTime account

SentinelTime AI uses an existing Atlassian account for Jira access. It also offers a separate, optional Turna Apps account solely for backing up non-secret app preferences. The steps and effects below explain how to delete each SentinelTime connection without deleting the separate Atlassian account.

Delete the optional settings-backup account in the app

  1. Open SentinelTime AI and go to More → Optional settings backup.
  2. Sign in to the backup account if needed.
  3. Select Delete backup account and backup.
  4. Review the confirmation and select Delete account.

This permanently deletes the Turna Apps/Supabase authentication identity, its email address, authentication sessions, and the linked settings-backup record. The backup contains only allow-listed preferences such as target hours, default duration, reminder settings, and leave-form configuration. It does not contain Jira content, Jira credentials, AI keys, or operation history.

Disconnect Atlassian and clear local SentinelTime data

In More → Settings, select Remove connection and OAuth authorization. SentinelTime revokes its server-side Atlassian OAuth grant and clears the device session, protected worklog draft, local operation history, and in-memory response cache. This does not delete the Atlassian account or Jira records owned by the Jira customer.

Request deletion without the app

If the app is unavailable, send a private deletion request from the email address associated with the relevant account. Include only the account email and Jira site URL needed to locate the records; never send a password, token, or confidential Jira content. We verify the requester before deleting data.

Request account or data deletion

What is deleted or retained

  • A verified deletion request removes remaining SentinelTime-held customer content and stored credentials within 30 days unless a longer period is legally required.
  • Activity signals used for suggestions expire after 30 days. Shared report links expire no later than 90 days.
  • Encrypted infrastructure backups expire under the hosting provider's normal backup lifecycle and are not restored to active use after a verified deletion.
  • Security, fraud-prevention, transaction, or compliance records may be retained only where required by law or necessary to establish or defend legal claims.
  • Atlassian accounts, Jira projects, issues, and worklogs remain controlled by Atlassian and the Jira customer. Delete those records through the applicable Jira administrator or Atlassian account controls.
Need more detail?

Read the SentinelTime AI Privacy Policy for the complete data map, purposes, service providers, retention rules, and user rights.