RamsvioScopeTime for Jira

ScopeTime for Jira — DPA Cover and Processing Schedule

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.

Agreement and execution

Ramsvio makes this service schedule available with the Bonterms Data Protection Addendum v2.0, Cover Page Version, including its Exhibits A and B, incorporated by reference. The standard is © 2026 Bonterms, Inc., available under CC BY 4.0. This ScopeTime cover uses the freely adaptable Bonterms cover-page structure; the underlying standard text is not reproduced or altered here except through the explicit Additional Terms below.

The Main Agreement is the ScopeTime Marketplace customer agreement identified in the Provider-Specific Terms and the Customer's Order. Provider is Rui Alexandre Moreira de Sousa, trading as Ramsvio. Customer is the legal person identified in that Order. The DPA Effective Date is the date on which both parties validly accept this cover and the incorporated DPA, and it applies to covered processing from that date. Ramsvio approved this form on 1 October 2026. Publication is not evidence of a particular customer’s signature or acceptance. If the Marketplace acceptance record does not unambiguously include this cover, the parties must execute it separately and identify the Order and customer details below before treating it as agreed.

Key terms

ItemScopeTime entry
Main AgreementBonterms Standard End User Agreement v1.0 plus ScopeTime Provider-Specific Terms and identified Marketplace Order
Provider/contactRui Alexandre Moreira de Sousa (Ramsvio); address above; support@ramsvio.com
Customer/contactLegal name/address in the identified Order; its authorised administrator/data-protection contact supplied with the acceptance record
Subprocessor ListScopeTime Subprocessor List, in the version supplied with this agreement
Designated EU Governing LawPortugal, when the EU SCC provisions apply
Designated EU Member StatePortugal, when the EU SCC provisions apply
Customer roleController, or processor with authority from its controller as identified in the acceptance record
Provider roleProcessor; subprocessor where Customer is a processor

Processing details

Subject matter is the operation and support of ScopeTime for Jira. The purpose is to record authorised work, classify it by project/activity, display calendars, aggregate reports, generate requested exports, deliver configured reminders and handle authorised support/privacy instructions. Operations include reading, validating, storing, displaying, grouping, updating, deleting and securely returning data. Processing is ongoing during use and scheduled maintenance; it is not limited to a one-time transfer.

Data subjects are the Customer's Jira users, employees, contractors, administrators, support-request authors and individuals mentioned in permitted issue/worklog content. Data comprises Jira identifiers/profile information and permissions; issue/project fields and native worklogs; schedules, holidays and absence dates/hours; team/department assignments; project/activity classification; preferences, saved criteria, timer/manual state, operational/revision/privacy records; and feedback and replies. The directory can temporarily display a person without a saved profile. Profiles can include an optional employee number, which can appear with the name on reports and exports. The optional calendar import reads the workbook locally. The organiser selects and saves the profile matches and calendar changes. Calendar reports distinguish annual leave, sick leave, other absences and public holidays from logged work. Optional exports can include additional fields selected by the Customer. The detailed boundaries and destinations are in the processing description.

No sensitive or special-category data is required or authorised for the core service. The Customer must avoid including it in selected fields or free text and must notify Provider if such data needs separate handling. This statement does not assert that the app can detect or technically prevent every such entry. A sick-leave category and its dates can reveal health information even without medical detail. The restrictions above also apply to calendar entries and imported data. A diagnosis is not requested.

Duration is the Main Agreement's term and the subsequent period necessary to perform authorised return/deletion and lawful restricted retention. The app's 90/365/30-day operational eligibility rules, exceptions for uncertain operations and minimal pseudonymous markers are described in the retention policy. They do not override a valid erasure instruction or the DPA. Export and return may require assistance because normal time reports do not contain every personal-data record.

Jira worklogs and delivered emails/downloaded reports are separate copies controlled under the relevant customer/platform relationship. Forge installation storage is subject to Atlassian's lifecycle; the provider must request/coordinate applicable deletion and accurately distinguish active data from platform backups. No unsupported physical-backup deletion deadline or EU-only processing promise is made in this schedule.

Security measures

The applicable technical measures are described in the Security Statement: Atlassian session identity; backend role, ownership and Jira permission checks; installation-scoped Forge storage; revision/privacy-generation controls; reconciliation and replay protections; minimisation/retention and supported erasure; and dependency maintenance. ScopeTime checks saved organisational authorisation, the intended account and duplicate-prevention records before releasing a personal report. Issue notifications use a saved Jira issue and an explicit recipient account ID. With Jira Automation, the action reads the connected account's own profile and returns its address and personal message to the customer's rule. The rule's send step and execution history are separate from the app's confirmation of preparation. Neither channel uses a separate external sending API from ScopeTime. Earlier installed versions and existing external-delivery copies remain identified in the processing description and Subprocessor List. This paragraph updates the technical implementation description; it does not change the DPA's legal commitments, acceptance mechanism or effective-date rules. These describe implementation and provider boundaries, not a certification.

Ramsvio’s adopted organisational commitments are restricted operator/contributor access, required account protections, confidential support handling, monthly closed-case review, a record of authorised access, and its incident/rights runbook. These are operational commitments; this schedule does not independently certify their implementation or any customer-specific configuration. No independent audit report, additional personnel or 24/7 staffed security team is asserted.

Additional terms and acceptance record

The parties identify support@ramsvio.com as Provider's privacy-notice address. Notices of a new directly engaged subprocessor use the Customer's authorised administrator email under the standard DPA. The standard 30-day notice/objection period and security-incident notice without undue delay and no later than 48 hours remain unchanged. Atlassian's separate incident reporting requirement is handled independently and can require earlier notice.

The standard DPA's cross-border mechanisms apply only where their conditions are met. They do not establish that a particular support-email provider has signed processor terms, is certified, or is appropriate for customer work datasets. The Subprocessor List distinguishes the Forge runtime agreement from ordinary correspondence/website services. Any additional customer-specific processing arrangement must be confirmed before its use. Provider is in Portugal; the competent authority for a particular SCC transfer follows clause 13 rather than being automatically assigned from the provider address.

For a separate execution, the acceptance record must identify the Customer's legal name/address, controller/processor role, data-protection contact, Order/reference, authorised signatories and dates. Ramsvio's signatory is Rui Alexandre Moreira de Sousa. Signature and acceptance fields remain intentionally unexecuted; they are not missing service-policy choices. Retain the exact agreed versions and acceptance evidence.