ScopeProfit — customer terms and processing agreement

Version 1.0 — 20 September 2026.

Agreement

For orders made through Atlassian Marketplace, the agreement consists of the Bonterms Standard End User Agreement (Version 1.0), unmodified, together with the Provider-Specific Terms and attachments below. It takes effect between the customer and the provider upon the customer's first order as provided in that standard agreement. This page does not itself accept an order or establish that the app is available for sale.

Standard agreement: https://www.atlassian.com/it/licensing/marketplace/end-user-agreement-v1

Provider-Specific Terms

Provider and product. Provider is Jon Ander Irazusta Iribar, trading as ProfitSignal Labs. Product is ScopeProfit for Jira. Legal notices may be sent to support@profitsignallabs.dev and the address in the Legal Notice.

Governing law. Spanish law applies, without excluding protections or jurisdiction rules that cannot lawfully be excluded. For disputes between businesses, the agreed courts are those of Donostia–San Sebastián, Spain.

Permitted use and documented limits. The Product is offered for internal business use with Jira Cloud. This release supports projects containing up to 200 issues visible to the user and sites with up to 1,000 visible projects. The Product uses original time estimates, not story-point conversions or actual worklog costs. Project financial access requires Browse Projects and Administer Projects permissions. A saved issue becoming inaccessible may block the project view.

Commercial records. Calculations depend on customer-entered information and Jira data. Missing estimates count as zero hours. The customer must review forecasts and supporting commercial evidence. Recording approval is an internal action; it does not send a quote, obtain a client's agreement, issue an invoice or collect money. The Product does not guarantee profit, savings or collection of change fees.

Attachments. The published Quick Start is the Documentation. The Support Policy and Security Measures below apply. The Data Processing Agreement below applies to Customer Personal Data processed on the customer's behalf. The Privacy Notice explains processing for the provider's own purposes and the service architecture. For personal-data processing, the DPA prevails over inconsistent terms to the extent required to protect that data.

Support and availability. No additional contractual uptime percentage is offered. Support response commitments must meet the Marketplace Partner Agreement: a response within 24 hours for requests identified by Atlassian as critical and within five business days for other requests. Response is not a promise of resolution within that time. This does not remove the obligations and remedies in the Standard Agreement or mandatory law.

Customer data use. The provider does not sell customer data, use it for advertising or use it to train AI models. The current app has no integration with an AI service.

Data Processing Agreement

Parties and scope. This DPA forms part of the Product agreement between the customer (controller, or processor acting for its controller) and the provider (processor, or subprocessor respectively). It applies only to personal data processed on the customer's behalf through the Product and associated instructed support conducted through an agreed channel covered by this DPA. The general enquiries mailbox must not be used to transmit customer project records or personal data from Jira.

Instructions and purpose. The agreement, documented configuration and authorized use of the Product are the customer's instructions to process data for scope analysis, financial forecasting, commercial records, service operation and instructed support. The provider will process that data only on documented instructions, including transfer instructions, unless applicable law requires otherwise. If legally permitted, it will inform the customer of such a requirement in advance. It will inform the customer if an instruction appears to infringe applicable data-protection law.

Details of processing. Duration is the service term plus the agreed deletion/platform-retention period. Operations include collection, retrieval, storage, comparison, calculation, display, export, correction, restriction and deletion. Data categories include the app data listed in the Privacy Notice and any support content expressly accepted through an agreed channel covered by this DPA. Data subjects may include customer personnel, contractors, clients and persons mentioned in issue summaries. The service is not designed to require special-category data or criminal-conviction data; customers should avoid entering it.

Confidentiality and security. The provider will ensure that persons authorized to process the data are subject to confidentiality obligations and will implement appropriate technical and organizational measures, considering the processing risks. The Security Measures below describe this release. Customer instructions do not authorize weakening those measures. The provider remains responsible for its applicable obligations even where the infrastructure is supplied by a third party.

