Privacy Policy

Effective 11 October 2026 · Version 2.8

This policy applies to the SentinelTime AI app for Jira Cloud, its native iOS and Android applications, and its optional standalone web experience. The independent publisher is Turna Apps (“SentinelTime”, “we”, “us”). For customer-controlled Jira End-User Data, Turna Apps acts as a processor under the customer's instructions. Turna Apps acts as an independent controller only for its own account, support, security, billing, and legal-compliance records.

1. Data we process

The Forge Marketplace app uses Atlassian's user authentication. The native applications use Atlassian OAuth 2.0 (3LO) through the system authentication browser and never ask the user to enter an Atlassian API token. Atlassian access and refresh tokens stay encrypted on the SentinelTime server; they are not returned to or stored in the mobile application.

2. How we use data

We process data to read and write worklogs requested by the user, provide weekly and team views, maintain tenant security, deliver optional language assistance, prevent abuse, diagnose failures, support customers, and meet legal obligations. We do not sell personal data or use customer Jira content for advertising.

3. Service providers and data egress

Forge remote calls are authenticated with Forge Invocation Tokens. Operational records are assigned to a workspace, server writes use a service role, and database Row Level Security prevents anonymous cross-tenant access.

The native application requests notification permission only when the user enables a local daily reminder. Reminder text contains no Jira issue content and is scheduled on the device. Microphone and speech-recognition permissions are requested only when the user starts optional dictation. Leaving the dictation screen or putting the app in the background ends listening. You can revoke these permissions in device settings and continue typing. SentinelTime does not add advertising, tracking, location, contacts, camera, photo-library, or cross-app tracking SDKs to the native release.

4. Retention and deletion

We retain workspace data while the subscription or account remains active and as necessary for service integrity and legal obligations. Activity signals used for suggestions expire after 30 days; share links expire no later than 90 days and store only a hash of the access token.

For Atlassian accounts whose personal data remains in our remote storage, we periodically report the account ID and oldest retrieval date to Atlassian's privacy API. If Atlassian identifies an account as closed or updated, we erase the stored account identifiers and their tenant-local pseudonyms; an updated user may need to reconnect and resync Jira data.

When the Forge app is uninstalled, installation-owned data is removed automatically. If the same workspace has a separate standalone subscription or another active installation, only the uninstalled Forge installation and its principals are removed. A verified deletion request removes remaining customer content and stored credentials within 30 days unless a longer period is legally required. Encrypted backups expire under the hosting provider's normal backup lifecycle.

In the native application, “Disconnect Atlassian” revokes the SentinelTime-side OAuth connection and clears the device session, protected draft, local operation ledger, and response cache. The operation ledger is otherwise limited to 100 entries and seven days and has its own clear control. Workspace records controlled by the Jira customer follow the retention and deletion rules above. An optional Turna Apps settings-backup account and its isolated preference record can be permanently deleted directly inside the app without deleting the separate Atlassian account or Jira records; the preference record is removed automatically with that backup identity. Users can also submit a verified privacy or deletion request through the Support page without signing in.

5. Security

We use transport encryption, tenant-scoped authorization, server-side token verification, least-privilege Jira scopes, encrypted credential storage for the standalone product, secret rotation, rate limits, and dependency scanning. No internet service can guarantee absolute security; confirmed concerns should be reported through our Security Policy.

6. Your choices and rights

Depending on applicable law, you may request access, correction, export, restriction, or deletion of personal data. Jira administrators can uninstall the app at any time. Native users can disconnect Atlassian in Settings, clear local operation history, sign out of the optional settings-backup account, permanently delete that backup account in-app, and submit a data request through the public Support page. Backup, assistance, and reminder features are optional.

7. International processing

Our providers may process data in multiple regions. Where required, transfers are protected by appropriate contractual and technical safeguards.

8. Data Processing Agreement

Where Turna Apps processes personal data on behalf of a Jira Cloud customer for the Marketplace app, the terms of our Data Processing Agreement apply in addition to this Privacy Policy.

9. Contact

Turna Apps · Independent software publisher · Türkiye
Contact support or submit a privacy request