RamsvioScopeTime for Jira

ScopeTime for Jira — Privacy 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.

Responsibility and purposes

Ramsvio provides time recording, project/activity classification, calendars, reports and configured reminders within Jira Cloud. For work information processed on an organisation's instructions, that organisation determines the purposes and lawful basis and Ramsvio acts as its processor under the agreed DPA. Where the organisation is itself a processor, the relevant chain of instructions applies. Ramsvio is responsible for its own processing; Atlassian does not assume that responsibility merely by hosting the app.

Ramsvio acts as controller for necessary business-contact details and correspondence used to answer enquiries, administer the supplier relationship, maintain security and meet legal obligations. The bases are contract or requested pre-contract steps where the individual is the contracting party; legitimate interests in support, business administration and security for organisational contacts; and applicable legal obligations for required records. These purposes do not authorise unrelated marketing or employee monitoring. The organisation must give its workers the appropriate information and establish its own lawful basis; installation alone is not employee consent.

Information processed

The People directory displays the names and account IDs of active personal accounts visible to the person opening it. Displaying a directory entry uses a temporary list. An authorised organiser can choose an entry, complete its profile and save the configuration. The list alone grants no app access and does not enrol a person in reminders.

For an optional calendar import, the organiser opens an Excel workbook in the browser. They review matches to ScopeTime profiles, confirm or skip entries and save the accepted changes. ScopeTime receives the selected configuration changes, which may include an employee number, calendar dates and categories, public holiday assignments and import source details. It does not upload the workbook. Calendar hours appear separately from work recorded on Jira issues. The sick-leave category can itself reveal health information, even where the record contains only dates and hours.

ScopeTime does not ask end users for Atlassian passwords or API tokens. It has no dedicated diagnosis field and is not intended for sensitive medical information, credentials, financial account numbers or other unnecessary sensitive data. Do not place these in comments, feedback, absence descriptions or selected export fields.

Use and access

Information is used to authorise requests, record and classify work, calculate configured capacity, show reports, produce requested exports, send configured personal reminders, handle support and privacy requests, reconcile uncertain operations and prevent duplicate writes. Atlassian's server-provided license state controls paid entitlement; card details are not collected by ScopeTime.

Ordinary users receive their own personal app records. Authorised organisation managers and Jira administrators can view wider reports subject to app roles and Jira issue permissions. An assigned team lead can view the configured team sheet and its individual analyses. Team, schedule and calendar information follows ScopeTime's organisational access rules. Reports and exports that identify a person can include the optional employee number beside their name. Authorised feedback support access is distinct from Jira administrator access and also requires access to that installation.

Reports describe recorded work and configured schedules. They are not automated employment decisions or guaranteed productivity measures. The reviewed runtime has no advertising, sale of personal data, external analytics or AI integration.

Storage, recipients and locations

Native worklogs remain in Jira. Forge KVS holds the app's records for the installation. The browser processes authorised data and generates downloaded reports. An authorised organiser can enable one of two Jira channels for a personal daily reminder or weekly report.

In both channels ScopeTime reads the recipient's own confirmed worklogs under their Jira permissions. Depending on the report, the message can include their name, the optional employee number in a weekly report, the period, project and calendar hours (including sick leave), entries awaiting classification, possible overlap times and a link to ScopeTime. Worklog descriptions and account credentials are excluded. ScopeTime verifies the account, saved audience, configuration and privacy state. A notification accepted by Jira, or a message prepared for an Automation rule, confirms that step only. The rule's execution and the recipient mailbox are separate from app storage. Previously saved issue-notification settings are preserved on upgrade.

The v0.17.12 app does not send messages to Resend or use a Resend API key. There is no Forge Remote backend or separate external app database. Emails and downloaded reports are separate copies.

Outside the runtime, support@ramsvio.com is forwarded by Porkbun to the operator's Google Gmail mailbox; the public website is hosted by OpenAI ChatGPT Sites. These services receive the correspondence or website-request data needed for their functions. Avoid emailing worklog exports or employee datasets; first send a redacted description. Necessary access must be arranged with the authorised customer using a verified channel and the minimum required data.

The operator is based in Portugal. Atlassian hosting, platform operations, downstream services, mail handling and website hosting can involve other countries. Forge storage residency does not establish the location of all processing. Atlassian Pty Ltd provides Forge under the Forge DPA, including its applicable transfer provisions. The Subprocessors and Business Services page identifies known services and their public privacy/processing terms. Processing can include the United States and other locations in those providers’ published information; this policy does not promise EU-only processing or a business processor agreement for the personal Gmail mailbox. Customer work datasets must not be sent through that mailbox without a separately assessed and authorised arrangement.

Earlier installed versions with the Resend integration may continue to use that external transport until upgraded. That earlier path sends the approved recipient address and personal message to Resend (Plus Five Five, Inc.); it is not part of the current native implementation. Previously accepted messages, provider records and recipient-mailbox copies are not recalled or deleted by an app upgrade. Historical provider information and handling are identified in the Subprocessors and Business Services page and retention policy. Disabling native delivery stops new scheduled requests; it cannot recall messages already accepted by Jira or remove copies in recipient mailboxes. No EU-only mail-processing guarantee is made.

Retention and deletion

App retention makes specified completed/cancelled operations eligible for minimisation after 90 days, completed feedback after 365 days without an update, and the derived discovery index after 30 days. Maintenance is resumable: these are eligibility periods, not instantaneous physical-deletion deadlines. Active or uncertain operations are preserved for reconciliation. Configuration, classifications, schedules, absences and preferences have no general age expiry. Minimal pseudonymous revision, replay and account-block markers can remain while needed. Full details and legacy-record exceptions are in the Data Retention Policy.

The external support-mail rule is removal of ordinary case correspondence and attachments within 12 months of closure, with monthly manual review. Temporary diagnostic copies are deleted within 30 days of closure or sooner when no longer needed. A specific legal requirement, active dispute or incident can require restricted retention for its documented purpose and applicable duration. This is an operator procedure, not automatic deletion configured in Gmail or a promise about provider backups. Required financial records have their applicable legal retention, to be confirmed in the commercial setup.

The app's personal erasure process removes supported account-linked records and structured references and prevents silent recreation. It can change historical report groupings. It does not delete native Jira worklogs/properties, delivered emails, downloaded reports, platform logs/backups or every mention in another person's free text. Those copies need separate instructions and handling. A self-requested storage block can be lifted only by explicit reactivation; a closed-account block cannot be lifted that way. License expiry does not itself erase work records.

Rights and contact

Contact your organisation about work-data rights, or email support@ramsvio.com with the subject PRIVACY. Ramsvio will identify the relevant controller and assist under the DPA. Identity and authority checks are proportionate; never send a password or API token. App reports are not a complete subject-access export, so some requests require assisted review.

Where Ramsvio is controller, applicable rights include access, correction, erasure, restriction, portability and objection. Requests are handled within the applicable statutory period, generally one month under the GDPR, with any permitted extension explained within that period. You can complain to the Portuguese supervisory authority, CNPD, or another competent authority.

The app uses Atlassian authentication and platform controls. No app-defined cookies or persistent browser storage were identified in the reviewed source; Atlassian and website hosting have their own practices. Material policy changes will be published on ramsvio.com, with an updated effective date and appropriate notice to affected customers. No separate ScopeTime certification or completed compliance audit is claimed.