Privacy Policy
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
- Atlassian identity and site data: account ID, display name, avatar, site/cloud identifier, locale, and email only when Atlassian makes it available.
- Jira work data: issue keys and summaries, projects, worklog dates, durations, authors, and comments required for the features you use.
- Workspace data: tenant membership, role, team directory, daily summaries, worklog requests, preferences, and service diagnostics.
- Optional Windows companion data: foreground application/window labels and activity intervals are stored locally for up to 21 days. Clipboard capture and screenshot capture are disabled by default and require separate user choices. Permitted screenshots are stored locally for up to five days; sending images to AI requires a separate opt-in. Windows OCR reads eligible windows locally and can be disabled in the tray or companion settings. Secret-like text is filtered before AI text processing.
- Activity evidence and assistance inputs: masked issue activity, optional integration events, text, and Jira context needed to create reviewable worklog suggestions. Raw commit content is not required for reporting.
- Optional mobile dictation: when you tap the microphone and grant permission, your device's speech-recognition service converts speech to editable text. Depending on the device and service, audio may be processed online by that service under its own privacy terms. This mobile dictation feature does not save audio files or send audio to SentinelTime's AI provider. The resulting text stays in the current screen until you choose to analyze it; Jira writes require a separate approval.
- Optional settings-backup account data: email address, Supabase account identifier, and an allow-listed copy of target, default-duration, reminder, and leave-form preferences. This Turna Apps account is separate from Atlassian and is created only when the user chooses the backup feature. Jira content, Jira credentials, AI keys, and the local operation ledger are not included in this backup.
- Standalone web connection data: only for the separate web product, encrypted OAuth or API credentials needed for a connection you explicitly configure.
- Optional Sentinel desktop audio: microphone and computer/system sound start disabled and require independent source consent. Enabling a source sends short audio chunks to the configured transcription service (Groq or OpenAI, directly or through Vercel AI Gateway). Spoken content cannot be masked before transcription. Raw audio is held only in memory by SentinelTime and is discarded after processing, cancellation or failure. Bounded transcript excerpts are encrypted with Windows DPAPI for your enrolled Jira account/site and expire after seven days while the companion is running. Capture pauses during lock, break, inactivity outside meetings, or manual pause. Source state is visible in companion settings and the Windows tray menu. Revoking a source cancels pending uploads; changing the enrolled account stops recording and resets source consent.
- Personal activity memory: your own historical worklogs and reviewed corrections teach task associations and writing style. The memory stores up to 1,000 bounded examples: task/customer topics, issue keys, recorded and observed duration, dates, and worklog wording. Browser storage and optional cloud synchronization are scoped to your own Jira account and workspace. Raw screenshots, raw audio, and transcript recordings are not stored in this cloud memory. Historical wording is an example of style, not proof that an old activity happened today.
- Optional automatic logging: when enabled, the day's open worklog proposals (issue key, title, duration and note) are stored in your own inbox so your phone can show them, and Sentinel sends a masked summary of the day and available transcript text to SentinelTime's AI service to match Jira issues. It then writes worklogs through the authenticated API using a signed session proof protected by your Windows account. Nothing is written automatically unless you chose "Write" mode; uncertain items remain for your review. You can switch it off or undo recorded worklogs.
- Native device data: a signed SentinelTime Jira proof, optional settings-backup access/refresh tokens, and the active protected worklog draft in operating-system secure storage; theme, target, reminder, pinned/recent issue helpers, and an account/site-scoped seven-day operation ledger in local application storage; and an in-memory Jira response cache discarded when the process ends. Operation history can include the worklog text required to perform a user-requested undo or redo.
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
- Atlassian Forge and Jira Cloud provide the host product, identity, licensing, and Jira APIs.
- Vercel hosts the SentinelTime remote API.
- Supabase hosts authentication and the tenant-isolated Postgres database.
- Third-party AI providers (DeepSeek, Groq, OpenAI, Google Gemini, Anthropic, OpenRouter or NVIDIA, depending on the service configuration) process minimized text and Jira context when assistance runs. The native apps ask for your permission before a note is sent for the first time, and you can withdraw it in Settings. Detected email addresses, phone and identity numbers, payment data, access keys, connection strings, and infrastructure addresses in text prompts are replaced before egress. Image input and desktop audio transcription require explicit, separate opt-ins; image pixels and audio may contain personal or company information that text masking cannot remove. Suggestions require a review/apply action unless the user explicitly enabled automatic "Write" mode.
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