Terms of Service

1. Operator and agreement #

The Service is operated by Komishan Nikita Danilovich (Комишан Никита Данилович), a self-employed individual (самозанятый), INN 231142994315 (the “Operator”).

These Terms set the rules for using the Service. Paid access, including payment, plans, auto-renewal, saving a payment method, and refunds, is governed by the separate Public Offer. If there is a conflict on payment matters, the Public Offer prevails. By creating an account, accessing tydy.dev, or using the Service, you agree to these Terms, the Acceptable Use Policy, and other policies referenced herein. If you use the Service on behalf of an organization, you represent that you have authority to bind that organization.

2. The Service #

Tydy is a multi-tenant workspace product for projects, tasks, feeds, and related collaboration. Optional features include Telegram integrations you configure, AI-assisted routing of conversational input into proposed project actions, an Inbox for human review of proposals below auto-apply thresholds, and MCP access for authorized clients.

One Telegram message is not automatically one task. Messages may be batched and interpreted as a change of project state; a batch may produce no actions. Later messages may update existing work. The AI proposes typed actions; validation, policy, confidence thresholds, and application occur in the Service’s business layer—not as unchecked model output written directly to authoritative records.

3. Accounts and workspaces #

You must provide accurate registration information and keep credentials confidential. You are responsible for activity under your account, including MCP tokens and OAuth grants you authorize.

Workspaces are permissioned environments. Server-side authorization controls access; client UI restrictions are cosmetic only. Denials for private resources may be presented without confirming existence of the resource.

4. Telegram and MCP #

Telegram features operate only for chats and bindings you configure. You must have the right to connect those chats and to process their content in the Service.

MCP may authenticate via OAuth and/or personal access tokens. Effective capability is the intersection of granted scopes and your live RBAC permissions. Tokens are hashed at rest after issuance; treat plaintext tokens as secrets and revoke them if compromised.

5. Your content and licence #

You retain ownership of content you submit (“Customer Content”). You grant the Operator a non-exclusive, worldwide licence to host, process, transmit, and display Customer Content solely to operate, secure, and support the Service, including AI proposal generation and review workflows you enable.

You represent that you have all rights needed to submit Customer Content and that it does not violate law or third-party rights.

6. Plans, payment, and auto-renewal #

Paid features are provided under catalog plans, including Free, Pro, Team, and other plans shown in the Service. Payment is accepted in Russian rubles via YooKassa.

The Service may offer a trial for some plans if platform settings allow it. A trial by itself is not the User’s consent to automatic charges.

When purchasing a paid subscription, the User may consent to saving a payment method and turning on automatic renewal.

With auto-renewal enabled, the plan price is charged automatically from the saved payment method at the start of the next billing period.

Before checkout, the User is shown the plan price, subscription period, and auto-renewal information.

In billing settings the User may turn off automatic renewal, detach a saved payment method, or change the plan under the available billing rules.

Turning off auto-renewal or detaching a payment method does not end already-paid access: the plan remains until the current paid period ends.

If an automatic charge fails, the Service may retry during a grace period. If payment is not completed successfully before that period ends, the workspace is moved to Free or another base plan under the then-current billing rules.

A switch to a cheaper paid plan may be scheduled for the next billing period. That plan takes effect only after successful payment for the corresponding period and is not granted for free if payment fails.

Detailed terms of payment, auto-renewal, plan changes, turning off auto-renewal, and refunds are governed by the Public Offer.

7. Acceptable use #

You must comply with the Acceptable Use Policy. The Operator may suspend or terminate access for violations, security risk, non-payment, or legal compulsion, and may rate-limit or block abusive traffic.

8. Availability and changes #

The Service is provided on an “as available” basis. The Operator may modify features, APIs, MCP scopes, plan entitlements, and interfaces, including discontinuing beta or optional integrations. Material billing changes will be reflected in pricing materials or the Public Offer.

The Operator does not warrant uninterrupted or error-free operation, nor that AI proposals will be accurate, complete, or suitable for any particular decision without human judgment.

9. Operator intellectual property #

The Service software, branding, documentation, and related materials are owned by the Operator or its licensors. Except for the limited right to use the Service under these Terms, no rights are granted. You may not reverse engineer, scrape, or misuse the Service except where mandatory law prohibits such restriction.

10. Security and confidentiality #

The Operator takes reasonable measures to protect the Service. You must promptly notify security@tydy.dev of suspected unauthorized access. Necessary cookies (flowtask_session, flowtask_csrf, tydy_remember_device) and localStorage preferences (locale, theme) support authentication and UX. The Service uses Yandex.Metrika for site analytics as described in the Cookie Policy.

11. Disclaimers #

To the maximum extent permitted by law, the Service is provided “as is” and “as available” without warranties of merchantability, fitness for a particular purpose, or non-infringement. The Operator makes no false compliance claims and does not assert certifications that have not been obtained for the Service.

12. Limitation of liability #

To the maximum extent permitted by law, the Operator is not liable for indirect, incidental, special, consequential, or lost-profit damages, or for loss of data, goodwill, or business interruption arising from use of the Service, AI proposals, Telegram or MCP integrations, or third-party platforms.

To the extent permitted by applicable law, the Operator’s aggregate liability arising out of these Terms is limited to the fees you paid to the Operator for the affected workspace in the three (3) months preceding the claim; if no fees were paid, liability is limited as mandatory law requires (including consumer and personal-data protections that cannot be waived). Nothing in these Terms excludes liability where exclusion is prohibited.

13. Indemnity #

You will defend and indemnify the Operator against claims arising from your Customer Content, your integrations, your misuse of MCP or Telegram features, or your violation of these Terms or applicable law, except to the extent caused by the Operator’s wilful misconduct.

14. Term and termination #

These Terms apply while you use the Service. You may stop using the Service and request account closure subject to workspace ownership and data-retention rules. Provisions that by nature should survive (including ownership, disclaimers, limitations, and indemnity) survive termination.

15. Governing law and contact #

These Terms are governed by the laws of the Russian Federation, without regard to conflict-of-law rules, except where mandatory consumer protections of your residence apply. Disputes should first be raised with legal@tydy.dev.

Contact: support@tydy.dev, legal@tydy.dev, privacy@tydy.dev, security@tydy.dev. Operator: Komishan Nikita Danilovich (Комишан Никита Данилович), self-employed (самозанятый), INN 231142994315. Email only—no postal address is provided for notices under these Terms.