ScopeTime for Jira — Data Retention Policy
Provider: Rui Alexandre Moreira de Sousa, trading as Ramsvio (individual provider, Portugal)
Address: Rua dos Cambitos, n.º 530, 4510-027 Jovim, Gondomar, Porto, Portugal
Support, privacy, security and legal contact: support@ramsvio.com
Website: https://ramsvio.com/
Policy revision: 22 November 2026 · Technical description of ScopeTime v0.17.12. Original policies adopted on 1 October 2026.
1. Purpose and scope
ScopeTime retains information needed to record time, classify work and present reports. Its application retention process reduces older operational data while preserving native Jira worklogs and the classifications needed for historical reporting.
This policy covers data managed by the ScopeTime application in Forge storage. It distinguishes application records from data held by Jira, Atlassian platform services, email recipients and customer exports. The applicable customer DPA governs contractual return/deletion obligations. This policy does not itself establish execution of a customer agreement or Marketplace approval.
The periods below determine when a record becomes eligible for processing. Actual removal or compaction occurs when the resumable maintenance process reaches the record. They are not promises of immediate physical deletion at the exact end of a period.
2. Retention schedule
| Record category | Eligibility period | What happens |
|---|---|---|
| Completed or cancelled timer state | 90 days after completion or cancellation | Operational content is removed; a minimal idle state and revision remain. |
| Completed or cancelled manual time-entry state and receipts | 90 days after completion or cancellation | Operational content is removed; minimal request markers prevent the same request from creating another worklog. |
| Receipt confirming an explicitly requested worklog deletion | 90 days after confirmation | The receipt is reduced to a minimal revision and pseudonymous ownership marker. Maintenance does not delete a Jira worklog itself. |
| Revision and edit guards | 90 days after the available operation timestamp, or an initial observation grace period where no reliable date exists | Guard values are minimised; immutable keys remain to reject stale or repeated writes. |
| Email period marked as queued or definitively rejected | 90 days after its terminal state | Detailed status information is removed; a minimal period claim remains to prevent resend. Related attempts follow the terminal period state. |
| Last email status marked as queued, rejected, skipped or preparation error | 90 days after the status timestamp | A minimal status summary remains. This does not confirm mailbox delivery. |
| Feedback marked completed | 365 days after its latest update | Title, description, support reply and direct author identity are removed; list indexes are removed and a minimal replay-prevention marker remains. |
| Derived worklog discovery index | 30 days from the start of its cache retention period | The index is invalidated safely and can be rebuilt from Jira. Unreferenced old cache buckets are removed in subsequent processing. |
| Configuration, worklog classifications, saved profiles including optional employee numbers, schedules, holidays, leave and absence entries, and saved preferences | No general automatic age expiry in this version | Retained while needed for the active installation, until an applicable authorised change, deletion or privacy request. |
| Native Jira worklogs and their properties | Outside ScopeTime automatic cleanup | Governed by the customer's authorised Jira actions and the applicable Jira/Atlassian arrangements. |
Displaying the Jira People directory does not create a saved profile. An Excel calendar import reads the workbook in the browser. Matching a name does not save that row. An organiser reviews and saves selected profile and calendar changes, which follow the configuration row above. The source workbook remains under the customer's control.
Days are 24-hour intervals measured from the applicable timestamps. The date on which work was performed is not used as the age of an operational receipt or cache.
3. Pending operations and legacy records
ScopeTime does not automatically purge the content of timers or manual requests that are running, prepared, being saved, recoverably failed or awaiting confirmation. Pending, unknown and retrying email sends are not treated as completed. New or in-review feedback is retained until it is resolved or an applicable privacy action is processed.
This preserves the information needed to reconcile uncertain operations without silently losing time entries, creating duplicate worklogs or sending an email twice. Technical guard values can be minimised separately while their protective keys remain.
Where an older record has no reliable terminal timestamp, its retention grace period starts when the maintenance process first observes it. ScopeTime does not infer completion from the work date or original personal-data acquisition date.
A legacy index without an explicit cache retention start receives a fixed anchor based on an existing observation timestamp, a valid existing rebuild timestamp or the first observation time. Later rebuilds do not extend that anchor. An already old cache may be reset immediately when first processed; an undated cache receives a new 30-day period.
4. Minimal markers and pseudonymous data
Some keys must remain available to prevent duplicate worklogs, repeat email sends, replayed feedback submissions and writes based on stale revisions. Removing these keys without an equivalent replacement would remove those protections.
Following compaction, their values no longer contain names, direct Atlassian account IDs, descriptions, support replies or work classifications. Keys and markers may still contain account hashes, issue/worklog references, revision numbers or timestamps. These are minimal technical records that may remain pseudonymous personal data; they are not described as fully anonymous.
There is no automatic age-based deletion period for these protective markers while they remain necessary within the installation. Global privacy revision fences already contain only a timestamp and remain outside the retention scan. Applicable account-erasure handling may remove account-specific markers while preserving the controls required to prevent unintended data restoration.
5. How maintenance runs
The described release uses the existing hourly privacy maintenance trigger. After privacy processing, it attempts to advance retention in persisted batches. The configured automatic invocation processes up to 120 references, with pages of 20, subject to available execution time. It may process fewer references and resume later.
After a complete round, the next round becomes eligible 24 hours later. Large datasets can require multiple invocations. Old cache buckets may only become removable in the round after their index is reset. Platform scheduling, interruption, failure, backlog and privacy work can delay processing; this policy does not promise a maximum completion SLA.
Privacy erasure takes precedence. Maintenance progress, completion information and pending errors are available to authorised administrators through the application's privacy information. A failed run must be investigated and resumed; it must not be represented as completed.
6. Historical reports and Jira records
Automatic retention does not change the duration, author or date of a native Jira worklog and does not automatically remove its ScopeTime project/activity classification.
The discovery index is derived data. When its cache period expires, reports require the relevant reconstruction, which reads Jira again under current access permissions. Rebuilding starts from the beginning of the available worklog feed. Historical worklogs are not excluded merely because they are older than 30 days.
A personal-data erasure request is a separate operation and may affect historical classification or person-level presentation as explained below.
7. Personal-data erasure
A confirmed user request or applicable Atlassian privacy instruction may remove application personal data before the normal retention periods expire. The described release handles supported structured account references, including people included in or excluded from holidays.
If a holiday applied only to the person being erased, that holiday entry is removed. Removing its last inclusion must not unintentionally make the holiday apply to the whole organisation.
Erasure can remove personal preferences, organisational membership information, absences, feedback, associated classification metadata and derived caches. This can change historical groupings or person-level detail in ScopeTime even though native worklogs remain in Jira. ScopeTime does not claim to detect every personal reference placed in another person's free-text content.
A pseudonymous block remains after erasure to prevent automatic re-creation of the erased application data. A block caused by the user's own request can be lifted through the user's explicit reactivation action. A block caused by an Atlassian account closure cannot be lifted through that action.
Requests concerning native Jira records must be handled through the customer's Jira administration and applicable processes; application cleanup does not erase those records.
8. Licensing does not erase records
The Paid via Atlassian release checks product entitlement separately from privacy maintenance. Missing or inactive licensing blocks protected product use and scheduled email processing, while privacy handling and authorised recovery/support routes remain available. License expiry does not automatically erase Jira worklogs, configuration or historical classifications. Retention proceeds under this policy; it is not shortened to an evaluation period.
9. Storage and copies outside application cleanup
App-owned retention operates within the installation's Forge storage boundary. Jira issue notifications create separate Jira/mail-service and recipient-mailbox copies. With Jira Automation, an app receipt indicates that ScopeTime returned a prepared message to the rule. The rule's execution history, mail delivery and mailbox copies follow their own lifecycle. ScopeTime receipts store delivery or preparation status and do not retain the returned address or message body. Earlier installed versions with Resend may create external provider copies until upgraded, and records from previous sends can remain. Disabling delivery or uninstalling ScopeTime stops new app sends but does not automatically erase these separate copies or recall accepted messages.
This application process does not directly control the physical deletion of:
- native Jira worklogs, comments and properties;
- Atlassian platform logs, backups or recovery copies;
- data managed by Atlassian's uninstall and account/installation lifecycle processes;
- emails already queued or delivered to recipient mailboxes;
- PDF, HTML, Excel or CSV exports downloaded, copied or retained by the customer;
- copies in external support systems, where such systems are used.
The 31 October 2026 disclosure recorded the then-used Resend Free-plan periods: a 30-day email/log window while the account was active, remaining customer-data deletion within 90 days after provider-account termination, and seven-day provider backups. These are historical provider descriptions, not new ScopeTime deletion guarantees or a statement of current provider terms. App uninstall or migration to native Jira sending is not termination of the Ramsvio Resend account. Requests concerning existing external copies can be raised through support@ramsvio.com and coordinated under the applicable provider arrangements. See Resend retention information and DPA. Native Jira delivery and recipient mailboxes have their own arrangements.
No numeric physical-deletion promise is made here for Jira, Forge/platform backups, customer downloads or recipient mailboxes. Their applicable arrangements must be checked separately.
10. Administration, customer requirements and changes
The Forge retention eligibility periods are preserved by the native Jira notification implementation. Own-account email tests use the same privacy ownership and operation compaction controls, with separate duplicate-prevention markers. Check the version deployed in your installation. There is no per-customer retention selector or automatic legal-hold facility. A different requirement must be assessed before a contractual promise is made.
Rui Alexandre Moreira de Sousa is responsible for reviewing maintenance failures and support-copy retention. Policy changes require implementation review and evidence that historical reporting, duplicate prevention and privacy handling remain protected. Material changes are communicated under the customer terms.
Ordinary email case correspondence and attachments are removed within 12 months of closure. Temporary diagnostic copies are removed within 30 days of closure or sooner when unnecessary. A monthly review identifies closed cases and documented legal/active-incident exceptions. These are manual operator rules and do not establish physical deletion of email-provider backups.