RamsvioScopeTime for Jira

ScopeTime for Jira — Security Statement

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.

Architecture and data boundaries

ScopeTime is a Jira Cloud app built with Atlassian Forge functions, Custom UI and Forge KVS. Jira holds native worklogs. Installation-scoped Forge storage holds app configuration, classifications and operational records. The authorised user's browser generates report downloads and reads the calendar import workbook locally. An organiser reviews matches and saves the selected records. The app does not upload the workbook to a service. ScopeTime can use Jira issue notifications or a customer-configured Jira Automation rule. The v0.17.12 manifest declares no Resend fetch destination or read:email-address:jira scope. The app does not use Forge Remote or public web triggers.

Atlassian operates the Forge platform infrastructure. Ramsvio remains responsible for its application permissions, dependencies, operator access and incident handling. These implementation details describe v0.17.12. For historical reference, the v0.17.5 production deployment on 19 November 2026 identified Forge version 6.0.0 as eligible for Runs on Atlassian. The Marketplace listing shows the applicable platform status. A deployment and an installation upgrade are separate steps.

Identity and authorisation

Users access ScopeTime through their Atlassian session. Backend operations verify identity, app roles and relevant Jira permissions. Routine Jira work reads and worklog changes use the user's authority. A role or license flag supplied only by the browser does not grant server-side access.

Members use their own functions. Designated organisation managers and Jira administrators can access wider organisational functions and reports under app roles and Jira visibility. Worklog editing/deletion remains subject to authorship and Jira permissions. Assigned team leads can view the sheets for the teams they lead. The People directory uses the signed-in organiser's Jira permissions and shows active personal accounts. Viewing a directory page creates no profile, schedule or access grant. In-app feedback administration requires a separate server-authorised support account and access to that installation; Jira administrator status alone is insufficient.

ScopeTime checks the intended account, app access, configured audience, configuration revision and privacy state before releasing a personal report. The app reads the recipient's work with their Jira permissions. For issue notifications it also checks the saved issue's accessibility and submits one explicit recipient account ID to Jira. The request excludes assignees, reporters, watchers, voters and groups as automatic recipients. An immediate own-account test has its own duplicate-prevention records and a five-minute repeat limit.

In Jira Automation, the personal connection supplies the account identity. The action accepts the report kind and reads the address from that account's own Jira profile. It returns the recipient and report content to the rule, which the customer configures to send to that recipient. An unavailable address stops preparation. The app uses a claim for the account, report kind and period to prevent duplicate preparation. The rule history shows whether the subsequent step ran. App receipts do not establish delivery to the mailbox. Earlier installed versions may still use the previous Resend transport until upgraded.

Integrity, retention and privacy

Revision and privacy-generation controls protect app-owned writes. Timer and manual-entry reconciliation references help resolve uncertain Jira responses before repeating writes. Privacy erasure blocks stale writes and leaves a minimal account marker to prevent silent recreation. Supported terminal-operation retention and privacy maintenance continue independently of paid entitlement; see the retention policy.

Paid entitlement is checked using trusted Forge context. Test overrides are restricted to supported non-production environments and are ignored in Production. Missing entitlement restricts normal product use and scheduled emails; privacy, support and supported recovery remain available with applicable identity and permission checks. License expiry does not itself delete customer work records.

Diagnostics and operator handling

Explicit application backend logs use generic scheduled-cycle failure messages. ScopeTime's email receipts contain status and timing information. ScopeTime does not write the Automation action's recipient address or message body to those receipts. Jira Automation processes those outputs and maintains its own rule history. Transport errors are reduced to fixed messages and HTTP status codes. Jira and recipient-mailbox services process the message under their applicable arrangements. Historical external-delivery copies are described in the retention policy. Local browser diagnostics record operation names, timing and success in memory/console; no external analytics endpoint or automatic external log shipping is configured. Forge errors and operational metadata must be handled as potentially sensitive.

Ramsvio's adopted operating procedure limits customer-data access to authorised purposes, reviews contributor/support access, protects deployment credentials, requires applicable account-security controls and minimises support evidence. Ordinary closed support correspondence is removed within 12 months and temporary diagnostic copies within 30 days, with documented legal/active-incident exceptions. These are operator procedures, not a claim that Gmail automatically enforces them.

No ScopeTime-specific ISO certificate, SOC report, independent penetration-test attestation, disaster-recovery attestation or Marketplace security badge is claimed. Platform certifications must not be read as certifications of Ramsvio. Tests and source review reduce risk; they do not guarantee an absence of defects or establish every customer's configuration.

Vulnerability and incident contact

Email support@ramsvio.com, using the subject SECURITY, with the affected version, steps, impact and a minimal redacted example. Do not include credentials, unnecessary employee information or unrelated customer datasets. The channel is operated by Rui Alexandre Moreira de Sousa; it is not a separately staffed security team. It remains available when the app cannot be opened.

Ramsvio will handle security incidents under its adopted runbook, including containment, a restricted chronology, appropriate notification and corrective action. Applicable Atlassian incident reporting is made through its current P1 route within 24 hours of awareness. Customer notification follows the agreed DPA and applicable law; the published DPA standard provides notice without undue delay and no later than 48 hours for covered incidents. These are separate obligations.

Cloud vulnerability remediation follows the applicable Atlassian schedule: critical within 10 days, high within four weeks, medium within 12 weeks and low within 25 weeks from the applicable reporting/triage point. This is not a general resolution-time warranty for ordinary support requests. Support commitments apply separately.