Terms of Service

Effective date: 2026-04-27 Last updated: 2026-06-07 Version: 1.0.5

1. Parties and acceptance

These Terms of Service ("Terms") constitute a binding agreement between:

• CT Core, trading name of Viktar Martavitski, sole proprietor (JDG) registered with the Polish Central Registration and Information on Business (CEIDG), NIP 9512543228, REGON 522272970, registered address ul. Hoza 86/410, 00-682 Warsaw, Poland ("CT Core", "we", "us"); and

• The legal entity or individual that installs, configures, or uses the Threadmaker product, including any of its authorized users ("Customer", "you").

By installing Threadmaker, checking "I agree", clicking through an Atlassian Marketplace or Slack App Directory purchase flow, or using the Service, you accept these Terms. If you are accepting on behalf of an organization, you warrant that you are authorized to bind that organization.

If you do not agree with these Terms, do not install or use the Service.

2. Definitions

• "Service" — the Threadmaker software, including the Forge plugin for Atlassian Jira Cloud, the Slack application, the web dashboard at threadmaker.dev, and all related documentation, APIs, and integrations.
• "Customer Data" — all data that the Customer or its users submit to, or is transmitted through, the Service, including message content, attachments, issue references, and workspace metadata.
• "Atlassian Marketplace" — the digital storefront operated by Atlassian, Inc. and affiliated Atlassian entities at marketplace.atlassian.com.
• "Slack App Directory" — the digital storefront operated by Slack Technologies LLC at slack.com/apps.
• "Marketplace Terms" — the Atlassian Marketplace Partner Agreement and the Slack App Directory Agreement, respectively, which bind CT Core as a Marketplace vendor.
• "Subscription Fees" — the fees payable for the paid tiers of the Service as set forth on the Service's Atlassian Marketplace listing (which is the canonical source for current pricing tiers and per-tier feature details).

3. License grant

Subject to the Customer's compliance with these Terms and payment of applicable Subscription Fees, CT Core grants the Customer a worldwide, non-exclusive, non-transferable, non-sublicensable, revocable right to install and use the Service during the term of these Terms, for the Customer's internal business purposes, in a number of Slack workspaces and Jira sites commensurate with the purchased tier.

This license does not grant the Customer any right, title, or interest in the Service beyond the use rights expressly stated. All intellectual-property rights remain with CT Core or its licensors.

4. Restrictions

The Customer shall not, and shall not permit any third party to:

1. Reverse-engineer, decompile, disassemble, or otherwise attempt to derive source code, object code, or underlying ideas, algorithms, or structure of the Service, except to the extent such restriction is prohibited by applicable law;
2. Resell, sublicense, rent, lease, or otherwise commercially exploit the Service except as expressly permitted herein;
3. Remove, alter, or obscure any copyright, trademark, or other proprietary notices;
4. Use the Service to build a competing product or benchmark it for public comparison without prior written consent;
5. Use the Service in violation of any applicable law or third-party right (including Slack's and Atlassian's Acceptable Use Policies);
6. Attempt to probe, scan, or test the vulnerability of the Service, breach authentication, or interfere with service to any user, host, or network (except under a responsible-disclosure process at security@threadmaker.dev);
7. Use the Service to process content that is illegal, abusive, infringing, or that the Customer does not have a lawful basis to process;
8. Circumvent any usage limit, throttle, or seat restriction of the subscribed tier.

5. Customer responsibilities

• Credentials and installation permissions. The Customer is responsible for controlling which administrators may install, authorize, configure, or remove the Service in the Customer's Slack workspace and Atlassian Jira site. CT Core is responsible for protecting Service-side credentials that it stores, including Slack bot OAuth tokens, per-installation HMAC secrets, and installation connection tokens, as described in the DPA and applicable security documentation. The Customer must promptly notify CT Core at security@threadmaker.dev if the Customer suspects unauthorized installation, unauthorized configuration changes, misuse of the Service, compromise of an administrator account, or compromise of a Service authorization.
• Authorized users. The Customer is responsible for the acts and omissions of any person the Customer authorizes to use the Service.
• Lawful processing. The Customer warrants that any Customer Data submitted to the Service has been lawfully collected, that the Customer has any required consents from data subjects, and that its use of the Service complies with applicable laws.
• Content. The Customer is solely responsible for its Customer Data and for the accuracy, legality, and quality thereof.

5.1 No high-risk regulated use without written agreement

The Service is designed for general business collaboration and software / product workflow synchronization. It is not designed for use as a system of record for protected health information (PHI), classified or government-restricted information, payment-card data (PCI-DSS), financial account credentials, children's data, or other high-risk regulated data unless CT Core has expressly agreed in writing to additional safeguards. The Customer is responsible for configuring Slack, Atlassian Jira, and the Service to avoid synchronizing channels, projects, comments, messages, or attachments containing such data unless the Customer has determined that the use is lawful and appropriate.

5.2 No sale, advertising, or model training

