Terms of Service
Effective date: 2 October 2026
1. Operator
Resultary is operated by David Finnich. Contact: support@getresultary.com.
2. Service availability and commercial access
Resultary for Jira Cloud is a commercial software service distributed through approved Atlassian channels. Access, pricing, billing, trials and license status are governed by the applicable Atlassian Marketplace listing and billing terms. Features, limits and integrations may evolve over time.
Resultary for n8n is currently a self-service beta. The current offer is a 15-day free trial followed by a recurring subscription at US$29 per month unless canceled before renewal. A payment method is required to start the trial. Taxes, currency conversion or localized amounts may vary by customer location and checkout; the amount and terms shown in the Paddle checkout control the transaction if they differ from marketing copy. The beta does not include a contractual production uptime commitment unless separately agreed in writing.
3. Billing, renewal and cancellation for n8n
n8n checkout and recurring billing are handled through Paddle. The subscription renews automatically at the applicable billing interval after the free trial unless canceled. During the beta, customers may use billing-management options provided by Paddle where available or contact support@getresultary.com to request cancellation before the next renewal. Cancellation stops future renewals but does not retroactively create a refund unless required by law or separately stated.
4. Authorization to install and use
You may install or use Resultary only on Jira Cloud sites, n8n workspaces, workflows, destination systems and data that you are authorized to administer or access. You are responsible for obtaining any internal approvals required by your organization.
5. Customer configuration and responsibility
Resultary verifies the run signals and Jira evidence that administrators configure. You are responsible for selecting appropriate monitors, proof rules, time windows, owners, business-impact values, notification destinations and escalation policies. Resultary does not replace backups, audit procedures, access controls, incident-management processes or human review.
6. Acceptable use
You must not use Resultary to obtain unauthorized access, interfere with systems, violate law, bypass security controls, disclose credentials improperly, or process information you are not authorized to process.
7. Platform quotas and limits
Resultary runs on Atlassian Forge and Jira Cloud and is therefore subject to applicable Atlassian platform quotas, storage limits, invocation limits, rate limits, maintenance and service availability. Those platform constraints may delay, throttle or temporarily prevent checks, notifications, incident synchronization or other functionality. Third-party Slack or Microsoft Teams integrations are also subject to their own service limits and availability.
8. No guarantee of complete detection or financial outcome
Resultary is designed to improve visibility into configured automation and business-result failures. It does not guarantee detection or prevention of every failure, delay, incorrect outcome, security incident or financial loss. “Value at risk” and “Estimated value protected” are calculated from administrator-provided values and app-observed recovery events; they are operational estimates, not accounting statements or guarantees of realized savings.
9. Intellectual property
Resultary, its software, product design, documentation and branding remain the property of the operator or applicable licensors. These Terms of Service grant only the limited right to use the applicable Resultary service for authorized evaluation and operation while access is valid.
10. Customer data
You retain your rights in data you or your organization provide or make available through Jira and Resultary. You are responsible for having the rights and permissions needed to configure Resultary to process that data. Data handling is further described in the Privacy Policy.
11. Feedback
You may provide feedback voluntarily. Feedback may be used to improve, develop and commercialize Resultary without an obligation to compensate the person providing it. Resultary will not intentionally publish customer-confidential information as a testimonial or case study without permission.
12. Third-party services
The Jira edition depends on Atlassian Jira Cloud and Atlassian Forge and may optionally integrate with Slack or Microsoft Teams / Microsoft Power Platform. The n8n beta may depend on n8n, Render, Neon, Paddle and an authorized customer destination used for independent proof. Those services are governed by their own terms, security controls and availability.
13. Support and service levels
Support is provided on a best-effort basis unless separately agreed in writing. No contractual uptime, support-response or recovery SLA applies unless a separate written service agreement states otherwise.
14. Suspension and termination
Access may be suspended or ended for security concerns, abuse, legal requirements, technical reasons, license expiration, beta completion or material violation of these terms. Jira users may stop using Resultary by uninstalling the app; n8n beta customers may stop product use by removing the Resultary workflow configuration and may request revocation of their Resultary integration key. Subscription cancellation is handled separately as described above. Jira records created by Resultary are not automatically removed when the app is uninstalled.
15. Disclaimer
To the maximum extent permitted by applicable law, Resultary is provided “as is” and “as available,” without warranties that the beta will be uninterrupted, error-free or suitable for every workflow or business purpose.
16. Limitation of liability
To the maximum extent permitted by applicable law, the operator will not be liable for indirect, incidental, special, consequential or punitive damages arising from use of Resultary. Nothing in these terms excludes liability that cannot legally be excluded or limited.
17. Changes to these terms
These Terms of Service may be updated as Resultary changes. Material revisions will update the effective date. Customers may be asked to accept additional terms or a data-processing agreement where applicable.