ScopeTime for Jira — Data Processing Description
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.
Parties and purpose
Provider: Rui Alexandre Moreira de Sousa, operating under the trading name Ramsvio (individual provider, Portugal), contact address: Rua dos Cambitos, n.º 530, 4510-027 Jovim, Gondomar, Porto, Portugal. Customer: the organisation installing ScopeTime for Jira. This technical description covers ScopeTime v0.17.12. The installed app version determines which features are available. This description is not, by itself, an executed customer agreement.
For customer work data, the customer is controller (or an authorised processor) and Ramsvio acts as processor (or subprocessor), with Atlassian Forge supporting that processing under the applicable terms. Controller activities for business correspondence are described in the Privacy Policy. The organisation is responsible for the lawful use of employee work information and for informing affected people.
Scope of processing
Data subjects include Jira users, employees and contractors whose worklogs or organisational records are included, administrators, feedback authors and people mentioned in permitted free text or optional exported issue fields.
Processing includes retrieval, validation, temporary display, classification, aggregation, storage, authorised modification and deletion, report generation, personal notifications, feedback handling and privacy lifecycle operations. The People directory uses the organiser's Jira permissions to display active personal accounts, including people with no time entries or saved profile. A directory query does not save a roster, grant access, add recipients or create capacity. It occurs when users interact with the app and during scheduled privacy and email processing.
Core data includes account identifiers and names, account status and permissions; issue and project identifiers and summaries; configured field values; native worklog author, start, duration, comment and restrictions; schedules, holidays and absence dates; team and department assignments; preferences and saved report criteria; and support request content. Jira may return additional profile fields, including email address and avatar references. Optional issue exports can broaden the data processed.
An organiser can save a person's profile with team, department, working hours and an optional employee number. Named reports and exports can show that number. Working time comes from Jira worklogs. Calendar reports distinguish public holidays, annual leave, sick leave and other absences. A date or number of hours labelled as sick leave can itself reveal health information. There is no medical diagnosis field.
An optional annual Excel import reads the workbook in the browser. The organiser reviews the employee-to-profile matches, confirms a name-based suggestion or skips a row, applies the chosen changes to a draft and saves the configuration. Selected changes can include an employee number, dated calendar entries and assignments, and the source year, employer and establishment used to recognise a reimport. The workbook and unmatched rows are not uploaded.
No special-category field is required for core time tracking. Free text and customer-selected fields can contain sensitive data. Customers should exclude unnecessary sensitive information and assess their own employment and data-protection obligations. Capacity and work reports should be interpreted with appropriate human judgement.
Processing locations and recipients
Jira is the system of record for worklogs. Forge Key-Value Store holds installation-specific configuration, classification and operational records. The user's browser receives authorised data and produces report downloads. Atlassian receives account identifiers and oldest-data timestamps through its personal-data reporting mechanism.
The chosen paid model uses Atlassian licensing and checkout. The app consumes trusted Forge entitlement status; it does not collect cards or invoke an external billing service. Marketplace customer and sales information accessed by the operator outside the app needs a separate processing inventory. The known external business services are Porkbun for domain/DNS and email forwarding, Google Gmail for the operator mailbox, and OpenAI ChatGPT Sites for the public page. They are not new runtime integrations; their data boundaries and public terms are described in the Subprocessors and Business Services page. No external runtime integration is added by those business services.
For personal reminders and weekly summaries, the organiser configures a channel and audience. The app reads only worklogs whose authorship matches the recipient, with that account's Jira access. The report can include the person's name, optional employee number in weekly reports, period, projects and hours, calendar categories including sick leave, missing classifications, possible overlap times and links into the app. The report excludes worklog descriptions and account credentials.
- Jira issue notifications. ScopeTime selects the saved issue as context, checks access and asks Jira to send the message to one explicit account ID. The app does not need the recipient email address on this path.
- Jira Automation. The action uses the connected person's own Jira profile. When a message is due, the rule receives that account's email address, the subject and the body for its send action. The address must be available from Jira. Each recipient needs their own connection. The rule runs without a notification issue. ScopeTime records preparation of the message. Jira Automation has its own rule and execution history, and the receiving mailbox holds a separate copy.
Earlier versions with Resend may continue the previously disclosed external path until upgraded. An upgrade does not erase existing provider or mailbox copies. Historical external processing is identified in the Subprocessor List and retention policy. Recipient mailboxes and downloaded reports are separate copies.
Atlassian's data-residency features apply to eligible hosted storage. Ramsvio operates from Portugal; Forge is provided by Atlassian Pty Ltd under its Forge DPA. Installation-specific storage location and applicable platform/downstream processing follow the customer’s Jira/Forge configuration and Atlassian’s published service information; the current installation location must be checked for a customer-specific residency assurance. Storage residency must not be described as a guarantee that every runtime, log, support or email operation occurs in one country.
Access and instructions
Customer instructions are expressed through installing the app, configuring access, catalogues, mappings and schedules, and authorised user actions. Routine Jira actions use user authority. Management reporting is limited to designated app roles and Jira-visible information. An assigned team lead can view sheets for the teams they lead and the corresponding individual analyses. Members receive their own people and absence records; shared project catalogues and destination mappings remain available for normal entry workflows.
Support can manage in-app requests only when its server-authorised account also has access to that installation. This is distinct from Forge contributor access to operational tooling. The provider must maintain and review both access paths and prohibit unnecessary copying of customer information into development or support tools.
Duration and end of processing
Application retention minimises specified terminal operations after 90 days, resolved feedback after 365 days and a derived discovery index after 30 days. It preserves native Jira records, application classifications and active configuration. Undated legacy terminal records start their grace period on first observation; an undated cache receives a fixed anchor. Pending or uncertain operations are retained until resolved or subject to a privacy action. Minimal duplicate/revision/account-block markers have no automatic age expiry and can remain pseudonymous personal data. No per-customer retention selector or automatic legal hold is implemented.
The hourly privacy trigger advances both personal-data handling and resumable retention; a full completed retention round schedules the next round no sooner than 24 hours later. Backlog, platform execution limits and errors may delay processing. Eligibility is not a maximum deletion SLA. The privacy reporting interval is separately derived from Atlassian's Cycle-Period, defaulting to seven days.
Erasure removes supported account-linked records and structured references, including holiday include/exclude arrays and saved report filters. Removing the only specifically included person removes that holiday entry so it cannot become universal. Generation/revision fences reject stale writers; a pseudonymous block prevents silent recreation. Explicit reactivation can lift a self-request block, not a closed-account block. A normal profile refresh revalidates cached profile data without erasing user-entered calendars or classifications.
Native Jira worklogs and their session properties, delivered emails, downloaded reports and platform logs/backups are outside this app erasure action. ScopeTime classifications and person-level presentation can change after erasure, even though worklogs remain. Personal references embedded in other people's free text require an assisted review rather than an unsupported universal detection claim.
Uninstallation follows Atlassian's hosted-storage lifecycle. Reinstallation is not an app-provided backup/restore mechanism. A deletion from active application storage is distinct from physical destruction of provider backups. Current Atlassian documentation contains differing recovery-period descriptions; confirm the applicable contractual lifecycle before supplying numeric maximum post-uninstall retention. No zero-day or EU-only guarantee is made.
Assistance and agreement
The ScopeTime DPA cover identifies the incorporated standard, processing details, security measures and acceptance mechanism. Publishing it makes the terms available; it does not establish that a particular customer has executed the agreement.
Contact support@ramsvio.com with privacy instructions and the authorised customer contact. The app has no complete one-click subject-access export; normal work reports omit preferences, feedback and some operational records. Ramsvio's assisted procedure identifies the relevant records, verifies authority, protects third-party information and distinguishes native Jira data, app records and external copies. No universal detection of personal references in free text is promised.
The Support Policy covers correspondence and contact procedures. Necessary customer-data access must be arranged with the authorised customer, using an appropriate verified channel. Do not send work datasets to the ordinary contact mailbox without that arrangement.