CT Core shall not sell Customer Data, use Customer Data for cross-context behavioral advertising, or use Customer Data to train artificial-intelligence or machine-learning models, except where the Customer has expressly instructed or authorized such processing in writing. CT Core may use aggregated or de-identified operational metrics solely to operate, secure, improve, and measure the Service, provided such metrics do not identify the Customer, its users, or data subjects and cannot reasonably be re-identified.

6. Subscriptions, fees, and billing

6.1 Billing channel

Subscription Fees for the Jira Forge plugin are collected by Atlassian via the Atlassian Marketplace and remitted to CT Core net of Atlassian's revenue share. The applicable revenue share is set by Atlassian under the Marketplace Partner Program for Cloud apps and may change from time to time; the current rate is published at https://www.atlassian.com/partners/marketplace/program. Atlassian's pricing policy controls; the Customer's payment relationship is governed by the Atlassian Customer Agreement and the Atlassian Marketplace Terms of Use. No direct invoicing occurs between CT Core and the Customer unless separately agreed in writing.

The Slack App is provided free of charge and has no associated Subscription Fee. Monetization applies exclusively to the Jira-side paid tiers.

6.2 Current pricing tiers (as of the Effective Date)

Annual commitments receive a 15% discount. Authoritative and current pricing is published on the Atlassian Marketplace listing (which is the canonical source); per-tier feature details are in the Marketplace listing description.

6.3 Taxes

Atlassian collects and remits applicable sales, use, VAT, and similar taxes on behalf of CT Core where required. Where tax is not so collected, the Customer is responsible for all applicable taxes other than those based on CT Core's net income.

6.4 Refunds

Refund requests are handled under Atlassian's refund policy. Where Atlassian issues a refund to the Customer, any resulting adjustment between Atlassian and CT Core is handled between Atlassian and CT Core. CT Core does not offer direct refunds for Marketplace-mediated purchases.

6.5 Free tier

The free tier (currently up to 10 Jira-side users) is provided as-is with no Subscription Fee. The Atlassian Marketplace listing for the Service is the canonical source for current pricing tiers, seat thresholds, and the corresponding Subscription Fees applied above the free-tier cap; the figures published on threadmaker.dev are mirrored from the Marketplace listing for convenience and may briefly lag during a Marketplace pricing change. CT Core reserves the right to modify, limit, or discontinue the free tier at any time with 30 days' notice via the Service or threadmaker.dev.

7. Term and termination

7.1 Term

These Terms commence on first installation and continue until terminated as set forth below.

7.2 Termination for convenience

The Customer may terminate these Terms at any time by uninstalling the Service from its Atlassian site and Slack workspace.

7.3 Termination for cause

Either party may terminate these Terms for material breach on 14 days' written notice if the breach is not cured. CT Core may terminate immediately without notice for (a) non-payment of Subscription Fees as reported by Atlassian, (b) security violation, or (c) activity that threatens the operation of the Service.

7.4 Effect of termination

Upon termination:

• The Customer's right to use the Service ends immediately;
• CT Core will delete Customer Data in accordance with the Privacy Policy and DPA (typically within 30 days);
• Accrued Subscription Fees for the current billing period remain payable (handled via Atlassian);
• Sections that by their nature should survive termination will survive (including Sections 4, 6.3, 8, 9, 10, 11, 12, 13).

8. Warranties and disclaimers

8.1 Limited warranty

CT Core warrants that during the term it will provide the Service with reasonable care and skill consistent with prevailing industry practice for SaaS vendors of similar scale.

8.2 Service level

There is no contractual SLA unless separately agreed in an enterprise order form. Operational health monitoring is available at /healthz (machine-readable JSON endpoint); best-effort availability targets are described in the Atlassian Marketplace listing.

8.3 Disclaimer

EXCEPT AS EXPRESSLY STATED IN SECTION 8.1, THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", AND CT CORE DISCLAIMS ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT.

CT CORE DOES NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR FREE OF HARMFUL COMPONENTS, NOR THAT ANY DATA WILL REMAIN SECURE OR UNALTERED ABSENT CATASTROPHIC EVENTS.

Some jurisdictions do not allow the exclusion of implied warranties, in which case such warranties are limited to the greatest extent permitted.

9. Limitation of liability

9.1 Exclusion of indirect damages

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOSS OF PROFITS, REVENUES, DATA, OR BUSINESS OPPORTUNITY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

9.2 Liability cap

EACH PARTY'S TOTAL CUMULATIVE LIABILITY TO THE OTHER UNDER OR IN CONNECTION WITH THESE TERMS, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STATUTE, OR ANY OTHER LEGAL THEORY, SHALL NOT EXCEED THE TOTAL SUBSCRIPTION FEES PAID OR PAYABLE BY THE CUSTOMER FOR THE SERVICE DURING THE 12 MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM.

9.3 Exceptions

Nothing in this Section excludes or limits a party's liability for:

• death or personal injury caused by negligence;
• fraud or fraudulent misrepresentation;
• gross negligence or willful misconduct;
• any liability that cannot be excluded or limited under applicable law (including GDPR administrative fines levied directly against that party).

9.4 Enterprise liability cap

For paid enterprise plans or separately executed order forms, the parties may agree to a different liability cap for confidentiality, security, data-protection, indemnity, or service-availability claims. Unless such a different cap is expressly agreed in a signed order form or written agreement between the parties, the standard liability cap in Section 9.2 applies to the maximum extent permitted by law.

