Contents
- 1. Who obtains consent
- 2. How consent is given
- 3. Purposes of processing under consent
- 4. Data covered
- 5. Processing actions
- 6. Recipients
- 7. Cross-border processing
- 8. Period of consent
- 9. Withdrawal
- 10. Voluntary nature
- 11. Your rights
- 12. No unverified compliance claims
- 13. Relation to other documents
- 14. Updates
1. Who obtains consent #
Consent is given to Komishan Nikita Danilovich (Комишан Никита Данилович), a self-employed individual (самозанятый), INN 231142994315 (the “Operator”).
Contact for consent and privacy matters: privacy@tydy.dev. Additional contacts: support@tydy.dev, legal@tydy.dev, security@tydy.dev. Correspondence is by email only; no postal address is provided.
2. How consent is given #
You give consent by affirmative action in the Service interface (for example checking a consent box, continuing registration after being shown this text, or another clear opt-in control labelled for personal data consent).
Consent is specific to the purposes described herein and in the Personal Data Processing Policy and Privacy Policy published on tydy.dev.
3. Purposes of processing under consent #
Where consent is the applicable ground, you agree that the Operator may process your personal data to:
- Create and administer your user account and authentication (including necessary cookies flowtask_session, flowtask_csrf, and optional tydy_remember_device).
- Provide workspace collaboration features and enforce permissions.
- Operate Telegram integrations only for chats and bindings you configure, including storing message context needed for AI routing and audit.
- Generate AI-proposed actions and present them for Inbox review or auto-application according to product rules (message ≠ automatic task).
- Provide MCP access via OAuth and/or PATs, applying scopes ∩ RBAC, with token secrets hashed after issuance.
- Process workspace billing via YooKassa, including subscription status, automatic renewal when the User gives separate consent at checkout, and saved payment-method metadata that does not include full card credentials. This personal-data consent is not consent to automatic charges; auto-renewal consent is given separately at checkout.
- Provide support, security monitoring, and abuse prevention.
- Store locale and theme preferences in localStorage on your device.
4. Data covered #
Consent covers personal data you provide or that is generated through use of the Service, including identity and contact data, credentials and session identifiers, workspace membership, Customer Content you submit, Telegram integration content you enable, AI proposal and review metadata, MCP connection metadata, billing references, and technical security logs.
5. Processing actions #
You consent to collection, recording, systematization, accumulation, storage, clarification, retrieval, use, transfer to processors necessary to operate the Service (including payment via YooKassa and infrastructure providers), anonymization where used, blocking, deletion, and destruction of personal data for the purposes above.
6. Recipients #
Personal data may be accessible to workspace members according to RBAC, to MCP clients you authorize within scopes ∩ RBAC, to subprocessors needed to run tydy.dev, and to authorities when required by law. Telegram and MCP host vendors act under their own terms when you use those products.
7. Cross-border processing #
You acknowledge that processing may occur on infrastructure outside your country of residence as needed to provide the Service, and you consent to such transfers where consent is required for that purpose.
8. Period of consent #
Consent is valid from the moment it is given until withdrawn, or until the purposes of processing are achieved or become impossible, subject to legal retention obligations of the Operator.
9. Withdrawal #
You may withdraw consent by emailing privacy@tydy.dev from your registered address or via an in-product control if provided. Withdrawal does not affect the lawfulness of processing before withdrawal.
After withdrawal, the Operator may continue processing where another legal ground applies (for example contract performance or legal obligation). Features that depend solely on consent may become unavailable.
10. Voluntary nature #
Consent is given freely. Refusal or withdrawal may prevent registration or continued use of some or all Service features because personal data is inherent to providing an authenticated SaaS workspace.
11. Your rights #
You retain rights of access, correction, deletion, restriction, and complaint as described in the Personal Data Processing Policy and applicable law. Contact privacy@tydy.dev to exercise them.
12. No unverified compliance claims #
Nothing in this consent asserts that the Operator holds specific third-party certifications or regulatory approvals beyond what is factually true for the Service. Security practices are described at a high level in the Privacy Policy.
13. Relation to other documents #
This consent is read together with the Privacy Policy, Personal Data Processing Policy, Cookie Policy, Terms of Service, and Public Offer. In case of conflict on commercial terms, the Public Offer and Terms prevail; on privacy mechanics, the Privacy and Personal Data policies prevail unless mandatory law requires otherwise.
14. Updates #
If processing purposes change materially, the Operator will seek a new consent or rely on another lawful basis and update the documents on tydy.dev (effectiveDate / updatedDate).