Subprocessors. The customer authorizes Atlassian, acting under the Forge Terms and Forge Data Processing Addendum, to provide Forge runtime, storage and platform operations. This is the current subprocessor register for the Product. The applicable Atlassian contracting entity and its onward subprocessors are identified in those documents and Atlassian’s published subprocessor list. No separate email provider is authorized by this DPA to receive customer project records; any additional support channel requires its providers and safeguards to be disclosed and covered before such records are accepted. The provider will impose applicable equivalent data-protection obligations on subprocessors and remains responsible as required by law. Additional direct subprocessors will be notified at least 30 days before processing begins, allowing the customer to raise a reasonable data-protection objection. The parties will seek a reasonable resolution before the new subprocessor processes that customer's data; unresolved objections require an agreed alternative or termination of the affected service under the agreement.

Assistance. Taking account of the nature of processing and information available, the provider will assist with data-subject requests and the customer's obligations concerning security, breach notification, impact assessments and consultation with authorities. It will forward requests concerning customer-controlled data and will not independently answer them except on instructions or where law requires.

Personal-data breaches. The provider will notify the customer without undue delay after becoming aware of a personal-data breach affecting the customer's data. Available information will include the nature and scope, affected categories, likely consequences, contact point, and mitigation taken or proposed. Information can be supplied in stages as investigation progresses. This does not transfer the customer's independent statutory notification responsibilities.

Return and deletion. At the customer's choice, the provider will return or delete customer personal data at the end of the service, unless applicable law requires retention. The CSV report is a commercial report, not a full restorable data export. Other access/return requests must be handled through a verified support process. Platform backups and retention are governed by documented provider schedules; retained data remains protected and is not used for unrelated purposes. No claim of immediate physical backup erasure is made.

Verification. The provider will make available information needed to demonstrate compliance and allow and contribute to audits and inspections by the customer or its mandated independent auditor, subject to reasonable confidentiality and security arrangements that do not prevent statutory rights. The parties will use available documentation first where appropriate. Audit access must not disclose another customer's data.

International transfers. Transfers must use a mechanism permitted by applicable law. Atlassian's applicable Forge DPA and transfer provisions must be in effect for its processing. The Forge DPA includes the applicable Standard Contractual Clauses. This agreement does not itself authorize a new recipient or create a transfer mechanism by merely mentioning one.

Security Measures and Support Policy

The current Product runs on Atlassian Forge with installation-scoped hosted storage. Jira requests use the caller's authorization; project financial actions require Browse Projects and Administer Projects. Before returning stored issue snapshots, visibility is rechecked. License checks are performed on the server; authorized deletion is available even when a license is inactive.

Project mutations use conditional revisions and transactions to prevent conflicting changes from silently overwriting each other. Project erasure uses resumable batches. The privacy maintenance process reports explicit author identifiers to Atlassian and handles its erasure instructions. The current app declares no external data destinations or AI integration. These statements describe implemented controls, not independent audit certification or a claim that every attack has been ruled out.

Support: support@profitsignallabs.dev. Support follows the Marketplace Partner Agreement's response commitments: 24 hours for requests Atlassian identifies as critical and five business days for other requests. These are response deadlines, not guaranteed resolution times; no additional uptime percentage is promised. Send sanitized reproduction steps and approximate time. Security reports should omit exploit details or sensitive records until a safe exchange method is agreed. No public bug-bounty payment commitment is offered.

Start support requests with the action, time and a sanitized error message. Do not send project exports, issue summaries, account identifiers, credentials or customer records to the general mailbox. If a request requires customer data, a covered channel and minimal scope will be agreed first. Requests for access, return or erasure begin with minimal identifying information; no password or API token is required.

Subprocessor and platform references

- Forge DPA: https://developer.atlassian.com/platform/forge/resources/Forge-Data-Processing-Addendum.pdf
- Forge Terms: https://developer.atlassian.com/platform/forge/developer-terms/
- Atlassian subprocessors: https://www.atlassian.com/legal/sub-processors
- Forge storage lifecycle: https://developer.atlassian.com/platform/forge/storage-reference/

Forge currently documents a 28-day hosted-storage retention period after uninstall. Recovery requires customer consent and a request within 21 days. This does not promise immediate erasure of platform backups or override applicable legal retention. Customers can erase ScopeProfit project records before uninstall through Data controls; Jira issues are unaffected. Export and return obligations include responding to verified requests beyond the limited commercial CSV report.