10. Indemnification

10.1 By CT Core

CT Core will defend, indemnify, and hold harmless the Customer against any third-party claim (a) alleging that the Service, when used in accordance with these Terms, infringes a third party's copyright, trade mark, or EU / US registered patent, or (b) arising directly from a personal-data breach inside the Service infrastructure caused solely by CT Core's gross negligence or material breach of its obligations under the DPA, and will pay damages finally awarded or agreed in settlement, subject to the liability cap in Section 9.2.

10.2 By Customer

The Customer will defend, indemnify, and hold harmless CT Core against any third-party claim arising from (a) Customer Data, (b) the Customer's use of the Service in violation of these Terms or applicable law, or (c) any dispute between the Customer and its users or data subjects.

10.3 Procedure

The indemnified party shall promptly notify the indemnifying party of the claim, tender control of the defense (with the indemnified party's reasonable cooperation at the indemnifying party's expense), and not settle any claim without the indemnifying party's prior written consent.

11. Data protection

The Parties' obligations regarding Personal Data are set out in the Privacy Policy at threadmaker.dev/privacy and the Data Processing Addendum at threadmaker.dev/dpa, which form part of these Terms. Where the Customer acts as Data Controller and CT Core acts as Data Processor, the DPA governs and, in the event of conflict with these Terms as to such processing, the DPA prevails.

12. Marketplace Terms

The Customer acknowledges that its relationship with Atlassian and Slack is governed by separate agreements with those providers. These Terms are offered in addition to, and do not supersede, any Marketplace Terms. In the event of a conflict between these Terms and a non-negotiable provision of the Marketplace Terms as imposed on CT Core as a vendor, the Marketplace Terms prevail strictly to the extent of such conflict.

13. Governing law and dispute resolution

13.1 Governing law

These Terms are governed by the laws of the Republic of Poland, excluding its conflict-of-laws rules and the United Nations Convention on Contracts for the International Sale of Goods (CISG).

13.2 Mediation first

Any dispute arising out of or in connection with these Terms shall first be submitted to good-faith negotiation between the parties' authorized representatives. If no resolution is reached within 30 days, the parties shall attempt mediation in Warsaw, Poland, before escalating to litigation. Either party may initiate mediation by written notice; mediator fees are shared equally unless the mediator orders otherwise.

13.3 Exclusive jurisdiction

Failing mediation, the parties irrevocably submit to the exclusive jurisdiction of the competent courts of Warsaw, Poland. Notwithstanding the foregoing, CT Core may bring proceedings to enforce intellectual-property rights in any court of competent jurisdiction.

13.4 Consumer exception

If the Customer qualifies as a consumer under Polish law, nothing in this Section deprives the Customer of rights of access to the court of the Customer's domicile or of EU-mandated consumer protection.

14. General provisions

14.1 Entire agreement

These Terms, together with the Privacy Policy, DPA, and the applicable Marketplace Terms, constitute the entire agreement between the parties and supersede all prior or contemporaneous communications.

14.2 Amendment

CT Core may update these Terms by publishing a revised version at threadmaker.dev/terms. Material changes take effect 30 days after publication. Continued use of the Service after the effective date constitutes acceptance.

14.3 Assignment

Neither party may assign these Terms without the other's prior written consent, except that CT Core may assign to a successor entity in connection with a corporate restructuring, conversion of legal form, incorporation, merger, acquisition, or sale of substantially all its assets, on written notice.

14.4 Force majeure

Neither party is liable for delays or failures caused by events beyond its reasonable control, including acts of God, war, terrorism, pandemic, governmental action, labour disputes, or failure of third-party infrastructure (including Cloudflare, Atlassian, or Slack).

14.5 Notices

Formal legal notices to CT Core shall be sent to legal@threadmaker.dev with a copy by registered mail to the registered address in Section 1. Notices to the Customer will be sent to the admin email on file with Atlassian or Slack.

14.6 Severability

If any provision is held unenforceable, the remaining provisions remain in full force, and the unenforceable provision is deemed modified to the minimum extent necessary to make it enforceable, preserving original intent.

14.7 No waiver

Failure to enforce a provision is not a waiver of the right to later enforce that or any other provision.

14.8 Independent contractors

The parties are independent contractors. Nothing in these Terms creates an agency, partnership, joint venture, or employment relationship.

14.9 Language

These Terms are issued in English. A Polish translation may be provided for convenience; in the event of conflict the English original prevails, except where Polish consumer law mandates otherwise.

Legal entity: Viktar Martavitski CT Core — NIP 9512543228 — REGON 522272970 — ul. Hoza 86/410, 00-682 Warsaw, Poland.

Contacts: legal@threadmaker.dev (legal notices) · dpo@threadmaker.dev (privacy / DSR / breach) · security@threadmaker.dev (security disclosure) · support@threadmaker.dev (operational support).

This document has been prepared for public publication on threadmaker.dev/terms. It is recommended to obtain a Poland-qualified legal review before the first paid installation onboards.